Sitemap Best Practices: Cadence and Split Indexes
By the SEO Health Team · Last updated: 2026-08-16 · We build the SEO Health checker at aimeetup.center. Methods below come from the product’s page audits, sitemap samples, and GSC export math — not from a claimed Google score.
Table of Contents
- TL;DR
- What ops work means in 2026
- Update cadence that matches change
- Split indexes without losing children
- Keep junk URLs out
- Stable URLs and the robots pointer
- How ops work differs from the spec
- Tool landscape
- Implementation steps
- Failure modes
- Frequently Asked Questions
- Conclusion
TL;DR
Direct answer: Sitemap best practices are the operating rules for a live URL inventory: rebuild when the set changes, split with an index before you hit the cap, and keep junk paths out. The 2026 finish is a stratified sample of 50–500 pages, not a nightly rewrite of lastmod.
What you'll learn
- A 47-word definition of sitemap best practices you can quote
- When to rebuild versus when to leave the file alone
- How to split an index by locale, type, or week without orphaning a child
- Which URL classes to exclude every time
- Why a stable path and a robots
Sitemap:line are ops, not decoration
If the inventory is already public, run a sampled site audit. Paste the host. Let the checker parse the map and draw pages from each bucket. Sitemap best practices that stop at “we regenerate weekly” leave the junk rows in the draw.
What ops work means in 2026
Key Definition: Sitemap best practices are the operating rules for a live URL inventory: update when the set changes, split with an index before you hit the cap, and keep junk paths out. The 2026 finish is a 50–500 page sample, not a nightly rebuild.
Quick answer: Sitemap best practices are the operating rules for a live URL inventory: rebuild when the set changes, split with an index before you hit the cap, and keep junk paths out. The 2026 finish is a stratified sample of 50–500 pages, not a nightly rewrite of lastmod. Key terms
| Term | Meaning |
|---|---|
| XML sitemap | The crawler-parseable inventory of canonical URLs. |
| Sitemap index | A list of sitemap files used when one file would exceed the size cap. |
| lastmod | The date the content last changed in a way a crawler should care about. |
| Stratified sample | A 50–500 URL draw on this page that respects locale and type buckets. (#573) |
People type sitemap best practices when a plugin republishes every night, a new locale never got a child file, or Search Console still lists URLs you unpublished last quarter. Those are ops jobs. Markup, size, and hreflang legality live in XML Sitemap Best Practices. How you first write the file lives in Generate Sitemap. This page stays on running the inventory after it exists.
The Sitemap for SEO hub is the method: clean list, then sample. Come here for cadence, splits, and junk.
Key definition, in practice
Ops work is a calendar plus an exclusion list. Rebuild when URLs are created, removed, or canonicalized. Split when a child approaches 50,000 URLs or 50 MB uncompressed. Exclude account, cart, thank-you, print, and facet rows that are not landing pages. Sitemap best practices do not include a timer that rewrites lastmod on unchanged posts.
Update cadence that matches change
Cadence follows the inventory, not the clock. A brochure site that ships two pages a month should not rebuild nightly. A newsroom that ships two hundred URLs a day should rebuild when those URLs go live — and should not stamp today on last year’s archive. Sitemap best practices treat lastmod as a change log you update when the row changed.
When to rebuild versus when to wait
Rebuild after a migration, a locale launch, a mass unpublish, or a canonical cleanup. Wait when you only changed a title on a page that is already listed. Changing the HTML is a page job; it does not require a new file unless the URL itself moved. A nightly sitemap best practices cron that exists “so Google notices us” is lastmod theater with a schedule.
Google’s Search Console sitemap report is where you watch processing errors after a real rebuild. It will not reward you for submitting the same bloated file every Monday.
A practical sitemap best practices calendar for a mid-size catalog is: rebuild on publish and unpublish events, rebuild after a canonical cleanup, and skip the Sunday job that only rewrites dates. If your CMS cannot fire on those events, a daily rebuild is acceptable only when lastmod stays still on unchanged rows. Measure that. Open twenty random rows from last week and this week. If the dates moved and the HTML did not, the calendar is theater.
We apply the same rule in sampled audits: a file that grew by 4,000 facet URLs since the last draw is an ops miss, not a title miss. Sitemap best practices that ignore the delta will keep sampling junk.
Split indexes without losing children
When one file is too large, publish an index that lists children. Update the index when a child is added or retired. A child that exists on disk but is missing from the index is invisible. Sitemap best practices for large sites are index hygiene, not one giant blob.
Extensions in the same file
Google’s note on combining sitemap extensions is the ops rule for image, video, or other extension markup: you may combine supported extensions in one sitemap. That is not a reason to invent namespaces. Keep extension rows on URLs that actually have the asset. An image extension on a thank-you page is still junk.
Split by locale, type, or week
Pick a split you can explain in one sentence: locale, content type, or publish week. Do not split by a hash. When a locale launches, add a child and list it in the index the same day. Sitemap best practices fail when /de/sitemap.xml ships and the index still points only at /en/. Language subdirectory is not a topic column; it is a file-planning axis.
Keep junk URLs out
List every canonical, indexable, 200-OK URL you want discovered. List nothing else. There is no bonus for a longer file. A bloated export is how crawl budget disappears into parameter URLs you will never want in the index. Sitemap best practices are mostly an exclusion list you enforce in the same query that writes <loc>.
What to exclude every time
Omit account, cart, checkout, search-result, print-view, and staging hosts that leaked into production. Omit faceted duplicates unless a facet is a real landing page with unique copy. Omit paginated archives if the first page already covers the set. Omit noindex and redirect hops; list the destination, not the hop. A plugin that cannot exclude those paths is the wrong plugin. Crawl-budget cleanup after the cuts is sitemap SEO optimization, not a ranking ritual.
Keep the exclusion list in the same repository as the generator. When a marketer launches a thank-you URL, it should fail the sitemap best practices check the same day, not after a quarterly cleanup. A written list that nobody runs is decoration. A query that drops utm_, sessionid, /cart, /account, and /print is the actual control.
If a facet is a real landing page — unique copy, a real H1, links you want — keep it. If it is a sort order on the same products, drop it. Sitemap best practices are a judgment on the URL, not a blanket “no parameters ever.”
Stable URLs and the robots pointer
A file that moves every deploy is an ops defect. W3C’s Cool URIs note is still the right habit: pick a path and keep it. /sitemap.xml or /sitemap_index.xml are enough. Do not rotate /sitemap-2026-08-16.xml as the declared address.
RFC 6596 is the document for the canonical link relation. The URL you list in the map should be the canonical you want discovered. If two addresses resolve to one article, list one. Sitemap best practices that list both the slash and no-slash twins waste a row and a fetch.
Cool URIs and slash twins
Pick a trailing-slash policy and stick to it in the file. If the site 301s one form to the other, list the destination. A weekly rebuild that reintroduces the hop is how Search Console stays noisy.
robots.txt as the pointer
Declare the absolute file location in robots.txt (Sitemap: https://example.com/sitemap.xml). The Wikipedia robots.txt article and the original robotstxt.org spec are the documents crawlers still use for that line. Path and “file not found” problems live in Sitemap URL. Fix the declaration before you argue about cadence.
How ops work differs from the spec
Spec work asks whether the document is legal. Ops work asks whether the inventory is current and clean. You need both. Do not paste a linter passing grade over a file that still lists 12,000 filters. Sitemap best practices in the operational sense are the cuts and the calendar. The spec sibling is the markup.
Sampled pages still need an on page seo tool for titles and headings. A clean inventory does not write the H1. If what is sitemap is still the blocker, start at What Is a Sitemap? and come back when the file is live.
Tool landscape
Generators write XML. Search Console shows processing errors. Desktop crawlers walk links. SEO Health parses the map and scores a stratified sample of 50–500 pages. We do not walk a million URLs.
| Job | Typical tool | What SEO Health does |
|---|---|---|
| Write and rebuild | CMS plugin, script | We do not replace your generator |
| Watch processing errors | Search Console | We fail a file that will not parse |
| Full link crawl | Desktop crawler | Out of scope; we sample |
| Sampled site audit | SEO Health | Parse → 50–500 draw → four reports |
A weekly sitemap best practices meeting that only opens Search Console will miss lastmod theater and locale-as-column errors. The sample is the faster first pass.
Use that meeting to read four numbers: child-file count, URLs added, URLs removed, and junk rows the sample still found. If added and removed are both zero and lastmod moved, you ran a vanity rebuild. If junk rows persist, the exclusion list is not in the write path. Sitemap best practices are those four numbers, not a slide that says “sitemap healthy.”
Start the sampled site audit after a real rebuild, not after a cosmetic date stamp.
Implementation steps
- Confirm the sitemap URL in robots.txt.
- Rebuild from the live canonical set when URLs changed — not on a vanity clock.
- Exclude junk in the same query that writes the file.
- Split with an index before you hit the cap. List every child.
- Keep the declared path stable.
- Parse. Stratify. Draw 50–500 pages. Do not take the first N lines.
- Read tech, on-page, compliance, and cluster reports.
- Fix the weakest cluster. Rebuild once. Re-sample the same buckets.
If you still need to generate sitemap output, do that, then apply sitemap best practices as the operating layer. Do not rebuild as a substitute for fixing titles.
After a locale launch, add the child, list it in the index, declare the index in robots, then sample. Skipping any of those four steps is how /de/ stays invisible for a month. Sitemap best practices for launches are a punch list, not a hope that Google discovers the new file.
Once robots and cadence are fixed, re-run the sampled site audit so the four reports update against the cleaned file.
Failure modes
These are inventory failures, not scoring-theater failures.
- Clock-driven rebuilds. A nightly job that rewrites lastmod on unchanged posts looks like sitemap best practices and is the opposite. Crawlers learn to ignore your dates. Rebuild when the set changes.
- Orphan children. A split that writes
/de/sitemap.xmlbut never lists it in the index hides a locale. The sample then looks like a single-language site. - Junk that creeps back. Facets, thank-you pages, and staging hosts re-enter when a plugin reset. Sampling a junk file only proves the junk. Fix the exclusion list before you argue about titles.
None of these are “the checker was unreliable.” They are ops failures. Fix the calendar and the list, then the pages. A rebuild that does not change the exclusion list is not sitemap best practices.
Frequently Asked Questions
How often should I rebuild the file?
Bottom line: When URLs are created, removed, or canonicalized. After a migration or a locale launch. Not on a clock that rewrites lastmod. Then validate and sample. Sitemap best practices do not include a Monday ritual for its own sake.
Should I split by locale or by content type?
Bottom line: sitemap best practices: Pick the axis you can maintain. Locale is a good first split for multilingual sites. Content type is a good first split for a large monolingual catalog. Week-based splits help newsrooms. Do not split by a hash you cannot explain.
What if Search Console shows couldn’t fetch?
Bottom line: Fix the path and the robots line first. That is a sitemap URL problem. Do not rebuild as a substitute for a 404.
Do I need a million-page crawl after each rebuild?
Bottom line: Not first. Parse the map. Draw 50–500 pages across real columns. A full crawl is a later luxury. SEO Health will not pretend to be that crawler.
Can I list noindex URLs just in case?
Bottom line: No. If you do not want the URL discovered, leave it out. Listing it spends crawl budget and confuses the compliance report.
Conclusion
Sitemap best practices are a calendar, an exclusion list, and an honest sample. Rebuild when the inventory changes. Split with an index you keep current. Keep junk out. Declare a stable path. Then run the sampled site audit, read four reports, and fix the weakest cluster before you rebuild again. For the method around the file, stay on Sitemap for SEO.
About the author — SEO Health Team. Reviewer: William Zhu (GitHub). Published and updated 2026-08-16. Credentials appear only here.