Go Live

Sitemaps

Edge Delivery Services generates a sitemap automatically at /sitemap.xml when you publish content. Most Commerce storefronts require additional configuration for catalog pages and multi-store setups.

What’s included automatically

Document-based pages appear in the sitemap when you publish them, but product detail pages are excluded by default. If you configure AEM Commerce prerender, it publishes each product page and updates the sitemap automatically.

If your catalog is large enough to exceed the sitemap URL count or file size limit, see Edge Delivery Services limits — indexing and sitemap size for how to split it across multiple sitemap files.

Configure a custom sitemap

Add helix-sitemap.yaml to the root of your GitHub repository to configure multi-language, aggregated, or custom sitemap behavior.

Sitemaps on AEM.live Configure helix-sitemap.yaml for simple, multi-language, and aggregated sitemaps. Includes hreflang, lastmod, and extension options.

Multi-store hreflang

For multi-store setups that need hreflang tags, see SEO indexing — multi-store setups.

Submit your sitemap

Getting your sitemap in front of crawlers takes two independent actions: referencing it in robots.txt so any crawler can discover it, and registering it with Google Search Console for faster discovery and indexing reports. Do the first for every project; the second is optional.

Reference your sitemap in `robots.txt`

If your project doesn’t have a robots.txt file yet, create one in the repository root. Then add a Sitemap directive so crawlers can discover your sitemap automatically.

1
# robots.txt
2
Sitemap: https://www.example.com/sitemap.xml

Register with Google Search Console (optional)

To register the sitemap with Google, open Google Search Console , select your property, go to Sitemaps, enter your sitemap URL, and choose Submit. Google starts crawling the submitted URLs within a few days. Check indexing status and errors in Search Console.

Sitemap submission is part of the launch checklist.