XML sitemaps that reflect the live site

Start with the decision, not the metric.

An XML sitemap is a maintained list of preferred URLs that helps search engines discover content. It is a discovery signal, not an indexing guarantee. The useful question is whether the file accurately describes the pages you want visitors to find, not whether it contains the highest possible number of addresses.

Sitemaps can drift away from reality after migrations, CMS imports, or bulk publishing. They may list redirects, removed pages, tracking variations, or pages intentionally marked noindex. That noise makes troubleshooting harder. A clean inventory also gives teams a reliable way to compare publication plans with actual availability.

Turn the idea into a repeatable workflow.

Generate the sitemap from the authoritative source of published content. Use complete preferred HTTPS URLs, and include only the indexable destinations you actually want in search. Separate distinct content types when that makes monitoring easier.
Validate the XML and fetch a sample from every sitemap group. Confirm that listed pages return the expected successful response, are not unintentionally blocked, and agree with their canonical and language annotations.
Use modification dates only when the page's meaningful content changes. Avoid updating every date on each build. Split large files before reaching the documented single-file limits of 50,000 URLs or 50 MB uncompressed.
Submit the sitemap or index in Search Console and monitor processing. When counts disagree, compare exact URL sets rather than relying on totals alone. Investigate missing priority pages and stale entries after every structural release.

Make the next step specific.

Choose one commercially important page or a small, related group of URLs. Record its current state, the user need, the proposed change and the person responsible. Separate evidence from assumptions so you can tell whether the work solved the original problem.

Use the Gavek planning workspace to turn these checks into assigned priorities. The free website snapshot can help inspect initial HTML signals; it does not replace a site-wide crawl, a live ranking data source or an index coverage review in Search Console.

Create your SEO action plan ↗

Avoid the work that creates more work.

Including every discovered URL regardless of canonical or indexing intent.
Changing all lastmod values merely because the site was rebuilt.
Treating successful sitemap submission as proof that every page is indexed.

Measure useful progress.

Listed URLs that are valid preferred indexable destinations.

Priority published pages missing from the sitemap.

Stale entries returning redirects, errors, or noindex.

Keep the comparison period, location, device and data source consistent. Search results and AI answers vary; a single observation is a diagnostic clue, not proof of long-term growth or causation. Connect visibility changes to relevant enquiries, qualified leads or sales wherever reliable first-party data is available.

Questions worth asking.

Can a sitemap replace internal links?

No. It can help discovery, but links provide navigation and contextual relationships for readers and crawlers. Important pages should be reachable through a sensible site structure as well as any sitemap listing.

Should deleted pages remain in the sitemap?

Remove destinations that are no longer part of the indexable site. Keep any necessary redirects active separately and verify their mappings; a sitemap should describe the current preferred content inventory.

Go to the source.

These independent guides are grounded in primary documentation. Platform behavior and search systems can change; consult the linked documentation when implementing a change.

Editorial guidance from Gavek. No ranking guarantees, customer-result claims or endorsement by the referenced platforms.