Browser tool · XML · Free to use
Sitemap comparison tool
Compare two sets of XML sitemaps and export added, removed and duplicate URLs.
Practice datasets are fictional and labeled as such. Real store captures are dated observations with their own sources and evidence limits.
Works in your browser
Check your own data
No signup or upload to a server. Up to 10 MB per file and 50,000 rows or URLs per set. Results describe the supplied files only.
Choose comparable snapshots
Add the XML urlset files for the before and after states. Multiple files can represent one set, up to 50,000 URL entries total. If you have a sitemap index, obtain the child files and add those; this tool does not fetch remote URLs or follow indexes. Keep capture dates and environments with your source files.
Compare equivalent scopes: all product child sitemaps before with all product child sitemaps after, for example. Comparing a full site to one category shard would create misleading removals. Empty files, malformed XML and unsupported DTD/entity declarations are rejected rather than treated as zero URLs.
Read changes as inventory evidence
An added URL is present only in the after set. A removed URL is present only in the before set. A duplicate appears more than once in one set. The summary also reports common exact URLs. Case, parameters and trailing slashes remain distinct, because silently normalizing them could hide a migration error.
Sitemap membership expresses a submitted inventory, not an indexation verdict. A removed address may still respond normally and may still be indexed. An added address may be blocked, redirected or noncanonical. Use the differences to select the next inspection, not as proof of search performance.
Worked comparison: one intentional change
The sample contains /old and /keep before, then /new and /keep after. The report returns one removal, one addition and one common URL. If /old permanently moved to /new, confirm the redirect and update internal links. If /new is an accidental duplicate, repair the sitemap generator instead.
In a real migration, join changes to your approved URL map and product IDs. Mark unexplained removals for investigation. A product count that stays the same does not prove that the right products survived; the identity of the changed addresses matters.
Close the comparison with a reviewed decision
Assign each unexpected difference an owner and disposition: intentional, generator defect, URL change awaiting verification or unresolved. Retain the exported difference file beside the snapshots and the release record.
Pass when changes can be explained against the intended inventory and priority URLs have separate response and canonical checks. The browser exports all differences even when the on-page table shows only its first 100 rows.
Sources and maintenance
Check current platform documentation before implementation. Review these instructions when your platform, catalog behavior or source guidance changes.