Sitemap generation of the sales channel
Compare the sitemap against the current SEO URLs of the sales channel. Consider the generation or cache time of the sitemap.
Check the part files mentioned in the Sitemap index and their up-to-dateness. For self-managed installations, the rebuild depends on the set up update strategy; in SaaS, the sitemap is managed by Shopware.
Where to check the setting in Shopware
Retrieve the sitemap via the specific sales channel domain. Compare affected products with activation and sales channel allocation and check the status of the generated sitemap. A sitemap of another sales channel is not a suitable proof of this URL.
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 Shopware
After a product change, retrieve the affected channel. If the file remains obsolete, check the configured generation instead of manually editing the compressed XML file.
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.
Related: Shopware 6 with Storefront. Self-hosted and SaaS offer different access and configuration options; view your own headless frontends separately.
Classify the general error
Definition, system-independent causes and further correction examples: The sitemap should specify the desired destination address