Compare two sitemaps before publishing or migrating

Which URLs and metadata actually changed between two versions?

A sitemap describes URLs proposed for crawling. Comparing files checks a publication scope, but does not measure indexing or rankings. Separate the change observed in the file from the checks still needed on the pages.

1. Freeze comparable versions

   Keep before and after files, their origin and coverage. Compare the same type: an index describes child sitemaps; a urlset describes pages. Identify partial extracts.

2. Compare addresses without merging them

   The comparator uses exact XML-decoded loc values. Scheme, host, case, trailing slash and parameters remain distinct. Similar removed and added URLs suggest a migration to investigate, not a proven redirect.

3. Review issues and metadata

   Inspect duplicates and invalid loc values before interpreting totals. For lastmod, identify a significant content change: regeneration alone does not justify a new date. Compare declared hreflang destinations, then check reciprocity on the pages.

4. Check pages and retain decisions

   Check HTTP responses, canonicals and indexing exclusions for affected URLs. Record reasons for intentional removals and an equivalent replacement if one exists. Export the report, assign actions and repeat after corrections.

Compare two XML sitemaps

Files stay in your browser. No upload or requests to contained URLs. The export includes complete URLs: review it before sharing.

Situations and decisions

Typical situations for preparing a check. They do not describe completed assignments or actual observations.

Record to retain

• Origin, filename, collection date and complete or partial scope of both files.
• Full report of added/removed URLs, metadata changes, duplicates and skipped entries.
• HTTP and canonical findings for pages actually checked, with check dates.
• Decision, owner, correction and verification after regeneration.

Official references

• Google Search Central — Build and submit a sitemap
• Sitemaps.org — XML protocol
• W3C — Date and Time Formats

Related protocols

• Crawling and indexing audit
• Prepare a multilingual website migration
• Verify a redirect and a domain change
• Build a multilingual journey acceptance plan

Checks before reaching a conclusion

• Do both files cover the same site and scope?
• Do invalid entries or duplicates explain count differences?
• Is every removal or language change documented?
• Were affected pages checked separately from the XML file?