Measures where clicks actually go on a Google SERP. Pixel position, effective rank, AI Overview citation share, and blue-link CTR.
Users
14
+2 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#178K
#149K among extensions
Version
0.5.1
updated 14 Aug 2026
Users
monthly, 3 months
Latest, 21 Oct 2026:14 usersMove the mouse over the chart for any month
Ratings count
monthly, 3 months
Latest, 21 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About SERP Pixel Share
Rank tracking tells you that you are position 2. It does not tell you that position 2 renders at 1,680 pixels, below an AI Overview and two ad blocks, where it performs closer to position 9.
SERP Pixel Share measures the gap.
WHAT IT MEASURES
Every clickable block on the page, classified: AI Overview, ads, shopping, People Also Ask, organic, sitelinks, featured snippets, video, image packs, local packs, discussions, knowledge panels, top stories.
Pixel geometry per element — vertical offset, height, share of total page height, and whether it falls above the fold at desktop, laptop and mobile.
Effective position: your rank restated as the rank whose clean-SERP CTR matches your suppressed estimate.
AI Overview presence, how much page height it occupies, and which domains it cites — including whether one of them is yours.
Blue-link CTR: your Search Console CTR recomputed over only the impressions where no AI Overview fired. This is the number that answers "did our CTR really collapse, or did the SERP change shape?"
HOW IT SHOWS IT
Inline CTR labels beside each listing on the live results page, plus a summary readout. A side panel carries the full breakdown: metrics, click share by element, a vertical pixel map, and CSV export.
CALIBRATION
Every coefficient in the CTR model is a default meant to be replaced. Connect Search Console and the extension solves feature-suppression coefficients from your own data rather than published averages.
ON ESTIMATES
Estimated CTR is model output, not measured data, and the interface labels it that way everywhere it appears. Connect Search Console to see actual CTR beside the estimate. Keep the distinction when this goes into a client report.
PRIVACY
Nothing about the pages you measure leaves your machine. No analytics, no telemetry, no backend. The only outbound requests are to Google's own Search Console API, and only if you choose to connect it.