Webflow sitemap
How it works, and the traps that catch CMS sites.

Webflow generates your sitemap for you at /sitemap.xml and rebuilds it every time you publish, so for most sites the job is to switch it on, publish, and submit it to Google Search Console. The traps start when you want to keep a page out of it: the toggle that does that also adds noindex, robots.txt does not remove anything from the sitemap, and a custom sitemap means you maintain it by hand.

Everything below about Webflow's behaviour comes from its own Help Center articles, Create a sitemap in Webflow and Disable search engine indexing, which we read on 21 October 2026.

Turn it on

1. 1Open the settingSite settings, SEO tab, Sitemap section.
2. 2Enable itSet Auto-generate sitemap to Yes and save.
3. 3PublishThe file only exists on the published site.
4. 4Check itOpen yourdomain.com/sitemap.xml and read it. Do not assume.
5. 5Submit itIn Google Search Console, Sitemaps, type sitemap.xml, submit.

Two details worth knowing. Each URL carries a lastmod date, which is the date that page was last published, and it only updates when you republish. And Webflow adds the sitemap address to your robots.txt on its own, so if you also type it in by hand, the file ends up listing it twice.

Once you have published a sitemap, Webflow says you cannot delete the /sitemap.xml page, so decide before you publish whether you want that URL to exist.

Trap 1: the exclusion toggle is not sitemap-only

The setting called Sitemap indexing, in each page's SEO settings, sounds like it only edits the sitemap. According to Webflow's documentation it does two things at once: it removes the page from the sitemap and adds a noindex robots meta tag to the page.

That is what you want for a thank-you page. It is not what you want if the page should stay findable in Google but you would rather not list it in the sitemap. With the automatic sitemap, that combination does not exist.

The toggle also only works while the automatic sitemap is switched on.

Trap 2: robots.txt does not take a page out of the sitemap

Per Webflow, a page you disallow in robots.txt is still included in the generated sitemap. So is a page where you added noindex yourself in custom code, unless the Sitemap indexing toggle is off too.

The result is a sitemap that invites Google to a URL your own rules say to avoid. Webflow's guidance for pages you want out of search is to use the toggle rather than robots.txt, because content can still be indexed without being crawled if it is linked from elsewhere.

Trap 3: CMS items

Each published CMS item gets a URL, so a collection of 300 items puts 300 URLs into your sitemap. Items have their own Sitemap Indexing toggle, under Item details. It overrides the site-level setting for that item, adds noindex, and excludes the item from the sitemap. It is only available on paid Site plans.

What to do with that:

• Leave the toggle on for items you want to rank.
• Turn it off for draft-like entries, near-empty profiles and campaign pages that exist for one audience.
• Do not use it as a substitute for fixing thin content. A noindexed page is a page nobody finds.

Trap 4: the custom sitemap

You can switch off auto-generate and paste your own XML into the Custom sitemap field. That is the only route to a page that is indexable but not listed. The cost is that Webflow stops updating it. New pages do not appear, deleted pages stay, and on a site using Localize you must add the hreflang tags yourself. We would only do this for a specific reason, and we would write the reason down.

What the models said today

We asked the same question on 19 October 2026, with web search on: "How does the Webflow sitemap work? Are CMS items and collection pages included, and how do I exclude pages?" ChatGPT came through DataForSEO's ChatGPT scraper, Perplexity through its Sonar Pro model.

• ChatGPT cited three Webflow Help Center articles and nothing else. Its steps and its warning that robots.txt blocking is not the same as leaving a URL out of the sitemap match the documentation above.
• Perplexity listed ten sources, and none of them was Webflow's own Help Center: agency blogs, SEO tool vendors and a developer's personal blog. Its advice to combine sitemap exclusion with a noindex setting reads as if they were two separate steps, which does not match what Webflow documents for the toggle.

Neither answer was bad. But the model that went to the source was the one that got the toggle right, and we found that worth knowing before copying a checklist from a summary of agency blogs, including this one.

What a sitemap will not do

A sitemap is a hint. Google's documentation says submitting one does not guarantee Google will fetch it or crawl the URLs in it, and that it ignores the priority and changefreq tags. It uses lastmod only when the dates are consistently accurate. One sitemap file holds at most 50,000 URLs or 50 MB uncompressed, which matters for very large CMS sites.

So a clean sitemap is hygiene, not a ranking tactic. If your pages are missing from Google, the sitemap is rarely the reason: look at content, internal links and noindex first. This one is also a ten-minute job. If you only need it done, do it yourself with this note, and spend our time on something harder. When the sitemap is one symptom of a larger indexing problem, that is the work on the Webflow SEO page.

The demand is small, too. Google Ads data via DataForSEO puts "webflow sitemap" at about 70 US searches a month, with a monthly range of 30 to 140 over the last twelve months and keyword difficulty 1 (checked 19 October 2026). Crawler access matters beyond Google as well, which we cover in ChatGPT SEO: what OpenAI documents.