Sitemap provider and URL generation of EXT:seo
Assign the entry to the page or record provider of the sitemap. A deleted news record and a moved page have different sources of care.
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 /product/expiration model/, this URL provides 404. The product was either deliberately removed or disappeared due to a routing error.
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.
Upon final removal, take the record from the sitemap selection. In the event of unintentional unreachability, restore the URL or set a suitable final destination.
Derogations and scope
A deleted page may correctly deliver 404. The contradictory inclusion in the sitemap is the part to be checked here.
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: Differentiate deleted and accidentally missing pages