Sitemap provider and URL generation of EXT:seo
Compare sitemap link generation with current site base and slug. A correct redirect rule alone does not update the created sitemap addresses.
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 calls /performance-alt/, which redirects to /performance/ permanently. The generator uses an outdated URL source.
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.
Take the final desired address directly into the sitemap and test the regular rebuild. Appropriately pass forwarding for old calls.
Derogations and scope
Do not remove the working redirect, just so that the old sitemap URL returns 200.
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: The sitemap should specify the desired destination address