Overview
Magento 2 builds a standards-compliant XML sitemap out of the box, listing your products, categories, CMS pages, and store home URL. It stops there: no HTML sitemap for shoppers, no fine-grained control over custom URLs, and nothing aimed at the AI crawlers that now shape discovery. A sitemap done right combines the core XML file, a human-readable HTML sitemap, and a deliberate strategy for how both search engines and language models find every page you care about.
The XML sitemap is a discovery aid, not a ranking tool. It tells crawlers which URLs exist and when they last changed, which matters most on large catalogues where deep pages would otherwise be found slowly or not at all.
Turn Magento's sitemap generation on, submit the file to Google and Bing, and treat the sitemap as a living index you regenerate on a schedule rather than a file you make once and forget.
This guide covers what core Magento's sitemap does, where it falls short, why an HTML sitemap earns its place, how sitemaps relate to AI and LLM discovery, and the mistakes that quietly leave pages uncrawled.
What does Magento's XML sitemap do out of the box?
Core Magento generates an XML sitemap that conforms to the sitemaps.org schema, covering four URL types: products, categories, CMS pages, and the store home URL. Each entry can carry a priority and a change frequency, and product entries can optionally embed image references.
You control it in two separate places. The generator and the file itself live under Marketing > SEO & Search > Site Map: this grid is where you create a sitemap record, point it at a filename and path, and click Generate to build the file on demand. The behaviour of what goes into it lives under Stores > Configuration > Catalog > XML Sitemap, where you set the priority and frequency for categories, products, CMS pages, and the store URL independently, add product images, and configure automatic generation.
Automatic generation and file limits
In the Generation Settings group you switch on scheduled generation, pick a standard or batch method (batch is the memory-safe choice for large catalogues), and set a start time and frequency. Magento rebuilds the sitemap on cron, which runs daily by default.
The Sitemap File Limits group caps each file at 50,000 URLs and roughly 10 MB, matching the sitemaps.org limits. When your catalogue exceeds a single file, Magento splits the output and writes a sitemap index automatically.
Robots.txt submission
The Search Engine Submission Settings group has one option: enable submission to robots.txt. Turn it on and Magento adds a Sitemap: line to robots.txt pointing at the file, so any crawler that reads robots.txt discovers the sitemap without a manual submission.
Where does the core sitemap fall short?
The built-in sitemap is solid for the four URL types it knows about. Its limits show up once your store is more than a plain catalogue.
No arbitrary or custom URLs. Custom routes, landing pages served outside the CMS, blog posts from a bolt-on platform, and faceted URLs you want indexed are not included, and there is no per-URL control to add them.
No HTML sitemap. Magento produces the machine-readable XML file only. There is no human-facing sitemap page, which is a missed internal-linking and usability asset.
Coarse CMS control. Every CMS page shares one priority and one change frequency. You cannot say your homepage matters more than a rarely-updated policy page; they are one group.
Nothing for AI or LLM discovery. There is no support for emerging conventions such as llms.txt, and no separate feed shaped for how language models ingest content.
Why add an HTML sitemap?
An HTML sitemap is an ordinary page that links to your important URLs in a readable hierarchy. XML is for crawlers; HTML is for people, and usefully for crawlers too.
It gives shoppers a fallback way to navigate a large store, creates internal links to deep pages that menus miss, and hands crawlers a second, on-page path to your content. On big catalogues those extra links help distribute crawl attention to pages that would otherwise sit several clicks deep.
Core Magento does not build one, so you create it as a CMS page or generate it with an extension, then link it from your footer.
How do sitemaps help AI and LLM discovery?
AI answer engines and their crawlers discover pages much the way search engines do: through links, sitemaps, and public web data. A complete, current XML sitemap is therefore as useful for AI discovery as for Google, because it is often the fastest route to every deep page.
A newer idea is llms.txt, a proposed plain-text file that points AI systems at your most important content. Treat it as experimental. It is a community proposal, not a standard any major search engine or AI provider has committed to consuming, so publishing one is low-cost but not something to expect measurable traffic from yet. The dependable work is unchanged: a clean sitemap, strong internal linking, and pages structured so a model can extract a self-contained answer.
The sitemap gets crawlers to the page; the page's structure decides whether it gets cited. See the sibling guide on helping AI agents find your store for that content side.
What priority and change frequency should you set?
Less than most guides claim. Google has publicly stated that it ignores the priority and changefreq values and relies on its own signals, so an elaborate scheme is wasted effort.
Magento's defaults are sensible and worth leaving alone: products at priority 1.0, categories at 0.5, CMS pages at 0.25, the store URL at 1.0, all with a daily change frequency. What actually helps is accurate lastmod data and a regeneration schedule that keeps it fresh, so crawlers see genuine change signals. Spend your effort on coverage and freshness, not on tuning numbers most crawlers disregard.
What are the common mistakes?
Mistake 1 - A stale sitemap
Generating the sitemap once and never again is the most common failure. New products never appear, deleted ones linger, and lastmod dates freeze. Enable scheduled generation so the file rebuilds automatically.
Mistake 2 - Blocking the sitemap in robots.txt
A robots.txt rule that disallows the sitemap path, or blocks the directory it sits in, makes the sitemap unreachable. Check that robots.txt permits the file and, ideally, references it with a Sitemap: line.
Mistake 3 - Orphan pages left out entirely
The sitemap only lists what Magento knows to include. Custom landing pages, blog URLs, and important faceted pages can be absent, so they rely entirely on internal links to be found. Add them through an extension or a supplementary sitemap.
Mistake 4 - Submitting once and walking away
Adding the sitemap to Search Console and Bing Webmaster Tools once is not the end. Check the coverage reports periodically for pages excluded, discovered-but-not-indexed, or errored: that is where a broken sitemap first shows up.
Advanced: coverage, indexes, and submission
Three refinements matter once the basics are running.
Split and index deliberately. On very large catalogues, let Magento's batch generation produce a sitemap index referencing multiple child files. A clean index makes it easy to see in Search Console which segment of the catalogue has coverage problems.
Submit to Search Console and Bing. Add the full sitemap URL under Sitemaps in Google Search Console, and do the same in Bing Webmaster Tools, which also feeds other engines. The robots.txt Sitemap: line helps passive discovery, but explicit submission gives you the reporting.
Keep XML and HTML in step. Generate the HTML sitemap from the same source of truth as the XML file so the two never disagree about which pages exist.
Where Moogento Fits
Core Magento covers the four standard URL types and leaves the rest to you. SiteMap extends that: it brings in the custom URLs core ignores, adds a human-readable HTML sitemap alongside the XML one, and supports discovery files aimed at AI and LLM crawlers, so a single tool covers shoppers, search engines, and answer engines from one configuration.
The point is coverage: a sitemap only helps for the pages it lists, and the pages core leaves out are often the landing pages you most want found.
Real-World Impact
Stores that switch from a stale, catalogue-only sitemap to a fresh, complete one usually see deep and newly-added pages get crawled and indexed faster, because the sitemap is doing its actual job: surfacing URLs that internal links alone would reach slowly.
The effect is clearest on large or fast-changing catalogues, where the gap between "product published" and "product crawled" is otherwise widest. Because crawl behaviour depends on your site's authority and size, measure the change in your own Search Console coverage report rather than expecting a fixed figure.
FAQs
Does Magento 2 have a built-in XML sitemap?
Yes. Magento 2 generates a standards-compliant XML sitemap covering products, categories, CMS pages, and the store home URL. Configure it under Stores > Configuration > Catalog > XML Sitemap and generate the file from Marketing > SEO & Search > Site Map.
How do I enable automatic sitemap generation in Magento?
Under Stores > Configuration > Catalog > XML Sitemap, open the Generation Settings group, set Enabled to Yes, and choose a start time and frequency. Magento then rebuilds the sitemap on cron, which runs daily by default.
Does Magento create an HTML sitemap?
No. Core Magento only produces the machine-readable XML sitemap. An HTML sitemap, a readable page linking your important URLs, has to be built as a CMS page or added with an extension, then linked from your footer.
Do priority and changefreq values in the sitemap affect Google rankings?
No. Google has stated it ignores the priority and change frequency values and uses its own signals instead. Magento's defaults are fine to leave as they are; accurate last-modified dates and regular regeneration matter far more.
How do I submit my Magento sitemap to search engines?
Add the full sitemap URL under Sitemaps in Google Search Console and in Bing Webmaster Tools. Enabling submission to robots.txt in Magento also lets crawlers discover the file automatically, but explicit submission gives you the coverage reporting.
Why are some of my pages missing from the Magento sitemap?
The core sitemap only includes products, categories, CMS pages, and the home URL. Custom landing pages, third-party blog URLs, and faceted pages are not added automatically, so they can be absent entirely. Add them with an extension or a supplementary sitemap.
Next Steps
- Enable automatic generation under Stores > Configuration > Catalog > XML Sitemap
- Generate the file and confirm robots.txt does not block it
- Submit the sitemap in Google Search Console and Bing Webmaster Tools
- Add an HTML sitemap and cover the custom URLs core leaves out
- Review the coverage report regularly and regenerate on a schedule
The highest-value move is turning on scheduled generation and submitting the file: a fresh, submitted sitemap is the single change that gets new pages crawled fastest.
Related reading: Magento 2 SEO Guide, How AI Agents Discover, Rank, and Recommend Magento Content, and Writing Magento Product Descriptions at Scale, With AI.