A sitemap is one of the clearest files on a website. That clarity makes it easy to assign it more power than it has. It’s an inventory of canonical URLs that the publisher wants a search engine to discover and consider.
We use a parent sitemap index with separate families for company pages, services, industries, locations, client work, and articles. The split makes ownership and debugging easier. It also lets us see whether a generated page accidentally entered the wrong public lane.
What inclusion should mean
A private candidate, a redirect alias, a noindex utility route, or a 404 shouldn’t appear simply because a generator knows the path. The sitemap should describe the public search surface, not every file the software can produce.
- The URL returns a successful response.
- Its canonical points to the intended public URL.
- It’s indexable and internally linked.
- The page has a distinct purpose and useful content.
- The release has been verified on the live domain.
Discovery is only the first gate
After discovery, Google still decides whether to crawl, index, canonicalize, and rank the page. Quality, relevance, authority, intent match, and site-wide trust still matter. Sitemap work removes ambiguity; it doesn’t replace competitive content or reputation.
Why we separate sitemap families
A single sitemap can be valid, but separate families make a growing system easier to inspect. Company pages, services, industries, locations, client work, products, and articles have different owners and publishing rules. When one family develops indexing problems, we can inspect it without treating the whole site as one opaque list.
The family split also exposes bad generation decisions. If a noindex sales utility, redirect alias, or unreviewed location candidate appears in a public sitemap, the release test should fail before Google ever sees it.