Sitemap configuration and actual generation
Compare the time of creation of the store sitemap with changed URL keys and rewrites. The new assignment must also arrive in the sitemap.
Under Marketing › SEO & Search › Site Map, check the generated file and its path as well as the associated store context. The configuration and the last successful rebuild are different things.
Where to check the setting in Magento
Under Marketing → SEO & Search → Site Map, check the sitemap assignment to the Store View. Check the creation time, file path and accessibility of the registered products. In the case of automatic generation, the responsible cron run must also work.
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 Magento
After a product change, create a new file or check the schedule. Compare the public sitemap with active product status and reachable target URLs.
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: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
Classify the general error
Definition, system-independent causes and further correction examples: The sitemap should specify the desired destination address