What you’ll need
Before and after CSV: url plus any shared status, title, description, h1, canonical or robots fields. Optional old_url,new_url map and source,target link exports.
Compare two crawl snapshots, account for planned URL moves, and review changes in metadata, directives and links.
Runs on your device · Files stay privateBefore and after CSV: url plus any shared status, title, description, h1, canonical or robots fields. Optional old_url,new_url map and source,target link exports. New here? Start with “Try an example”.
Or paste your data below. You can edit it before running the tool.
Or paste your data below. You can edit it before running the tool.
Or paste your data below. You can edit it before running the tool.
Or paste your data below. You can edit it before running the tool.
Or paste your data below. You can edit it before running the tool.
Before and after CSV: url plus any shared status, title, description, h1, canonical or robots fields. Optional old_url,new_url map and source,target link exports.
Exact URL joins or explicit move mappings compare shared fields. Link sets are compared independently. Missing coverage is separated from confirmed changes.
10,000 page rows per snapshot; 50,000 link rows. Supplied snapshots only: no live crawl, ranking-loss diagnosis or Google-selected canonical.
A redesign may improve the page visually while quietly changing a canonical, dropping a title or adding noindex. This SEO change checker compares two supplied crawl snapshots so you can review those changes explicitly. It is useful for release QA and migrations where some URLs are expected to move. Declared moves are compared as planned mappings instead of being mistaken for unrelated removals and additions.
Export before and after crawl CSVs with a URL column and the shared SEO fields you want to compare. Keep the crawl scope as consistent as possible.
Add an old-to-new URL map for planned moves, and supply link exports if you need to compare internal-link relationships.
Run the comparison and prioritize unexpected directive, canonical, status and metadata changes. Keep the original snapshots with the report for investigation.
Missing rows can reflect crawl coverage rather than deleted pages. A changed field is evidence of a change, not proof of ranking impact. Only shared supplied fields can be compared, and the tool cannot reconstruct values that were absent in one snapshot.
Confirm high-priority findings on live pages with Fetch & Render, then rerun the comparison after a release fix.
10,000 page rows per snapshot; 50,000 link rows. Supplied snapshots only: no live crawl, ranking-loss diagnosis or Google-selected canonical.
It can identify changes in supplied crawl evidence, but it cannot establish a ranking-loss cause. Combine the report with live checks, Search Console evidence and your release history.
A known old-to-new mapping lets the tool compare corresponding pages. Without it, the old URL and new URL can appear as separate coverage changes rather than a planned migration pair.