Sitemaps
Edge Delivery Services generates a sitemap automatically at /sitemap.xml when you publish content. Most Commerce storefronts need additional configuration for catalog pages and multi-store setups.
How automatic sitemap generation works
Section titled “How automatic sitemap generation works”Document-based pages are added to the sitemap when you publish them.
Product detail pages are not published documents, so they are not included in the sitemap by default. If you configure AEM Commerce prerender, it publishes each product page as overlay content and updates the sitemap automatically. Without prerender, add a custom helix-sitemap.yaml that sources product URLs from your catalog.
Configure a custom sitemap
Section titled “Configure a custom sitemap”Add helix-sitemap.yaml to the root of your GitHub repository for multi-language, aggregated, or custom sitemap configurations.
For configuration examples — simple sitemaps, multiple language sitemaps with hreflang, and aggregating multiple indexes into one file — see the full reference on AEM.live:
Multi-store setups
Section titled “Multi-store setups”Add hreflang attributes to your sitemap for storefronts that support multiple languages or locales.
See SEO indexing — multi-store setups for the hreflang configuration steps that apply to your Commerce storefront.
Submit to Google Search Console
Section titled “Submit to Google Search Console”After generating your sitemap, submit it to Google Search Console.
Also add your sitemap URL to robots.txt so other crawlers can find it automatically:
Sitemap: https://www.example.com/sitemap.xmlIf your site uses multiple sitemap files, reference each one in robots.txt or create a sitemap index file at /sitemap-index.xml that lists them all.
Sitemap submission is also part of the launch checklist — verify it alongside other SEO tasks before go-live.