Sitemap generation of the sales channel
Check Sitemap Selection and Robots Rule in the same sales channel. Contradictions can arise if an extension only changes the side answer.
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: An internal search page with conscious noindex is recorded by the sitemap generator. Sitemap selection and indexing intent do not match.
Sitemap: https://example.org/suche/?q=rad
HTML: <meta name="robots" content="noindex">
Entscheidung: interne Suche bleibt ausgeschlossen → nicht in die Sitemap aufnehmen.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.
If consciously excluded, permanently remove the URL from the generator selection. If noindex is accidental, correct the page default and retrieve both outputs.
Derogations and scope
Remove Noindex not only to pass the sitemap check. For user functions, the exclusion may be correct.
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: Align sitemap selection with the intention to publish