Check the Live Sitemap Before Signing Off the Release
A sitemap can export correctly while the live website still serves an older URL list. The task needs a check at the public sitemap address after deployment.
That check should compare the published file with the pages the team agreed to include.
Imagine an export containing 200 URLs. The public sitemap also contains 200, but it still lists a retired service page and omits the new replacement. The totals match. The contents do not.
Before closing the task, check:
• The production sitemap address returns the expected XML.
• Its complete URL list matches the agreed inventory.
• Each intended page type is represented, including a newly published page.
• Deliberately excluded pages remain absent.
• Someone owns the process that keeps the file current.
Start with the sitemap already on the site. It may be an index pointing to several smaller files. Include those files in the comparison so a working index does not hide an outdated section underneath it.
Keep the inventory decision explicit: which service pages, locations, articles or products belong in this release? A crawler's export tells you what it discovered. Compare that list with the pages the site was supposed to publish.
Open a sample of the listed URLs as well. Check that they reach the intended production pages and use the preferred addresses. If the sitemap includes modification dates, those dates should reflect significant page updates; exporting the file again does not make every page newly updated.
For a site that publishes regularly, document how new pages enter the sitemap and how retired pages leave it. An automated generator still needs clear inclusion rules and a check when those rules change.
Keep the public address, inventory comparison and update owner in the release notes. Make the sitemap discoverable through Search Console or robots.txt, and check for retrieval or processing errors. Submission does not guarantee that every listed page will be crawled or indexed.
The 200 vs 200 example is exactly how it slips through. I'd also check that the sitemap URLs match the canonical tags on those pages, those can drift apart too.
Solid checklist. I'd add lastmod: if every release stamps today's date on every URL, Google learns to ignore it. It should only change when the page content changes. Also worth confirming every sitemap URL returns a direct 200, not a redirect.
Exactly. I’d also check where lastmod comes from, a build timestamp can make unchanged pages look newly updated on every deployment. If the CMS can’t supply a reliable date, leaving it out is better than inventing one. A useful QA test: rebuild unchanged pages and confirm their...
Agreed, no date beats a fake one. On static builds I take lastmod from the last git commit that touched the page's content file, so it only moves when the content really changes. Easy to automate, and it passes that rebuild test.
Yep, and that gives you a useful audit trail too. If a lastmod date looks wrong, you can trace it back to the commit behind it and check what actually changed.
The sitemap index point is a sneaky one: a healthy index can easily mask a stale child file. Do you automate that inventory diff in CI after each deploy, or keep it as a manual release-checklist step?
I’d use both. The repeatable part belongs in a post-deploy check: fetch the public index and its child sitemaps, compare the actual URL set with the approved inventory, and report missing or unexpected URLs. The manual step is reviewing intentional changes to that inventory.
Great job, Nick! Local SEO can be underestimated so it's good seeing people thriving from doing it how it's supposed to be done. Looking foward on seeing your next work.
Kajabi Coaching Website Design | Wellness & Mindfulness
A clean, modern Kajabi website concept designed for a mindfulness and wellness coaching brand.
The focus was on creating a calm, professional digital experience that builds trust, communicates coaching services clearly, and makes it easy for visitors to take the next step.
Design highlights:
Minimal, calming visual direction
Clear content hierarchy and navigation
Dedicated coaching service sections
Strategic consultation booking calls to action
Responsive website design approach
Trust building testimonials and service information
The goal was to balance thoughtful design with a user experience that feels welcoming, intuitive, and conversion focused.
Need a professional Kajabi website for your coaching business? Let's connect.