Sitemap configuration and actual generation
Compare the sitemap of the respective store view with effective exclusion rules. Extensions can change robot outputs without adjusting sitemap selection.
Under Marketing › SEO & Search › Site Map, check the generated file and its path as well as the associated store context. The configuration and the last successful rebuild are different things.
Where to check the setting in Magento
Under Marketing → SEO & Search → Site Map, check the sitemap assignment to the Store View. Check the creation time, file path and accessibility of the registered products. In the case of automatic generation, the responsible cron run must also work.
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 Magento
After a product change, create a new file or check the schedule. Compare the public sitemap with active product status and reachable target URLs.
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: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
Classify the general error
Definition, system-independent causes and further correction examples: Align sitemap selection with the intention to publish