Sitemap provider and URL generation of EXT:seo
Check the selection rules of the respective sitemap provider against the effective robots specifications. Check page and extension records separately.
Distinguish the page sitemap from data set sitemaps of an extension. Compare the specific XML entry with page properties, language, and the actual generated detail path. A manual change to the XML output will not survive the next rebuild.
Where to check the setting in TYPO3
First, check the sitemap index of EXT:seo via the configured sitemap path or type=1533906435. After that, check the responsible page or record provider. A news record needs a URL generation that matches the detailed route, not just an entry in the XML file.
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 TYPO3
Re-search the same URL for a normal sitemap retrieval and cache update. In the case of data sets, additionally control a second detail URL of the same provider.
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: TYPO3 13.4 with EXT:seo. For other major versions and own extensions, responsibilities may differ; check the actually installed output.
Classify the general error
Definition, system-independent causes and further correction examples: Align sitemap selection with the intention to publish