XML Sitemap Inventory and Audit Template

What to Include / Exclude

When to use: Decide exactly which URLs belong in your sitemap so you only signal your best, indexable pages.

Include only canonical, indexable, 200 URLs

A sitemap is a shortlist of the URLs you want indexed, so it must contain only pages that genuinely qualify. List a URL only when it is the canonical version, returns a 200 status, and is open to indexing.

Define your inclusion rules:

• [Property] Self-referencing canonical & no noindex directive
• [Property] HTTP 200 only, no redirects (3xx) or errors (4xx/5xx)
• [Property] Single absolute URL, consistent protocol & host

Exclude anything that dilutes the signal:

• [Exclude] Noindexed, robots-blocked, or paywalled pages
• [Exclude] Parameter, filter, and session-ID duplicates
• [Exclude] Non-canonical variants, redirect targets, and 404s

Document the URL source you generate from (CMS export, database query, or crawl) so the list rebuilds the same way each time.

A clean, consistent list tells search engines you maintain quality control. Mixed or broken URLs erode that trust.

Sitemap Structure & Splitting

When to use: Keep large sites within sitemap limits by splitting files and tying them together with a sitemap index.

Respect the 50,000 URL and 50MB limits

Each sitemap file is capped at 50,000 URLs and 50MB uncompressed. Hit either limit and you must split into multiple files referenced by a sitemap index.

Plan your structure:

• [Total URLs] Count canonical, indexable URLs to map file count
• [Split logic] Group by content type, section, or template
• [Naming] Predictable pattern, e.g. sitemap-products-1.xml

Then build the index:

1. Create one index file that lists each child sitemap location.
2. Keep child files under both limits, gzipping large ones to ease transfer.
3. Submit the index URL (not every child) in Search Console.

Grouping by section also makes monitoring easier: if one segment shows coverage drops, you can isolate which sitemap it lives in.

Set [Owner] to keep file counts and splits updated as the site grows past each threshold.

Specialized Sitemaps (Image, Video, News)

When to use: Surface media and time-sensitive content with the right specialized sitemap extensions.

Use extensions for image, video, and news

When standard URL discovery is not enough, specialized sitemaps add structured detail for specific content types. Add them only when you publish that content type.

Image sitemaps help surface visuals tied to a page:

• [Field] Image location URL for each key image on the page
• [Scope] Only meaningful content images, not UI assets

Video sitemaps describe each hosted video:

• [Field] Thumbnail URL, title, description, and content/player URL

News sitemaps cover recent articles for Google News:

• [Field] Publication name and accurate publication date
• [Rule] Include only articles from the last 48 hours

Define which extension applies:

• [Content type] Image / video / news
• [Source feed] Where the media metadata is generated from

Keep media URLs canonical and 200 too: the same quality rules apply across every sitemap type.

lastmod & Accuracy

When to use: Use accurate lastmod values so crawlers can prioritize genuinely changed pages.

Keep lastmod truthful; skip changefreq and priority

The lastmod value tells crawlers when a URL meaningfully changed. Google trusts it only when it is consistently accurate, so it must reflect real content updates, not a build timestamp or a daily blanket refresh.

Google ignores changefreq and priority, so do not rely on them to influence crawling; an accurate lastmod is the signal that matters.

Set your accuracy rules:

• [Source] Pull lastmod from the content's true update date
• [Format] Valid W3C datetime (date or full timestamp)
• [Trigger] Update only on substantive content changes

Avoid common mistakes:

• [Don't] Stamp every URL with today's date on each deploy
• [Don't] Bump lastmod for trivial template or footer edits

If every URL claims to change daily, the signal becomes noise and crawlers learn to ignore it. Set [Validation] to spot-check lastmod against real edit history each release.

Submit & Reference

When to use: Make sure search engines can find your sitemap via robots.txt and Search Console.

Reference in robots.txt and submit in Search Console

Even a perfect sitemap is useless if engines cannot find it. Expose it in two places so discovery is reliable.

First, add the directive to robots.txt:

• [Directive] Sitemap: full absolute URL to your sitemap or index
• [Rule] Use the index URL if you split into multiple files
• [Check] URL is absolute, lives at the domain root, returns 200

Second, submit in Google Search Console:

1. Open the Sitemaps report for the correct property.
2. Enter the sitemap (or index) path and submit.
3. Confirm status reads Success and review discovered URL counts.

Repeat the submission step in Bing Webmaster Tools if Bing traffic matters to you.

Record where the sitemap is referenced under [Locations] so future audits confirm both signals stay live.

Sitemap QA & Monitoring

When to use: Catch coverage errors and stale URLs before they hurt indexing.

Validate, then monitor coverage errors

A sitemap needs ongoing QA because URLs change, redirect, and disappear over time. Build a recurring check so the file stays trustworthy.

Pre-publish validation:

• [Check] Well-formed XML, correct namespace, under 50k URLs & 50MB
• [Check] Every URL returns 200, is canonical, and is indexable
• [Check] No redirects, 404s, noindex, or blocked URLs slipped in

Ongoing monitoring in Search Console:

• [Metric] Submitted vs. indexed URL counts per sitemap
• [Alert] Coverage errors, e.g. redirects or 404s reported
• [Cadence] Review weekly or after each major release

Remember a sitemap aids discovery but does not guarantee indexing: investigate why valid URLs stay unindexed rather than re-submitting blindly.

Assign [Owner] and a [Review date] so monitoring never lapses.

Sitemap Inventory (fill-in)

When to use: One row per sitemap file: its URL source, URL count, indexable share, lastmod accuracy, exclusions, validation result and owner.

Sitemap inventory

Sitemap index: [https://www.example.com/sitemap.xml] · Declared in robots.txt: [yes / no] · Submitted in Search Console: [yes / no, date]

Column notes

• URL source: where the list is generated from. If nobody knows, that's the first finding.
• Indexable 200s: URLs that return 200, aren't noindexed or robots-blocked and are their own canonical. Everything else shouldn't be listed.
• lastmod accurate? Compare 10 URLs' lastmod with the date their main content really changed. Google uses lastmod only when it's consistently and verifiably accurate.
• Excluded on purpose: write down what you leave out and why, so nobody "fixes" it later.

Audit Checks & Completion

When to use: The pass-or-fail checks to run on every sitemap file, based on Google's current sitemap rules.

Audit checks (Google's rules, checked October 2026)

Completion check

• Every sitemap file has an owner and a known URL source: [yes / no]
• Non-indexable URLs listed: [0]
• Search Console sitemaps report shows no errors: [date checked]
• Next audit date: [date]

Remember: submitting a sitemap is a hint. It helps discovery, it doesn't force crawling or indexing.

Worked Example (fictional publisher)

When to use: A filled-in inventory from an invented news-and-guides site, with the two problems the audit found and how they were fixed.

Worked example: Ridgeway Outdoors

Example only. The company, people, URLs and figures are invented to show what a usable, filled-in version looks like.

What changed

The tag sitemap was switched off: it listed 3,950 pages the site itself had marked noindex. The 28 redirected guides were replaced with their final URLs. The product export now uses each product's last real edit date instead of the export time, so lastmod means something again.

Next step

Rebuild a clean file from your verified URL list with the XML Sitemap Generator, and make sure robots.txt declares it with the Robots.txt Generator. Run a website audit to catch listed URLs that redirect or are noindexed. To notify engines that support IndexNow about changed URLs, use Ping Search Engines; Google doesn't use IndexNow, so keep Search Console as your Google route. Need a full technical review? See our SEO & GEO services.