A large sitemap needs a predictable split

What to change

As an inventory grows, the supplier may split it into connected files. The owner needs assurance that the split preserves every intended route exactly once and remains publicly retrievable. Ask for a boundary test using more entries than the next release requires, plus a combined route count across the resulting files. Confirm current platform limits from official documentation rather than copying an old threshold into the acceptance criteria.

A worked example

Illustrative example

Illustrative test: Build a synthetic inventory that crosses the configured split boundary.

How to check the result

Every route appears once across valid publicly reachable child files.

A mistake to avoid

Testing only the current small inventory misses boundary failures.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordConfirm the current limits in the search engine's official documentation.Test the generator beyond the expected publication volume.Verify all child files are reachable from the sitemap index.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.