Sitemap

The demo store combines sitemap files generated by Shopware with a sitemap for static routes owned by the Frontends application.

Link:

http://<your_domain>/sitemap.xml

Admin sitemap

/server/routes/sitemap.xml.ts

This route creates a sitemap index from the files returned by the Store API /sitemap endpoint. Those files contain dynamic Shopware pages such as:

• Product pages
• Category pages
• CMS pages

Shopware owns the contents of these files. The Frontends route receives their filenames and does not download or rewrite every URL.

Shopware-generated sitemaps prefer the canonical SEO URL when one exists. A technical URL such as /detail/{id}, /navigation/{id}, or /landingPage/{id} is a valid fallback only when no canonical SEO mapping is available.

More about the Shopware sitemap can be found here.

Frontends sitemap

/server/routes/sitemap-local.xml.ts

This sitemap contains static pages declared by the Frontends application. Each static page should be added manually to /server/sitemap.ts.

The demo route excludes technical Shopware URLs from this local sitemap and logs a warning. Dynamic product, category, and landing-page URLs belong in the Shopware-generated sitemap instead.

Detect and clean up technical sitemap URLs

Inspect the sitemap index and every referenced sitemap file for URLs whose path starts with:

/detail/
/navigation/
/landingPage/

If a technical URL has a canonical SEO mapping, it should not be published in the sitemap. Determine which system generated it before applying a fix:

• For a custom Frontends sitemap, load authoritative SEO URL data and publish the seoPathInfo value.
• For a Shopware-generated sitemap, verify SEO URL generation and indexing, regenerate the sitemap, and clear sitemap or CDN caches.
• If no canonical SEO mapping exists, keep the technical URL as the only available route.

After cleanup, verify that sitemap URLs return 200 directly. A sitemap should not rely on redirects for canonicalization, even though Frontends redirects a mapped technical request to protect clients when an outdated URL is crawled.

Do not use robots.txt to canonicalize sitemap URLs. Blocking a technical URL can prevent crawlers from observing its redirect and delay index cleanup.