One calculator peaked at five clicks and position 26 in late July. I never changed a line of its code. Then it fell to position 43 and one click per week — and I still haven't touched it.
Meanwhile, a different page — one the automation committed to 14 days ago — just had its best week in the series: four clicks, 10.53% CTR, position 21.
Both facts are real. Neither adds up to a clean story. That's what this week looked like in GSC.
Since July 5, a daily Claude Code routine has been improving one calculator page per day. Benchmark update, worked examples, verified external sources, updated dateModified schema. Commit. Repeat.
42 commits later, the queue this week covered: Runway, Ad Spend, Conversion Rate, CAC, LTV, ARR, MRR. Every one of those pages has zero presence in Google Search Console. Not a single impression across all seven.
That part I expected. Pages committed today don't show up in GSC tomorrow. Or next week. The lag between on-page work and Google's response has been a constant in this series.
What surprised me was the pattern on the pages the automation touched weeks earlier — and the one it never touched at all.
The impression calculator is our highest-volume page by impression count — 2,007 impressions in the last 28 days. I haven't committed to that file in over six weeks.
| Week | Clicks | Impressions | CTR | Position | |---|---|---|---|---| | Jul 18–24 | 4 | 555 | 0.72% | 26.4 | | Jul 25–31 | 5 | 664 | 0.75% | 31.5 | | Aug 1–7 | 1 | 474 | 0.21% | 32.7 | | Aug 8–16 | 1 | 475 | 0.21% | 43.4 |
Something changed on or around August 1. The clicks fell from five to one. The CTR dropped from 0.75% to 0.21%. The position has been sliding since — from 31.5 to 43.4, a move of 12 positions over two weeks.
I went back through every commit from July 30 to August 2. Nothing touches ImpressionCalculator.tsx. The sitemap got a batch lastmod update on August 1 — every page's date bumped to August 2026 at once — but I can't confirm whether that caused a recrawl that hurt the page or whether it's coincidence.
The impression calculator has 2,007 impressions in 28 days at the page level. When I pull the query-level breakdown for the same period, I get 25 queries covering 174 visible impressions.
That leaves 1,833 impressions — 91% of the total — in GSC's privacy graveyard. Queries with one or two impressions that don't meet the threshold for disclosure. The bulk of the traffic distribution is invisible to me.
I can see that "impression calculator" (the head term) sits at position 30.3 with 2 clicks and 49 impressions. I can see "calculate impressions from cpm" at position 46.4 with 35 impressions and zero clicks. But I can't see what drove five clicks in one week in late July, because those queries are buried below GSC's threshold.
What I can say: the position on the visible queries (30–47) hasn't moved dramatically. If the position degraded, it happened mostly on the long-tail queries I can't see. The click drop and CTR drop might be a position shift on the invisible majority, not on the queries I'm watching.
This is the same trap as the loan payment calculator in the first post in this series — aggregate position metrics hide a distribution, and the distribution hides the actual behavior.
The book value calculator had no GSC data for the week of July 25–31. Nothing. Not even impressions.
The automation committed to it on August 2: updated the dateModified field from June to August, changed "Last Updated: June 2026" to August, swapped one internal link for an external link to CSIMarket's industry aggregates, and updated benchmark text.