Key takeaways
- An XML sitemap audit checks that the sitemap lists only indexable, canonical URLs that return 200.
- Google's limits: 50,000 URLs or 50MB uncompressed per sitemap; an index file can list up to 50,000 sitemaps.
- Google ignores priority and changefreq and uses lastmod only when it is consistently accurate.
- Read the Sitemaps report in Search Console, then filter the Page indexing report by sitemap.
An XML sitemap audit is one of the checks we run on every client site we take on through white label SEO. It matters most on big sites: earlier in our careers we managed SEO for a US directory with more than 70,000 location pages, and today we supervise online stores with millions of products, where the sitemap is often the only way to see what the platform thinks exists. This guide covers what to check and how to report it. It is a focused part of the technical SEO audit checklist.
What is an XML sitemap audit?
An XML sitemap audit compares the URLs in a site's sitemaps with the URLs the site should have indexed. You check that each listed URL returns 200, is indexable and canonical, that important pages are not missing, that the files are valid and within limits, and how Google reports them in Search Console.
Google's sitemap overview sets expectations: a sitemap helps search engines discover URLs, but it "doesn't guarantee that all the items in your sitemap will be crawled and indexed". The audit makes the sitemap a reliable signal; it does not force indexing.
What should you check in a client sitemap?
Check four things: the files, the URLs, coverage and dates. Files must be valid UTF-8 XML within Google's limits. URLs must be absolute, return 200, be indexable and canonical. Coverage means every important page is listed and nothing junk is. Dates mean lastmod reflects real content changes, not every deploy or copyright update.
| Check | What good looks like | Common problem |
|---|---|---|
| Status codes | Every URL returns 200 | Redirects and 404s from old URLs |
| Indexability | No noindex, no robots.txt block | Noindex tag pages, filtered URLs |
| Canonical | Each URL is its own canonical | Parameter or variant URLs listed |
| Coverage | All key pages listed | New templates or categories missing |
| Format | UTF-8, absolute URLs, valid XML | Relative URLs, unescaped characters |
| Size | Under 50,000 URLs and 50MB uncompressed | One huge file on large catalogs |
| lastmod | Matches real content changes | Same date on every URL |
The format rules come from Google's build and submit a sitemap page: one sitemap is limited to 50MB uncompressed or 50,000 URLs, it must be UTF-8 encoded, and it should use fully qualified absolute URLs, generally the canonical ones. A crawler makes the URL checks fast. In Screaming Frog, enable crawling of linked XML sitemaps and run crawl analysis, and the Sitemaps tab lists non-indexable URLs in the sitemap, crawled URLs not in any sitemap, sitemap URLs with no internal links, and files over 50,000 URLs or 50MB. Pages listed in the sitemap but not linked internally are a separate problem we cover in orphan pages SEO.
How do you find sitemap errors in Search Console?
Open the Sitemaps report. Each submitted sitemap shows a status: Success, Has errors or Couldn't fetch, plus the last read date and discovered pages. Open a sitemap to see its errors. Then use the Page indexing report filtered by that sitemap to see how many listed URLs are indexed and why the rest are not.
Google's Sitemaps report help lists the usual causes. Fetch errors include a robots.txt block, a 404, temporary server problems or an unresolved manual action. Parsing errors include invalid dates or tags, URLs outside the sitemap's directory or domain, compression problems, too many URLs and sitemap index files nested inside other index files. Two details clients often get wrong: submitting needs owner permission (otherwise list the sitemap in robots.txt), and deleting a sitemap from the report does not make Google forget it or its URLs. For the indexing side, the Page indexing report sitemap filter is the best view; we explain how to triage it in our page indexing report guide.
Does Google use lastmod, priority and changefreq?
Google ignores priority and changefreq. It uses lastmod only when the value is consistently and verifiably accurate, meaning it matches the last significant change to the page: the main content, structured data or links. A site that stamps today's date on every URL teaches Google to ignore its lastmod values altogether.
This is straight from the Google sitemap guide, which also says a copyright date update is not a significant change. In the audit, sample ten URLs, compare lastmod with what really changed, and ask the developer how the field is generated. If it comes from the deploy time, recommend tying it to content edits or removing it.
When does a client site need a sitemap index?
When it has more than one sitemap, which in practice means any site over 50,000 URLs or with separate sitemaps by type, such as products, categories, posts and locations. A sitemap index lists the child sitemaps so you submit one file. Splitting by template also makes Search Console reports far easier to read.
Google's sitemap index guide allows up to 50,000 loc tags in one index and up to 500 index files per site in Search Console. Child sitemaps must be on the same site as the index, in its directory or deeper, unless cross-site submission is set up. Index files cannot list other index files.
How should the sitemap audit be reported to the client?
Report it as a short list of fixes with counts: how many sitemap URLs redirect, return errors, are noindex or are not canonical, and how many important pages are missing. Include the Search Console status of each file and a proposed sitemap structure. Then recheck the Sitemaps and Page indexing reports after the fix ships.
- Inventory: list every sitemap and index file, how it was found, and its Search Console status.
- Counts: non-200, noindex, non-canonical and duplicate URLs per sitemap.
- Gaps: important crawled pages missing from all sitemaps.
- Structure: proposed split by page type with a single index file.
- lastmod: how it is generated and whether it can be trusted.
- Follow-up date: recheck Search Console two to four weeks after release.
Our white label SEO audit includes this section under your brand. Or book a 30-minute call.
Frequently asked questions
Should images and videos go in the main sitemap?
They can be added as extensions to page entries or as separate sitemaps; the Sitemaps report does not show data for them yet. Check that the files are accessible and listed correctly, and test the pages with URL Inspection to confirm Google can find them.
Do small sites need an XML sitemap?
Not always, but it rarely hurts and makes new pages easier to monitor in Search Console. Include only canonical, indexable pages, and keep the sitemap updated automatically if possible. This helps Google discover new content faster and makes indexing problems easier to spot.
Should paginated or filtered pages be in the sitemap?
List only pages you want indexed. Filter combinations and internal search pages usually stay out. Keeping the sitemap focused helps Google spend time on the pages that matter most. Make sure the URLs match the canonical versions and return a 200 status code.
Where should the sitemap live?
At the site root is simplest, because it can then cover every URL on that host. List it in robots.txt and submit it in Search Console, so search engines find it easily. Sitemaps in subfolders can only include URLs from that folder and below.
Can the CMS plugin handle the sitemap alone?
Usually, but someone still needs to check what it includes after each template or plugin change. Make sure it excludes noindex pages, redirects and duplicate URLs, and that new content appears correctly. Regular checks catch errors before they affect indexing.
Want these agency guides first? Choose White Label SEO LATAM as a preferred source on Google, and my articles are more likely to show up for you in Top Stories.
Follow on GoogleAdd as a preferred source