Skip to content
Academy
Marketing Academy · Field Work●SEO
All projects·From: Content Decay: Refreshing and Reclaiming Lost Rankings
MiniAudit· 30 minutes

The Triage Call: Auditing a Search Console Decay Report

PolicyBazaar (PB Fintech)

Objective: Given a real 20-page Search Console export comparing the last six months to the prior six, classify each page's decay pattern and decide which pages get a quick refresh, a full rewrite, or a lower-priority hold.

You're the SEO analyst on PolicyBazaar's content team. Organic clicks to the insurance-guides section are down 18% year over year, and leadership wants a prioritized fix list before the next content sprint, not a vague 'traffic is down' summary.

Sort the export by clicks lost, classify each page's decay pattern, then flag which pages are quick wins versus pages that need a full rewrite.

Before you start

What you'll need

Free path (everything below is enough to finish)

Google Search Console
FreeSource of the six-month-vs-prior-six-month clicks, impressions, and position data

Free, first-party, and the only tool that shows Google's actual view of each page's performance trend

Google Sheets
FreeClassify decay patterns and sort the prioritization list

Free, no account friction, sorts and filters the export in minutes

The process

2 steps

Step 01 of 02

Classifying decay patterns from Search Console deltas

The lesson splits decay into three patterns from a six-month-vs-prior-six-month Search Console comparison: cliff decay (a sudden 40-60% drop after 18+ stable months), slow bleed (5-10% fewer clicks every month for six months), and position drift (rank falls while impressions hold, so users stop clicking).

Row 3, 'car-insurance-renewal-guide', held steady at ~9,200 clicks/month for 14 months, then dropped to 3,600 clicks in the most recent quarter with impressions falling the same amount. Row 11, 'two-wheeler-claim-process', still gets the same impressions but clicks fell from 4,100 to 2,050 as average position slid from 3.8 to 7.9. Which pattern is each row?

Google Sheets— Import search-console-decay-export.csv, freeze the header row, add a 'pattern' column.

Procedure

  1. Import search-console-decay-export.csv and freeze row 1
  2. For each row, compare the impressions trend against the clicks trend across the two six-month windows
  3. Tag rows where both impressions and clicks fell together after a long stable run as 'cliff decay'
  4. Tag rows where impressions held but average position and clicks both fell as 'position drift'
  5. Tag the remaining steady, small monthly declines as 'slow bleed'
Sample output
PATTERN CLASSIFICATION (excerpt)
car-insurance-renewal-guide      clicks 9,200->3,600   impr 41,000->16,200   pattern: cliff decay
two-wheeler-claim-process        clicks 4,100->2,050   impr 38,500->38,100   pos 3.8->7.9   pattern: position drift
health-insurance-tax-benefits    clicks 6,800->6,100->5,500 (monthly)      pattern: slow bleed

Healthy

Every row in the export gets one of the three pattern tags before any prioritization happens, so the fix matches the actual cause instead of a generic 'refresh everything' response.

Unhealthy

Sorting only by percentage lost and missing that 'car-insurance-renewal-guide' lost more raw clicks (5,600) than three slow-bleed rows combined, because percentage loss hides the highest-value page in the list.

What this means

Cliff decay usually points to a SERP feature change or algorithm update and needs investigation before rewriting; position drift with flat impressions means Google still shows the page but users don't click it, which is a freshness or snippet problem, not a ranking problem.

So what do I do about it?

SymptomActionEffort
A page shows cliff decay after 18+ stable monthsCheck for a named algorithm update or new SERP feature on that query before rewriting a single word30 min
A page shows position drift with flat impressionsRewrite the title tag and meta description first, since Google is still showing the page but nobody clicks it30 min
YouYou can do this yourself, no engineering access required.

Step 02 of 02

Prioritizing by traffic value, decay severity, and competitive gap size

The lesson prioritizes by three factors together, current traffic value, decay severity, and the size of the competitive content gap: a page bleeding 20% with a small gap is a quick win, while a page down 60% against a much deeper competitor article needs a full rewrite, not a patch.

You have 6 sprint slots. 'car-insurance-renewal-guide' lost 5,600 clicks/month (cliff decay, competitor gap: 3 missing subsections) and 'bike-insurance-online-guide' lost 900 clicks/month (slow bleed, competitor gap: outdated pricing table only). Which gets a slot first, and what kind of fix does each get?

Google Sheets— Add 'clicks lost' and 'gap size' columns, then sort by clicks lost descending.

Procedure

  1. Add a 'clicks lost (raw)' column, not percentage, and sort the sheet by it descending
  2. Add a 'competitor gap size' column, tagging each row 'small' or 'large' based on missing subtopics
  3. Cross the two: high clicks lost + large gap = full rewrite this sprint; high clicks lost + small gap = quick win this sprint
  4. Push low clicks-lost + small-gap rows to next quarter's backlog
Sample output
SPRINT PRIORITY (6 slots)
1. car-insurance-renewal-guide     -5,600 clicks   large gap    FULL REWRITE
2. two-wheeler-claim-process       -2,050 clicks   small gap    QUICK WIN (title/meta + intro)
3. bike-insurance-online-guide       -900 clicks   small gap    QUICK WIN (pricing table update)
...
BACKLOG (next quarter): 14 rows under 500 clicks lost

Healthy

The 6 sprint slots go to the highest raw-clicks-lost rows first, with rewrite-vs-quick-win split by gap size, so the sprint recovers the most traffic possible with the time available.

Unhealthy

Spending a full sprint slot rewriting 'bike-insurance-online-guide' (900 clicks lost, small gap) while 'car-insurance-renewal-guide' (5,600 clicks lost) sits in the backlog because its percentage loss looked smaller.

What this means

Raw clicks lost, not percentage, determines business impact; gap size determines whether the fix is a quick win or a full rewrite. Confusing the two produces a sprint plan that feels busy but recovers little traffic.

So what do I do about it?

SymptomActionEffort
The backlog has more pages than sprint slotsSort by raw clicks lost first, then split each row into quick win or full rewrite by gap size30 min
YouYou can do this yourself, no engineering access required.

Final deliverable

A 20-row prioritized sprint list with each page tagged by decay pattern (cliff decay, slow bleed, position drift) and fix type (full rewrite, quick win, backlog), sorted by raw clicks lost.

See a reference example
Sample output
Chewy, pet-care content decay triage (excerpt)

SPRINT PRIORITY
1. dog-food-allergy-guide         -4,900 clicks   large gap    FULL REWRITE
2. cat-litter-comparison-2024     -1,800 clicks   small gap    QUICK WIN (title/meta + stats)
3. puppy-vaccination-schedule       -700 clicks   small gap    QUICK WIN (pricing update)

BACKLOG (next quarter): 12 rows under 400 clicks lost

Success criteria

You're done when you can:

  • Every row in the export is tagged with one of the three decay patterns
  • Sprint slots go to the highest raw-clicks-lost pages first, not the highest percentage
  • Each prioritized page is tagged full rewrite or quick win based on competitive gap size, not guessed