How to Find Pages Losing Traffic in Google Search Console (and What to Do Next)
How to Find Pages Losing Traffic in Google Search Console (and What to Do Next)
"Pages losing traffic" means URLs whose Google Search clicks (or impressions) fell when you compare two equal-length windows in the Performance report's Pages dimension — not a vibe from Analytics alone.
A site-level drop and a page-level drop are different jobs. Uniform multi-row decline across many unrelated URLs is usually a window, seasonality, or algorithm effect. A handful of URLs accounting for most of the lost clicks is a page problem.
Understanding Search Console metrics
Clicks count visits from Search. Impressions mean a user has seen (or potentially seen) a link. Average position is the topmost position averaged across queries. CTR is clicks ÷ impressions.
Google documents how impressions, position, and clicks are counted, and how the Performance report groups Pages vs Queries and date filters. The generative AI performance report reports AI Overview / AI Mode impressions with no clicks and no CTR — do not add it to Search totals or you double-count. For quality triage, use Google's people-first content guidance.
Why the Pages dimension comes first
Open Performance → Search results → Pages. Compare two equal windows (last 28 days vs previous 28). Sort by click difference, then inspect impression difference. Queries come after you know which URLs moved.
7-step workflow to find pages losing traffic
- Open Search Console → Performance → Search results
- Set search type to Web unless you have a reason otherwise
- Enable comparison of two equal date ranges
- Open the Pages tab
- Export or scan rows with the largest negative click change
- For each candidate, filter to that page and check Queries, Countries, and Devices
- Write a one-line verdict before editing the page (use the triage table)
Triage table: symptoms, causes, and next actions
| Symptom | Likely cause family | First check | Next action |
|---|---|---|---|
| Clicks down, impressions flat | CTR / SERP competition | Queries + titles | Run the impressions-up / clicks-down diagnostic |
| Clicks and impressions down | Rank or demand loss | Position + query coverage | Update/expand if demand remains; see content refresh |
| Impressions down, still indexed | Fewer eligible queries | Queries tab | Confirm indexing is not the issue before rewriting |
| Sitewide uniform multi-row drop | Window / algorithm / seasonality | How many URLs moved together | Do not rewrite everything today; re-read after the window advances |
| Single URL collapse | Page-specific | That URL's queries | One-line verdict, then action ladder |
| Near-zero visibility / indexing flags | Indexing | Page indexing report | Crawled – currently not indexed |
| Many URLs need verdicts | Corpus sprawl | Export size | SEO content audit checklist |
| Gradual page bleed with stable impressions | Content decay | 28-vs-28 compare | Content decay pillar |
Sitewide drop vs page-level drop
If dozens of unrelated URLs each lost a similar percentage at the same time, treat it as sitewide until proven otherwise. If one or a few URLs explain most of the lost clicks, work those first.
What to do next
Update/expand pages that still have demand. Fix titles/descriptions only for CTR-shaped leaks with real volume. Merge cannibalizing URLs. Check indexing only when the indexing report says so. Use the decay pillar for the refresh loop — never invent a recovery percentage.
Measure before you change anything
Before editing, snapshot clicks, impressions, CTR, and average position for the page's main queries and the date. Re-read the same window length later. Without the before-snapshot you cannot tell a fix from seasonality.
How ClickFlow fits this workflow
ClickFlow reads Google Search Console to surface pages losing traffic, drafts refreshes for review, and measures recovery. AI visibility scans are a separate surface. Pricing: Starter, Essentials $159/mo, and Agency — see clickflow.com.
Honest limits: it does not crawl your site for inventory and does not replace Search Console. Human review before publish is expected.
Frequently asked questions
How do I find pages losing traffic in Google Search Console?
Open Performance → Search results, enable a date comparison with two equal-length windows (such as last 28 days vs. previous 28 days), then click the Pages tab. Sort by click difference to see which URLs lost the most clicks. For each declining URL, filter by that page and check the Queries, Countries, and Devices tabs to understand why the drop happened.
What date range should I compare in Search Console?
Use two equal-length windows. For routine monitoring, compare the last 28 days to the previous 28 days. If you suspect a specific event caused the drop (a site deploy or a confirmed Google update), align your comparison windows around that date. The windows must be the same length or the deltas will be misleading.
How do I tell a page-level drop from a sitewide drop?
Export your page-level data and look at the pattern. If dozens of unrelated URLs each lost a similar percentage of clicks at the same time, the cause is likely external (algorithm change, seasonality, or macro search-demand shift). If your overall traffic is roughly flat but two or three URLs account for nearly all the lost clicks, you have a page-level problem and should diagnose those specific URLs first.
Why can impressions fall while a page is still indexed?
Impressions reflect how often a link to your page appeared in search results, which depends on both your ranking position and how many people searched for relevant queries. A page can be fully indexed yet receive fewer impressions because search demand dropped for its target queries, because it slipped to a lower position where fewer searches reach it, or because a SERP feature now occupies space above organic results.
What should I do first when a page loses clicks?
Before editing anything, write a one-line verdict by filtering to that page in Search Console and checking its Queries, Countries, and Devices tabs. Identify whether the loss is driven by a ranking drop, a CTR decline, a demand shift, or an indexing issue. Then snapshot the page's current clicks, impressions, CTR, and average position so you have a baseline to measure any fix against.
How do I measure whether a traffic-loss fix worked?
Before making changes, record clicks, impressions, CTR, and average position for the page's main queries along with the date. After publishing your fix, wait for at least one full comparison window (28 days minimum) to pass, then pull the same metrics for the same queries. Compare the two snapshots. Without the before-snapshot you cannot distinguish your fix from seasonality or unrelated ranking changes.
The comparison is the work
Open the Pages tab, compare two equal windows, sort by the delta, and write a verdict before you touch anything. That sequence protects you from rewriting pages that did not need it.