Streaming live at 10am (PST)

Sitemap.xml - covarge errors/warnings issues & exclude collection pages

Scenario: home>team - Inside this page a collection-list of 50 team members - without seperate page (post) for each team member.
Collection: team members (slug “team”)
Items: 50 collection items (tom, mark, anton, lorem…member 50)…

webflow will auto-generate-sitemap 50 pages (empty pages)

  • /team/tom
  • /team/mark
  • /team/anton
  • /team/team-member-50

Than under google console the spiders will “go crazy” and the site get a lot of covarge errors issues -or Warnings


To avoid indexing - The classis solution is to block pages by Disallow: /folder-name/ robots.txt (or by meta tag in the head) - but this also will cause errors (Beacuse you block pages Which appears on the auto-generate-sitemap).

** auto generate sitemap set to off is not practical solution for medium-big projects.

Any ideas/wishlist -or- trick to solve this issue?

1 Like

Looks like you need to edit the sitemap.xml output then upload that as a custom sitemap. Unless I am missing something, webflow needs to provide an a sitemap exclusion option for collections in the collection settings.

Thanks. Related. I find this wishlist topic (From may 17):

Automatic Sitemap Improvements

Hi @Siton_Systems, second time I’m on one of your posts today :stuck_out_tongue_winking_eye:

I have the same issue. Did you end up manually updating the sitemap every time new content, E.g. blog posts, were added or did you just allow collection pages you wanted excluded to be indexed and appear in the site map?

No solution. “Middle solution”:

  • draft or protect by password unwanted pages (“unwanted” - page you don’t want in your auto-sitemap).

Again for small project its fine, but for big project this is very tidy to manually update sitemap (So you should “live” with X console coverage errors).


In blog-posts its very rare to "excluded " post-X. The problem is with empty collection pages (Sometime you create collection without design/create collection page).

  1. Ya, I had managed to exclude 2 standard pages by password protecting them.
  2. Unfortunately CMS Collection pages don’t seem to exclude even when password protected. I don’t want to “draft” the actual items (in the e.g. below gallery images) as they wouldn’t pull through to the category page.

password - They didn’t exclude from site-map - but you also wont get console coverage errors. This is why i call this solution “middle solution”.

Surprised more users haven’t brought this up. Anyway I’ve voted on the Wishlist. Fingers crossed that a better solution will be made standard.

Open user her:

And vote + comment her: