The Real Refresh: Rewriting a Decayed Page's Intro and Closing Its Gaps
Objective: Given a decayed page's old intro, its stale stats, and a list of subtopics competitors now cover that it doesn't, produce a refresh brief and rewritten intro that would actually recover rankings, not just change the publish date.
You're a content strategist at Zendesk. 'customer-support-ticketing-best-practices' ranked #4 for two years, has slid to position 11, and the fastest fix on your desk was a marketer suggesting you 'just bump the date.' You have the old page and a competitor gap analysis.
Diagnose the decay pattern, then rewrite the intro and outline the fix for every stale stat and content gap, not just the timestamp.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, first-party performance data for the exact URL
Free, easy to share with an editor or developer for review
Paid upgrades (optional, faster/deeper)
The free path (manual competitor read-through) takes longer but produces the same gap list; Ahrefs just speeds up finding it.
Content Gap tool surfaces ranking subtopics across competitor URLs faster than manual review
No access? Manually read the top 3 ranking competitor pages and list subtopics they cover that this page doesn't
The process
3 steps
Step 01 of 03
Cliff decay, slow bleed, and position drift each point to a different root cause, and treating all three the same way wastes the fix.
The page held position 4 for two years, dropped steadily to position 11 over 5 months, and impressions barely moved. Which decay pattern is this, and does that change whether a full rewrite is even the right first move?
Procedure
- Pull the URL's six-month clicks, impressions, and average position trend from Search Console
- Confirm impressions stayed flat while position and clicks fell, matching position drift, not cliff decay
- Note that position drift usually means the page is still relevant to Google but reads as thinner or staler than competitors now, which justifies content rewrite over a technical fix
customer-support-ticketing-best-practices Impressions: 22,400 -> 21,900 (flat) Position: 4.1 -> 11.3 Clicks: 3,100 -> 890 Pattern: position drift -> content freshness/depth problem, not a technical or SERP-feature problem
Healthy
Confirming position drift before rewriting means the fix targets content depth and freshness, the actual cause, instead of chasing a technical issue that isn't there.
Unhealthy
Assuming this is cliff decay and spending the sprint auditing for a manual penalty or crawl error when impressions never dropped.
What this means
Flat impressions with falling position and clicks is Google's way of saying 'I still think this page is relevant, but I'm not confident it's the best answer anymore.' That is a content problem, not a technical one.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Position falls steadily while impressions hold | Skip the technical audit and go straight to a content depth and freshness review | 30 min |
Step 02 of 03
A real refresh starts with the first 100-150 words, rewritten to answer the query directly and in plain language, because that section is what AI Overviews and answer engines lift first.
The old intro opens with 'In today's fast-paced customer service landscape, ticketing systems have become an essential tool for businesses of all sizes.' It doesn't answer the query for 3 more sentences. Rewrite it to answer 'what are customer support ticketing best practices' in the first sentence.
Procedure
- Delete the throat-clearing opening sentence entirely
- Write a first sentence that states the direct answer: the core best practices, named
- Keep the full rewritten intro under 150 words and in plain, direct language
OLD (deleted): 'In today's fast-paced customer service landscape, ticketing systems have become an essential tool...' NEW: 'The best customer support ticketing practices in 2026 are: route by urgency and skill match, not first-in-first-out; set a first-response SLA under 1 hour; and close the loop with a resolution summary the customer can search later. Here's how each one works and why it moves your CSAT score.'
Healthy
A reader or an AI Overview can lift the answer from the first sentence alone, without reading the rest of the page.
Unhealthy
Keeping the throat-clearing opening and only swapping the 'last updated' date, which is the fake refresh the lesson calls out directly.
What this means
The first 100-150 words carry the most weight for both human skimmers and AI answer extraction, so that's where refresh effort pays off fastest per minute spent.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| The intro takes 2+ sentences to state the actual answer | Rewrite the first sentence to state the direct answer before anything else | 30 min |
Step 03 of 03
A real refresh replaces every dated statistic with a current one and fills the thin sections where competitors now cover a subtopic the page skipped, fixing what's wrong in place rather than padding the bottom with new words.
The page cites a 2022 stat ('62% of customers expect a reply within 10 minutes') and is missing a section on AI-assisted ticket routing that all 3 top competitors now include. What two fixes go in the brief, and where do they go, not at the bottom?
Procedure
- Find a current, sourced replacement stat for the 2022 figure and note the exact paragraph it replaces
- Write a one-paragraph outline for the missing AI-assisted ticket routing section, placed after the section it logically follows, not appended at the end
- List every other dated claim in the old page (a discontinued tool mention, a deprecated best practice) as a third fix category
STAT REPLACEMENTS - Para 2: swap 2022 stat for 2026 figure, cite source, same location in the page GAP FILLS (mid-page, not appended) - New section after 'Routing Rules': 'AI-Assisted Ticket Routing' (competitors: Zendesk's own guide competitors cover this, we don't) OUTDATED CLAIMS TO FIX - Para 6 recommends a tool that was discontinued in 2025, replace with current alternative
Healthy
Every fix is placed exactly where the outdated or missing content lives in the page structure, so the page reads as coherently updated, not patched at the end.
Unhealthy
Adding a new 'AI-Assisted Ticket Routing' section at the very bottom of the page after the conclusion, which the lesson explicitly calls out as not counting as a real refresh.
What this means
Placement matters as much as content: a gap-fill section appended at the end reads to both readers and Google as padding, while the same content placed where it logically belongs reads as genuine depth.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| A competitor gap analysis lists a missing subtopic | Write the new section and insert it at its logical place in the existing structure, never appended at the end | half day |
Final deliverable
A refresh brief with the confirmed decay pattern, a rewritten 150-word intro, a stat-replacement list with exact paragraph locations, and a gap-fill outline placed within the existing page structure.
See a reference example
Wise, 'international-wire-transfer-fees-guide' refresh brief (excerpt) DECAY PATTERN: position drift (4.5 -> 9.2, impressions flat) NEW INTRO: 'International wire transfer fees in 2026 range from $0-$50 depending on your bank and destination currency. Here's the current fee breakdown for the 8 most-used providers, and how to avoid the hidden markup most guides don't mention.' STAT REPLACEMENTS: Para 3, swap 2023 average-fee figure for current 2026 figure GAP FILL: New section after 'Bank Wire Fees' on 'Hidden FX Markup', competitors cover this, we don't
Success criteria
You're done when you can:
- Decay pattern is confirmed from Search Console data before any content decision is made
- The rewritten intro states the direct answer in the first sentence and stays under 150 words
- Every stat replacement and gap fill is placed at its logical location in the page, none appended at the bottom