Sitemap maintenance for online stores

A sitemap tells search engines which pages matter, and Google calls submitting one merely a hint, so keep it simple: live pages in, dead pages out. Let your platform build it, submit it once in Search Console, and check it after every big catalogue change.

Minor4 min read

By Edvinas Ivanauskas How the guides are reviewed

Why this matters

Google Search Central's “Learn about sitemaps” page sets expectations: “A sitemap helps search engines discover URLs on your site”, but “If your site's pages are properly linked, Google can usually discover most of your site.” Its guide to building one is blunter still: “submitting a sitemap is merely a hint”. A sitemap does not rescue a page nobody links to, and it does not hide a page you forgot to delete. It is a list, and a list is only as good as its last update.

The rules that matter for a store fit on a postcard. “All formats limit a single sitemap to 50MB (uncompressed) or 50,000 URLs.” “Use fully-qualified, absolute URLs in your sitemaps.” “Include the URLs in your sitemap that you want to see in Google's search results.” The last-modified date counts only when it is honest: Google uses it “if it's consistently and verifiably (for example by comparing to the last modification of the page) accurate”. A sitemap that stamps today's date on every page teaches search engines to ignore the date.

Most platforms do the building for you. Google's page says “If you're using a CMS such as WordPress, Wix, or Blogger, it's likely that your CMS has already made a sitemap available to search engines and you don't have to do anything.” Shopify and WooCommerce publish one as well. The work that is left is checking that it lists what you actually sell today.

Your Shopping listings come from the product data you submit to Merchant Center, so the sitemap's job is search: helping the same product and policy pages get found in Google Search. It is cheap housekeeping that supports good canonical tags and a clean robots.txt.

The free scan does not grade your sitemap, so it is yours to check: open it in a browser to confirm it loads, and after a big catalogue change spot-check a few pages in it. The checks the scan does run are on the misrepresentation checker.

Typical evidence

Publish a sitemap people and tools can find

A complete, referenced sitemap helps search and maintenance tools discover the public URLs you intend to expose. Generate it from the site, submit it where appropriate, and check that it lists products and policy pages.

sitemap.xmlthin

homepage1

<url> collections4

<url> products0 — missing

<url> policy pages0 — missing

Deep pages discovered by luck, slowly.

sitemap.xmlcomplete

homepage1

<url> collections12

<url> products450

<url> policy pages5

Referenced in robots.txt + submitted in GSC.

Generate it with your platform's tool, reference it from robots.txt with a Sitemap: line, and submit it in Search Console — then confirm it lists products and policy pages, not just the homepage.

The public signals this check looks for:

The sitemap still lists products deleted months ago, so it points search engines at 404 pa…
The sitemap still lists products deleted months ago, so it points search engines at 404 pages.
New collections and products never appear, because the sitemap is a one-off file someone u…
New collections and products never appear, because the sitemap is a one-off file someone uploaded by hand.
Entries use relative addresses such as /products/mug, or the old http…
Entries use relative addresses such as /products/mug, or the old http:// or staging domain.
It lists every filtered and tagged version of a collection instead of the one address you …
It lists every filtered and tagged version of a collection instead of the one address you want found.
Every page carries today’s date as its last-modified date, whether it changed or not
Every page carries today’s date as its last-modified date, whether it changed or not.
robots
robots.txt blocks the sitemap file itself, or the sitemap sits behind a password.

What it looks like once it is right

The platform generates the sitemap, robots.txt points to it, Search Console shows it read without errors, and a spot-check after each launch finds the new products in and the deleted ones gone.

Common mistakes

Common mistake

A hand-built sitemap uploaded two years ago lists 180 products, 60 of them deleted, uses http:// addresses, and dates every entry to the upload day. The new spring collection is not in it at all.

Fix checklist

Open yourdomain.com/sitemap.xml, or the address your platform uses, in a browser and confirm it loads. On most platforms it is an index that links to separate product, collection, page and blog sitemaps.
Open the product and pages sitemaps and spot-check: a few recent products should be there, a deleted one should not, and your returns, shipping, privacy and contact pages should all appear.
If the file was built by hand, replace it with your platform’s generated sitemap or a plugin that updates itself. A hand-made file starts going stale the day after you upload it.
Make sure every URL is absolute, uses https:// and your live domain, and is the address you want shown, not a filtered or tagged variant.
Check that last-modified dates change only when a page does. If every entry shows today’s date, fix the generator or leave the date out.
Add a Sitemap: line to robots.txt, submit the sitemap once in Search Console’s Sitemaps report, and look at that report for errors after a migration.
After a big catalogue change or a platform move, open the sitemap again and repeat the spot-check.

Tell Search Console where the index lives

Reference the sitemap from robots.txt and submit it in Search Console. Use its report to review whether Google has read the sitemap and the URLs it discovered; that is useful evidence, not a guarantee of full coverage.

/sitemap.xmlSuccess

URLs discovered

2 days

last read

robots.txt

Sitemap: https://yourdomain.com/sitemap.xml

New products are discovered in hours instead of weeks, and policy edits are picked up almost immediately.

Questions merchants ask

Does Google Merchant Center need a sitemap?

Your Shopping listings come from the product data you submit, not from a sitemap. A sitemap helps Google Search find your pages. Keep one, because your platform makes it for free, and keep it accurate: live product and policy pages in, deleted ones out.

How many URLs can one sitemap hold?

Google's guide says all formats limit a single sitemap to 50MB uncompressed or 50,000 URLs. Bigger stores split the list into several sitemaps under one sitemap index, which most platforms do automatically.

Should I submit my sitemap in Search Console?

Yes, once, in the Sitemaps report, and look at the report again after a migration or a big catalogue change. Google calls submitting a sitemap merely a hint: it helps discovery, and it does not force every page into search results.

Remediation

Risk signal

A sitemap does not get a page approved or indexed on its own, but a stale one sends search engines to pages that no longer exist. Let the platform build it, check it after big changes, and save your worrying for the pages themselves.

PriorityLow priority on its own — clear it as housekeeping so the record is complete.

EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

Last reviewed 29 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.