28-day Search Console window, position 5-30, impressions >= 20, zero clicks. Scored by raw Jev p_max (jev-1.13.0).
| Query | Position | Impr. | Clicks | p_max | Matched page |
|---|---|---|---|---|---|
| va mortgage calculator | 6.7 | 27 | 0 | 0.96 | https://boringtoolskit.com/va-mortgage-calculator/ |
| credit utilization calculator | 8.6 | 27 | 0 | 0.96 | https://boringtoolskit.com/credit-utilization-calculator/ |
| population density calculator | 16.4 | 47 | 0 | 0.95 | https://boringtoolskit.com/population-density-calculator/ |
| youtube monetization calculator | 5.4 | 130 | 0 | 0.93 | https://boringtoolskit.com/youtube-revenue-calculator/ |
| degree day calculator | 8.7 | 242 | 0 | 0.89 | https://boringtoolskit.com/growing-degree-day-calculator/ |
| chinese zodiac and element calculator | 6.7 | 109 | 0 | 0.85 | https://boringtoolskit.com/chinese-zodiac-and-element/ |
| degree day calculation formula | 8.8 | 37 | 0 | 0.65 | https://boringtoolskit.com/growing-degree-day-calculator/ |
| chinese zodiac animal calculator | 7.4 | 96 | 0 | 0.46 | no match |
| tax deductions calculator | 7.7 | 34 | 0 | 0.29 | no match |
| what is vinyl playback speed | 10.7 | 30 | 0 | 0.28 | no match |
| 2.0kpa to psi | 9.0 | 23 | 0 | 0.22 | no match |
| rapidtables | 25.5 | 105 | 0 | 0.06 | no match |
Suppose you run a small personal-finance blog and the report pulls 37 qualifying queries over the 28-day window. Scanning the p_max table, the first row shows 'how to calculate effective tax rate' currently averaging position 11, but it touched position 6 during the period. That gap is the signal the report exists to find: the page has already earned a top-6 placement at least once, so its ceiling is proven and the gap to page one is small. By contrast, a query sitting flat between 19 and 24 with a p_max of 17 has never broken through — it likely needs a substantive rewrite or new internal links rather than a title tweak, so it goes on the backlog, not this sprint.
Assume these numbers are hypothetical, then treat the workflow as the takeaway: pick the two or three queries in the top 8 whose current position and p_max differ by roughly five or more spots, confirm the page actually answers that exact query, align the title and H1 to it, add one concrete element the current page lacks (a worked example, a comparison table, a step-by-step list), and link to it from two or three of your strongest related posts. Mark the report date, re-run it after the next full 28-day window, and compare current position and p_max side by side. Be honest about what this proves: it gives you a before/after baseline, and pages in the 5-30 band generally respond faster to targeted edits than pages ranked 50+, but the size of any gain varies by niche, competition, and SERP layout, and the report cannot promise a specific ranking or click improvement.
Sampling and window problems come first. The 20-impression floor deliberately filters out long-tail and low-volume queries, so never read the report as a complete inventory — read it as the highest-signal slice. The 28-day window can straddle seasonality: pull it the week after a tax-season peak and current positions may look artificially weak, so note known seasonal swings before acting. Search Console also reports position as an average, and for a query with exactly 21 impressions a handful of outlier days can distort both the average and the peak, so a p_max built on a single day — say during a brief competitor outage or a news spike — deserves a manual check before you bet a sprint on it.
Interpretation mistakes are just as common. GSC position does not isolate SERP features, so a query at position 5 behind a featured snippet, a People Also Ask block, and a video carousel may have far less visible click potential than the number implies — eyeball the live SERP for anything you plan to work on. Filter out branded queries, which rank easily and inflate confidence without teaching you anything about content quality. Do not assume linear payoff from moving 12 to 7: if the page mismatches the query's intent, the position gain will not convert into useful visits. Watch for one URL targeting several qualifying queries — edits made for one query can strip terms another depends on. Finally, treat the 28-day re-pull as directional evidence rather than proof: algorithm updates, competitor changes, and normal volatility all confound a single before/after comparison.