Sitemap provider and URL generation of EXT:seo
Go to the sitemap from the public site base. Check routing and forwarding before you suspect an error in the XML content.
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: The sitemap index provides 200, but a partial sitemap linked to it provides a login page. The successful index retrieval is not sufficient as proof.
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.
Retrieve index and any relevant part file as an unlogged client. Check the status, XML content and retrieval of these URLs separately.
Derogations and scope
An HTML error page with status 200 is not a valid XML sitemap. Even successful compression must be delivered correctly.
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: Retrieve sitemap index and individual files separately