After your change, this page group is pulling ~235 more Google clicks / month — and we can show it wasn’t just the season.
+45% clicks vs the 8 weeks before, while a comparable set of pages you didn’t touch stayed flat (+3%).
| Metric | Before | After | Change |
|---|---|---|---|
| Clicks / mo — changed pages | 520 | 755 | +235 (+45%) |
| Clicks / mo — control pages | 610 | 629 | +19 (+3%) |
| Impressions / mo — changed | 18,400 | 22,100 | +20% |
| Avg. position — changed | 12.3 | 8.1 | ▲ 4.2 |
| CTR — changed | 2.8% | 3.4% | +0.6 pt |
Two of your URLs may be competing for “best running shoes”:
/shop/running-shoes (pos 8) and /blog/best-running-shoes-2026 (pos 14).
Google keeps swapping which one it shows — likely splitting clicks between them.
Worth reviewing the internal links and the intent split — and a canonical only if the blog page
shouldn’t rank independently. Often a consolidation here turns two weak results into one stronger one.
Read-only Google Search Console access or a CSV export · the change date · which pages changed · and 3–10 comparable pages you didn’t touch (for the control). About 5 minutes on your end.
Method. Source: Google Search Console Performance data (your own, read-only). 8 weeks pre vs 8 weeks post deploy. Control = 6 comparable pages — same template, same section, similar baseline traffic, no edits in the window — used to net out sitewide / seasonal movement. Avg. position is directional (GSC averages across queries). No estimates, no third-party scrape.
Made by Max · This sample uses illustrative data; the real report uses your GSC data and your change log.