Sitemap settings and published collection items
Check sitemap settings and publish on the correct domain. A stored designer state does not yet occupy an updated public sitemap.
Check whether the automatically generated or a consciously own sitemap is used. Design, archive and publish status of collection items must match the publicly named URLs.
Where to check the setting in Webflow
Control the sitemap setting of the site and the publication of the affected collection pages. Compare an automatically generated sitemap with your own XML. After changes, the published domain must deliver the new status.
Example of this specific finding
Illustrative control case: A shop has many new products, but no well-maintained sitemap endpoint. A one-time URL export would become obsolete after the next import.
follow-up audit in Webflow
After publishing index and retrieve specific entries. For proxy or domain changes, check whether the sitemap actually uses the public host version.
Provide a regularly generated selection of final public URLs. Check new, removed and excluded products after a normal data update.
Derogations and scope
A small, well-linked website can be found without a sitemap. A sitemap does not replace meaningful internal navigation.
Reference: Websites published on Webflow and CMS Collections. Exported HTML or an upstream own proxy layer may have other responsibilities.
Classify the general error
Definition, system-independent causes and further correction examples: Use a reliable URL source instead of any export