Sitemap provider and URL generation of EXT:seo
Check EXT:seo and the sitemap configuration matching the site. In the case of detailed content, a suitable data record provider must also be available.
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: A shop has many new products, but no well-maintained sitemap endpoint. A one-time URL export would become obsolete after the next import.
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.
Provide a regularly generated selection of final public URLs. Check new, removed and excluded products after a normal data update.
Derogations and scope
A small, well-linked website can be found without a sitemap. A sitemap does not replace meaningful internal navigation.
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: Use a reliable URL source instead of any export