Webflow Sitemap: Turn It On, Exclude Pages and Submit It
Where is my Webflow sitemap? Once you turn on Webflow’s auto-generated sitemap in your site settings (SEO tab), it is published at https://yourdomain.com/sitemap.xml and rebuilt when you publish the site. To keep a page out, switch off its Sitemap indexing setting: Webflow then adds a noindex tag and drops the page from the sitemap.
When we checked webflow.com on September 25, 2026, its sitemap was at /sitemap.xml (a sitemap index) and its robots.txt pointed to it with a Sitemap: line.
Turn On the Auto-Generated Sitemap
In your site settings, open the SEO tab and enable the auto-generated sitemap, then publish. Webflow builds the file from your published static pages and CMS items. You can instead paste your own sitemap XML into a custom sitemap field, but then you have to keep it up to date by hand, so auto-generation is the better choice for almost every site.
The auto-generated sitemap reflects the published site. New pages and CMS items appear after you publish, not when you save.
Keep Pages Out of the Sitemap
Use the Sitemap indexing toggle. In a page’s settings, turn Sitemap indexing off. According to Webflow’s help center, the page is then no longer indexed by search engines and no longer included in the sitemap. The toggle only works when the auto-generated sitemap is on.
A noindex in custom code is not enough. If you add a noindex tag through custom code, or block a page in robots.txt, Webflow still lists it in the auto-generated sitemap until you also turn Sitemap indexing off. That leaves Google with two conflicting signals, so use the toggle.
CMS collections. Collection items take their settings from the collection template page, so set indexing there for the whole collection. Keep draft items unpublished until they are ready.
Good candidates to exclude: utility pages such as the style guide, password and 404 pages, thank-you pages, and any template page that only exists for design.
Stop the webflow.io Address From Being Indexed
Every Webflow site also lives at yoursite.webflow.io. Once your custom domain is live, you don’t want Google indexing that copy as well. Webflow has a setting to disable search engine indexing of the Webflow subdomain; you need a Site plan or a paid Workspace to use it. Then connect your custom domain, make it the default domain, and publish, so the sitemap lists custom-domain URLs.
Submit Your Webflow Sitemap to Google
- Add your custom domain as a property in Google Search Console and verify it, either with a DNS record or by adding the verification meta tag to your site’s custom head code.
- Publish the site so the verification and sitemap are live.
- In Search Console, open Sitemaps, enter
sitemap.xmland click Submit.
Submit the sitemap on your custom domain, not on webflow.io.
Submit It to Bing
In Bing Webmaster Tools, add your site (or import it from Search Console), open Sitemaps and submit https://yourdomain.com/sitemap.xml. Bing also supplies results to several AI assistants, so it is worth the two minutes.
Common Webflow Sitemap Problems
There is no sitemap at /sitemap.xml
The auto-generated sitemap is switched off, or you haven’t published since switching it on. Turn it on in the SEO settings and publish.
New pages or CMS items are missing
Publish the site; the sitemap is built from the published version. If a page is still missing, check its Sitemap indexing toggle, and for CMS items check the collection template and whether the item is still a draft.
The sitemap lists pages you marked noindex
You probably added the noindex with custom code. Turn off Sitemap indexing on those pages instead, so the tag and the sitemap agree.
Sitemap URLs use webflow.io
Connect your custom domain, set it as the default, and publish again. Then submit the custom-domain sitemap in Search Console.
How to Check Your Sitemap
Open https://yourdomain.com/sitemap.xml after publishing and spot-check a few URLs. For an outside check, the free sitemap finder reads your robots.txt, locates the sitemap, and tests 30 of its URLs for 404s, redirects, noindex tags and canonical problems.