See how your fixed pages did in Google
Connect Google Search Console with read-only access. After a fix, PixyScan compares Google clicks to the fixed pages with the rest of your site: 28 days before and 28 days after. You read one plain sentence.
Does this sound familiar?
You fixed 40 pages. Did it matter? An audit can tell you they are fixed. It cannot tell you what happened next.
- You report “40 pages fixed” and get asked what it did for traffic. You have no answer.
- Clicks went up after your fix, and also after a Google update. A chart alone cannot tell the two apart.
- A release went out on Tuesday and clicks fell on Thursday. Nobody connects the two for weeks.
How it works
How it works, in three steps
After a fix, PixyScan compares Google clicks to the fixed pages with the rest of your site.
- Step 1
Connect Search Console
In the site's Settings, open the Search Console tab, connect your Google account and choose the property. Access is read-only, and PixyScan never changes anything in Search Console.
- Step 2
Fix, then scan
Each production scan is compared with the one before. Every check that stopped failing on some pages becomes a fix to measure.
- Step 3
Read the result
PixyScan counts clicks for 28 days before the scan, waits 7 days for Google to recrawl, then counts the 28 days after. An early signal shows at 14 days, and the final result after about five weeks.
What you get
What you get with it
You see how the pages you worked on did afterwards, in one plain sentence, without building a spreadsheet.
- 01
One plain sentence for each fix
A result reads like this: “After this change, these pages did 15% better than the rest of the site.” Regressions are measured the same way, so you also see how pages did after a problem appeared.
- 02
Deploys marked on your clicks trend
Every production scan is marked on the Search performance trend. A deploy from your pipeline shows its commit and branch, and you can filter the trend to deploys only.
- 03
An alert when clicks drop after a deploy
PixyScan compares Google clicks in the 3 days after a production deploy with the same days of the previous 4 weeks. If they fall at least 25% from a usual level of at least 100 clicks, and by more than the site's normal swing, you get one alert about a week later.
- 04
Clicks next to every page and problem
The Pages table and each issue's affected pages show Google clicks and impressions for the last 28 days. Sort by them to fix the busiest pages first.
Which tiers include it
Basic, Pro and Enterprise, with Google Search Console connected. Not on Free or Hobby.
- Search Impact and Search Console data start on Basic.
- Search Console history is kept for 6 months on Basic, and 16 months on Pro and Enterprise.
- Deploy markers and the traffic-drop alert also need scans from your CI/CD pipeline, which Basic includes.
- A result needs at least 3 matched pages, and 100 impressions on them in the 28 days before.
What it doesn’t do
- It is a comparison with the rest of your site, not proof of cause. Google updates, seasons and other changes move the numbers too.
- Web search only. Image, Video, News and Discover figures are not measured.
- Pages are matched to Google's data by address. Redirects are not followed.
- No Google Analytics, so no sessions, conversions or revenue.
- It never changes your score, your issues or their order, and it cannot fail a build.
Why use it
When it helps
Everyday moments where it saves you time or catches a problem early.
Report on the work, not only the list
Next to “38 pages fixed”, show how those pages did in Google against the rest of the site over the same weeks.
Find the release behind a drop
Deploys are marked on your clicks trend with their commit. Open a marker to see the branch, the score change and the issues fixed and new.
Fix the busiest pages first
Sort an issue's affected pages by Google clicks, and start with the pages people actually land on.
Where to find it in the app
Take the product tourExplore
Search performance
Connect Google Search Console and this view shows your clicks, impressions, click-through rate and average position, by page and by search query. Your scans sit on the same trend, so you can see what happened to traffic after a fix.
Monitor
Changes
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.
Understand
Site overview
The Overview is the first view you see for a site. It shows your health score, what changed since the last scan and where the problems are. Click any number to see the detail behind it.
Questions
Common questions
Short answers about tiers, setup and limits.
Does a result prove my fix caused the change?
No. It shows how the pages you changed did compared with the rest of your site over the same days. Comparing with the rest of the site takes out what happened everywhere at once, such as a season or a Google update, but other things can still move a page's clicks.
How long until I see a result?
An early signal shows once 14 days of the after window have data. The final result is ready when all 28 days are in, about five weeks after the scan.
Why does a fix say Not enough data?
A fix cannot be measured when fewer than 3 of its pages have Search Console data, when those pages had under 100 impressions in the 28 days before, when your tier's history does not reach back far enough, or when the connection was interrupted.
Which tiers include Search Impact?
Basic and above, with Google Search Console connected to the site. Free and Hobby show a locked card instead.
Does search traffic change my health score?
No. Search Console data never changes your score, your issues or their order.
Will it warn me if a deploy hurts traffic?
Yes, if you deploy through CI/CD. If Google clicks in the 3 days after a production deploy fall at least 25% below the same days of the previous 4 weeks, you get one alert about a week later. It tells you clicks fell, not why.
Can PixyScan change anything in my Search Console?
No. The connection is read-only. PixyScan only reads your performance data.
Other features
All featuresAI readiness
Every scan scores how well AI tools can read your site, and shows which AI bots you allow or block.
ReadMCP server
Connect your AI assistant to PixyScan, so it answers from your real scan and can test its own fix.
ReadThe audit and the score
PixyScan checks every page against 200+ search, AI and technical checks and gives your site a health score out of 100.
ReadSee 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