Fix forwarding in the XML sitemap
Why Sitemaps should only contain final 200 URLs.
Why sitemaps should only contain final 200 URLs The sitemap is a control signal. It should only contain URLs that are reachable, relevant and meaningfully indexable from an SEO point of view.
The sitemap should specify the desired destination address
After a path change, the sitemap can still contain the redirected old URL. Check if the generator uses outdated slugs, liaisons, or a cached export. What matters is the source of the entries, not just the currently visible XML file.
Example: Recognizing the Result
Illustrative example: The sitemap calls /performance-alt/, which redirects to /performance/ permanently. The generator uses an outdated URL source.
Limit cause and implement correction
Replace the entry with the final relevant URL and create the sitemap again. Check their status and indexing specifications. The forwarding of the old address can be preserved for existing external links. It does not have to be removed just because it is no longer in the sitemap in the future.
What makes you recognize a suitable correction
Take the final desired address directly into the sitemap and test the regular rebuild. Appropriately pass forwarding for old calls.
Classification and boundaries
When is this indication not a clear error?
Do not remove the working redirect, just so that the old sitemap URL returns 200.
Forwarding in the XML sitemap to CMS and cause
Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where forwarding in the XML sitemap has a clear cause or fixed route in the respective system.
Frequent causes of this error
Related SEO Errors
Appropriate Seitenreport checks
This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.