Webflow Sitemap

What is a Webflow sitemap?

A Webflow sitemap is an XML file that lists the pages search engines should be able to discover on a Webflow website. It acts as a crawl guide by providing URLs and, where available, information about when those pages were last updated.

When automatic sitemap generation is enabled, Webflow creates and updates the sitemap as pages and CMS items are published. It is normally available at /sitemap.xml on the website’s primary domain.

Does Webflow automatically create a sitemap?

Yes. Webflow can automatically generate a sitemap for hosted sites. Static pages and eligible CMS Collection pages are added when they are published and allowed to appear in the sitemap.

The sitemap supports discovery, but it does not guarantee indexing or rankings. Search engines still evaluate whether a URL is accessible, canonical, valuable, and eligible to appear in search results.

What does a Webflow sitemap include?

A generated sitemap can include:

• Published static pages.
• Published CMS Collection item pages.
• Localized page URLs when localization is configured.
• Last-modified information supported by the platform.

Draft, unpublished, excluded, or otherwise ineligible pages should not appear. Utility pages and certain system-generated URLs may be handled differently from normal indexable pages.

How do you find your Webflow sitemap?

Add /sitemap.xml to the main domain. For example, the sitemap for example.com would normally be found at https://example.com/sitemap.xml.

Open the URL in a browser and check that it loads successfully, uses the correct preferred domain, and contains the pages you expect. It is especially important to inspect the sitemap after a migration, domain change, localization rollout, or large CMS import.

How do you submit a Webflow sitemap to Google?

1. Verify the website in Google Search Console.
2. Open the Sitemaps report for the correct domain property.
3. Enter the sitemap path, usually sitemap.xml.
4. Submit it and review the status for processing or retrieval errors.

Submitting the file helps Google locate it quickly, but Google may also discover it through the website’s robots.txt file and normal crawling.

How do you remove a page from the Webflow sitemap?

Exclude a page or CMS item from indexing and the generated sitemap using the relevant SEO or sitemap settings. The exact control depends on whether the URL is a static page or a CMS item. After making the change, republish the affected content and confirm the URL no longer appears.

Sitemap choices should follow the site’s wider content structure. A clear SEO taxonomy helps determine which pages deserve independent, indexable URLs and which archives, filters, or thin variations should remain excluded.

What are common Webflow sitemap problems?

• The sitemap contains staging or outdated domain URLs.
• Important CMS items are unpublished or excluded.
• Old URLs remain accessible after a migration.
• Pages in the sitemap redirect or return an error.
• A canonical points somewhere different from the submitted URL.
• Low-value pages are included while important pages are difficult to reach internally.

Is a sitemap enough for Webflow SEO?

No. An XML sitemap is a discovery mechanism, not a replacement for crawlable navigation, internal links, useful content, correct canonicals, fast performance, and sound information architecture. Important pages should still be reachable through the website itself.

An experienced Webflow agency can design the CMS, page hierarchy, redirects, internal linking, and publishing workflow as one scalable system rather than treating the sitemap as an isolated SEO setting.