See what changed between two scans
The Changes view compares two scans of your site. It shows which problems are new, which you fixed and which are still open, and what changed on each page.
- columns: new, resolved, still open
- 3
- columns: new, resolved, still open
- page facts compared
- 7
- page facts compared
- finished scans to compare
- Any 2
- finished scans to compare
Reading a comparison
What each label means
Changes puts two scans side by side. Every check and every page gets one of these labels.
- New
A check that fails now but passed in the older scan.
Look here first after a release. Something you changed probably caused it.
- Resolved
A check that failed before and passes now.
Your fix worked. Nothing more to do.
- Still open
A check that failed in both scans.
Open it to see which pages still fail.
- Modified page
A page whose title, description, H1, status, canonical, indexability or word count changed.
Check the change was on purpose. The old value is shown crossed out.
- Added · Removed
Pages found in only one of the two scans.
Make sure removed pages redirect somewhere useful.
What it shows you
Did a release break anything?
Issues
Three columns, New, Resolved and Still open, each check with the number of pages it affects and a link to its report.
Pages changed
Every edited page, with the old value crossed out beside the new one, so accidental edits stand out.
Any two scans
Pick the newer and the older scan. Both health scores show beside the pickers, with the difference.
Search impact
From Basic, with Search Console, how Google clicks to the changed pages did compared with the rest of your site.
Inside the app
Two scans, side by side
New, Resolved and Still open, with both scores in the toolbar.
Click around: it is a working copy of the screen, filled with our test site's data.
Your first visit
Check a release in four steps
- 1
Check which two scans are compared. By default, your latest scan and the one before.
- 2
Read the New column and open anything that hits many pages.
- 3
Check Resolved to confirm your fixes worked.
- 4
Open Pages changed to find the edits behind any new problems.
Included from Hobby up
Changes needs a second scan to compare against. On Free your scans are still kept for 30 days, and you can open any of them from Scan history.
The checks behind this screen
Check categories shown here
These groups of checks feed the numbers on this screen. Each one is explained on the score page.
On-Page
35 checksThese checks look at each page's title, meta description, headings and URL. They flag any that are missing, empty, duplicated on other pages, too long or too short, including pages with more than one H1, because these are the first things search engines read and show.
Crawlability
18 checksYour robots.txt file and your sitemaps tell search engines which pages to visit. These checks read both, and they flag sitemaps that list broken, blocked or duplicate pages, CSS and JavaScript files that robots.txt blocks, and pages that failed to load during the scan.
What this screen is for
The results it is part of
A screen is where you look. These are the things PixyScan does for your site that you see here.
FAQ
Common questions about this feature
Which tiers include Changes?
Hobby, Basic, Pro and Enterprise. On Free your scans are still kept for 30 days, and you can open any of them from Scan history.
Why can't I pick a certain scan?
Only finished scans that measured the same thing can be compared: same branch, same scan type and same coverage. A preview branch is never compared with your live site, or every page would look added or removed.
Can I get alerts about changes?
Yes. Email, Slack or webhook alerts can go out when a scan finishes or fails, the score drops, or a new critical problem appears. From Basic, with Search Console connected and scans run from CI/CD, you can also be told when Google clicks drop sharply in the 3 days after a deploy, about a week later. Set them up in Settings, Alerts tab.
Does it show who made a change?
No. It compares two scans of your live site, not your code, so it cannot name who made an edit. Comparing the scans either side of a release narrows it to that release. From Basic, scans run from CI/CD record the commit or release they ran for, and with Search Console connected each deploy is marked with it on the Search performance trend.
Continue the product tour
Previous and next features
Features follow the order of the app’s menu. See the full list to jump to any of them.
See what is wrong with your site
Add your site and get your score, your to-do list and a fix guide for every problem. Free for one site and 500 pages a month, with no time limit.
Nothing to install · Cancel any time