Check a site
SEO change checker for deploys
Save a snapshot of your most important pages, then check again after a release. You'll see exactly what changed: new noindex tags, moved canonicals, broken pages, rewritten titles and a changed robots.txt.
Free · No signup · Reads public pages only
How it works
List up to 20 key pages and save a baseline. It's stored in your browser, not on our servers.
Ship your release, redesign or CMS update as usual.
Come back and press "Check for changes". Serious problems are listed first.
Why releases break SEO
Most traffic drops after a release aren't penalties. They're small technical changes nobody noticed: a staging site's noindex tag that made it to production, a template that now points every canonical at the homepage, a new robots.txt that blocks a folder, or a redirect that sends old URLs to the wrong place.
None of these show up when you click around the site. The pages look fine to people. They only show up to search engines, and often weeks later when traffic has already gone. Comparing a before and after snapshot catches them on the same day.
What the snapshot records
- Status code, redirects and the final address.
- Title, meta description and H1.
- The canonical tag and robots rules, from the page and the X-Robots-Tag header.
- The number of hreflang tags and the types of structured data.
- Word count and a fingerprint of the main text, so edits show up.
- Each site's robots.txt: its status and a fingerprint of its contents.
It doesn't store the pages themselves, only these facts, which is why a baseline of 20 pages fits comfortably in your browser.
How serious is each change?
Serious: a page now returns an error, is set to noindex, has lost its title or H1, has a canonical pointing at a different page, or lost all its hreflang tags. Also a robots.txt that now errors, because Google pauses crawling the whole site while that lasts.
Worth a look: titles and H1s that changed, new redirects, removed structured data, a page whose text shrank by more than a fifth, or robots.txt rules that changed. These are often intentional. Check that they were.
For your info: edited text, new structured data, and pages that recovered. No action needed unless it surprises you.
Making it part of your release routine
Save a baseline when things are known to be good, then run the check right after each deploy. If you work on several machines or with a team, download the baseline file and load it wherever you need it. Save a new baseline once you've reviewed and accepted the changes, so the next comparison starts from the new normal.
Questions people ask
Where is my baseline stored?
Only in your browser's local storage. If you clear your browser data it's gone, so download the baseline file if you want to keep it.
Which pages should I include?
The ones that matter most: your homepage, pricing or product pages, top landing pages, and the articles that bring the most search traffic. Search Console's Pages report shows which those are.
Why does it say the text changed when we didn't edit anything?
Dates, prices, counters and rotating testimonials change the page's text on their own. If the word count barely moved, it's usually one of those.
Does it check how pages look?
No. It compares what search engines read: tags, status codes and text. For visual changes, use a screenshot tool.
Is the SEO change checker free?
Yes. No signup. Up to 20 pages per check.
Want it done for you?
Romeo watches every page, every day
He rechecks your whole site daily, not just 20 pages, and tells you the morning after a release breaks something, with the fix ready for you to approve.
