Sitemap settings and published collection items
Compare sitemap recording and effective robots output of the published page. An additional noindex in the custom code can pass the sitemap setting.
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: An internal search page with conscious noindex is recorded by the sitemap generator. Sitemap selection and indexing intent do not match.
Sitemap: https://example.org/suche/?q=rad
HTML: <meta name="robots" content="noindex">
Entscheidung: interne Suche bleibt ausgeschlossen → nicht in die Sitemap aufnehmen.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.
If consciously excluded, permanently remove the URL from the generator selection. If noindex is accidental, correct the page default and retrieve both outputs.
Derogations and scope
Remove Noindex not only to pass the sitemap check. For user functions, the exclusion may be correct.
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: Align sitemap selection with the intention to publish