How to find declining pages in Search Console before the traffic is gone

Open Search Console. Go to Performance, then Pages. Change the date to Compare, select Last 3 months vs Previous 3 months. If your product is seasonal, use the same months year on year instead.

Tick Clicks, Impressions, CTR and Position. Sort by Clicks Difference, smallest first. This sends the steepest fallers to the top. The default comparison is the last 28 days against the 28 before. Three-month windows smooth noise for small sites.

Open each declining page in a new tab. You will diagnose them one by one by reading their queries. Do not jump to rewrites yet.

You may see more impressions but fewer clicks. A page can be shown more often while dropping from position 5 to 12. Average position is the mean over all impressions, so a page can average 8 while appearing at 3 and at 40. CTR is clicks divided by impressions, so it falls when the page slips or a feature takes the click.

An impression is counted when a link to your page appears on any loaded results page for web search, even if the user did not scroll to it. This is why rising impressions can mask a quiet loss of placement. Sorting by lost clicks cuts through that.

1. 1

   Open Queries for the falling page

   On the page detail, click Queries. Stay on the same date comparison.

2. 2

   Sort by Impressions Difference

   If the biggest queries lost impressions across the board, demand fell. If impressions held but average position worsened, your page fell.

3. 3

   Scan the results pages for the top queries

   Click the query, then the search icon to see the current results page. Note new features: AI answer, PAA, a carousel, a new video row, or fresher dates.

4. 4

   Check query coverage

   Some rare queries are omitted in Search Console. Do not chase ghosts. Focus on the few queries that drive most of the clicks for that page.

Worked example: /guides/getting-started lost 120 clicks. The query “yourproduct setup guide” shows steady impressions, position slipped from 4.3 to 9.8. That is your page falling. The query “yourproduct 2023 pricing” shows impressions down to near zero, demand moved to “yourproduct 2026 pricing”. That is demand moving on.

• If core queries lost impressions and position held, hold your nerve. There is less to win. Watch again next month.
• Check if the topic moved. If “yourproduct 2023 pricing” died, update /pricing to target “yourproduct pricing” without a stale year in the title.
• Find adjacent demand. If “how to export from yourproduct” fell, see if “yourproduct migrate to csv” now dominates the results page. Add a clear section to the canonical page that serves that intent.

A fixed page here often means a steadier, broader title and a section that answers the phrasing people now use. Keep the same URL. Update facts and screenshots that anchor the answer to the new query.

Content decay is a steady loss of clicks and impressions for a page while the rest of the site holds. It happens when the results page moved or your page went stale. Your job is a refresh, not a rewrite from scratch.

1. 1

   Map gaps to the live results page

   Search the head query. Note what wins now: structure, sections, updated facts, media, and any new questions in People also ask.

2. 2

   Update facts and dead bits

   Fix dates, prices, version numbers, step names, and any tool UI that changed. Retake screenshots. Replace dead links. Keep the URL.

3. 3

   Rewrite only the sections that miss intent

   Fold in the answers the results page now shows. Remove sections that no longer match the query. Do not add fluff to pad length.

4. 4

   Retitle if the results page moved

   If top results lead with “setup checklist” instead of “installation”, revise the title and h1 to match the dominant phrasing, within about 60 characters for the title.

5. 5

   Update the modified date

   Show a visible date on the page. Set datePublished and dateModified to match. Change the modified date only when you made a significant update.

Worked example: /pricing lost 90 clicks. The results page now has a comparison carousel and fresher dates. You add a clear “Plans compared” table, fix old screenshots, clarify billing terms, and set dateModified. The URL stays /pricing.

• Merge when two pages rank on the same queries and neither does well. Keep the URL with more links and clicks. Fold in the better bits from the other and 301 it.
• Delete when a page has no clicks, no impressions, no links and no purpose for a year. Return 410 Gone or 404. If a close equivalent exists, 301 to it instead.
• Avoid thin page families. Each page must hold data or an answer of its own that a reader would want. This protects your site’s overall assessment.

A content audit keeps this honest. Make a table of every page with 12 months of clicks and impressions, inbound links, date and purpose, and pick one decision: keep, refresh, merge, redirect or remove. Repeat each quarter and judge on the next quarter’s figures. Pruning is a data decision, not a hunch.

Google’s spam policies, updated March 2024, cover scaled content abuse, site reputation abuse and expired domain abuse. Google does not penalise AI-assisted writing as such. It acts on pages made at scale without value of their own. Keep pages that help, not pages that pad counts.

• Intent shift: the results page favours “how to” over “what is”. Fix your h1 and opening to meet the new intent, then tighten the matching sections.
• Freshness gap: rivals show visible recent updates and current UI. Update facts and media. Set a correct dateModified and show it on page.
• Feature steals the click: AI answer, PAA or a video row moved above you. Add a concise answer box and FAQ, consider a short video if that now dominates.
• Rival’s better page: a stronger guide landed. Improve structure, examples, internal links from relevant pages, and clarify your product’s angle.
• You cannibalised yourself: two close pages now split queries. Check Queries across both. Merge and 301 the weaker one if they answer one intent.

Worked example: /guides/export-csv and /blog/how-to-export-csv both rank for “yourproduct export csv”. Neither is above position 12. You keep /guides/export-csv, fold in the clearer steps from the blog post, 301 the blog URL, and retest in a month.

1. 1

   Set a calendar reminder

   On the first Monday, run the three months vs three before comparison. If seasonal, also keep a saved view for the same months year on year.

2. 2

   Tag pages

   For each faller, tag it Keep, Refresh, Merge, Redirect or Remove in your audit sheet. Add the main query and the suspected cause.

3. 3

   Fix two to four pages

   Small batches ship. Update titles, sections, screenshots and dates. Merge or redirect when you see overlap.

4. 4

   Request recrawl only if needed

   You can let Google recrawl. Use URL Inspection’s Request Indexing after significant changes on important pages, not for every typo.

5. 5

   Review after 28 days

   Judge on trends, not a day’s spike. Compare again next month. Keep what worked, adjust what did not.

Save your comparison in Search Console to skip setup next time. If you ship a lot in a quarter, add a column in your sheet for dateModified so you can see which updates moved the needle.

• Average position can drift when a page picks up many long-tail impressions. Read it with the Queries table for the head terms.
• CTR changes when the results page changes. If a new feature sits above you, aim for stronger placement or richer appearance, not just a new title.
• Query totals are lower than page totals because rare and anonymised queries are omitted. Do not expect perfect sums.
• Judge by clicks on the few queries that matter to the page. A rise from position 11 to 7 on “yourproduct pricing” is a win even if long-tail impressions fall.

A fixed page here looks like this: steadier clicks on its head query, position back into the top 10, a clear updated date, and fewer competing internal URLs for the same intent. You did not change the URL. You changed the parts that people and Google care about.