Compare the sitemap with the publication inventory
Prepare the current public inventory of articles, pricing, categories and language versions, then compare it with sitemap URLs. Look for administration, unfinished translations, nonexistent articles and retired addresses. A valid XML response does not establish correct membership. Check each URL’s intended role and align the preferred-URL policy. Removing an entry and deciding the old URL’s redirect or retirement are separate actions. Sitemap removal alone does not determine every publication or indexing state. Treat the inventory as discovery assistance, not a replacement for the page’s actual content or access control.
Define the change represented by lastmod
Google describes lastmod as the time of a significant page update, with main content, structured data and links among its examples, rather than a copyright-year edit alone. Your application can hold separate generation, check, publication and content-change dates. Decide which record supplies the value instead of filling missing dates with the current build time. Rechecking a price without changing the page should remain distinguishable from an actual correction. The purpose is an explainable date, not maximizing the number of apparently fresh entries. Keep the editorial event and technical generation event separately named in the operating record.
Example: correct pricing in one language first
Suppose Japanese contract guidance is corrected while the English counterpart remains under review. Inspect the changed body and state of each published URL. If a shared product table changes both, account for that effect too. Do not mark unreviewed English prose updated merely to make dates match; assign its actual revision. Conversely, a common table or link change can affect many pages, requiring a judgment about significance on each. Coherent reader-facing conditions matter more than superficial date alignment. This scenario illustrates maintenance reasoning and does not claim we measured incorrect values on a particular deployed website.
Inspect the served file and the served page
Inspect the publicly served sitemap and representative pages, not only generation code. If caching or environment differences leave an older inventory, establish which version was fetched. Compare a new, revised, unchanged and retired page to reveal blanket date updates or missed changes. Follow redirects to the intended final URL rather than accepting a matching string. Check encoding, absolute URLs and any required splitting against current specifications. File availability, correct entries and Google-side processing are separate evidence. Keeping those checks distinct avoids declaring discovery or indexing complete merely because a generated file downloads without an error.
Do not buy tooling from page count alone
A site with thousands of pages does not automatically require a particular paid subscription if it can build a truthful inventory and inspect changes. If a crawler helps reconcile many responses, estimate URLs, saving, comparisons and load. Mark the verified boundary when a free allowance cannot cover the whole set; missing scope is not passing scope. Budget generation, editorial change records, translation follow-through and public verification too. Do not assume newer lastmod values create a ranking gain. Price the missing capability needed to maintain coherent publication and update information rather than paying for a larger report because the page count looks substantial.
Migrate date meaning as well as URL data
Before changing CMS or delivery, retain URL role, significant update date, rationale and the current sitemap. An identically named field in the replacement can mean creation or last save rather than the same editorial event. Hand over examples of edits that do and do not change the date. Verify required access to old outputs or history before retiring the former arrangement. After migration, retest old and new URLs plus revised and unchanged cases, following Google-side processing separately. A newer date is not the outcome. The acceptance condition is an operating process that keeps actual substantive changes represented correctly through future releases.
Official sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- Google sitemap construction and lastmodInformation checked: 2026-10-28
- Search Console performance metrics and setupInformation checked: 2026-10-27
- Screaming Frog pricingInformation checked: 2026-10-28
- About Google Search ConsoleInformation checked: 2026-10-27
- Search Console dimensions and data groupingInformation checked: 2026-10-27
- Screaming Frog SEO SpiderInformation checked: 2026-10-28