When a refresh beats a new URL
Refresh when the URL has history, backlinks, or brand recognition, and the query still maps to that page. Write new when intent has shifted so hard that the old URL confuses users, or when you are merging thin pages into a stronger home. Content pruning is part of the job: some pages should redirect or be removed.
Who this is for
- Sites with older posts that slipped from page one
- Teams sitting on outdated stats, screenshots, or product names
- Publishers with thin overlap across many similar URLs
Who it is not for
- Pages with no traffic, no links, and no strategic role (prune instead)
- Clients who only want a fresh date in the CMS
- Full site rewrites better scoped as website copywriting
How a content refresh works
- Pull performance, indexing, and backlink context for the URL.
- Re-read the SERP and compare coverage gaps.
- Decide: update, expand, merge, prune, or rewrite on the same URL.
- Brief the changes section by section.
- Rewrite and edit; update meta, headers, and internal links.
- Deliver a change log so your team knows what moved.
Intent reading comes first. Use search intent and SERP reading before touching prose. Brief quality still matters; see what goes into a good content brief.
What you get
- Recommended action per URL (refresh, merge, prune, leave)
- Updated draft with tracked changes or a clear change log
- Revised meta title and meta description
- Internal link updates and anchor guidance
- Notes on outdated claims removed or replaced
- CMS upload when scoped
| Symptom | Likely tactic | Notes |
|---|---|---|
| Rank slip, thin coverage | Expand with gap sections | Keep URL if intent holds |
| Outdated facts | Accuracy pass + sources | Fast win when structure is fine |
| Many near-duplicate posts | Merge + redirect | Prune carefully |
| Intent changed | Retarget or new URL | Do not frankenstein forever |
Turnaround
A focused refresh often takes four to eight business days from brief to draft, faster for accuracy-only passes and longer for heavy rewrites. Batches of URLs are scheduled like a mini programme.
Pruning, merges, and internal linking
Content pruning removes or narrows pages that add noise. Keeping weak URLs often hurts the whole cluster by splitting relevance. We recommend redirects and hub updates when you remove posts so equity flows somewhere useful. Merge decisions get documented so your team knows which slug survives and why.
Refreshed hubs strengthen topic clusters: pillar pages get updated links from supporting posts, and supporting posts get revised intros that point to current product language. Net-new volume should wait until high-equity URLs are honest again. Pair refresh work with blog writing services when the calendar needs ongoing production after the library is stable. For AI summary visibility, see writing for AI Overviews when extractability matters on updated pages.
Batch refresh programmes
Large libraries refresh in phases ranked by traffic, revenue proximity, and factual risk. A fifty-URL batch without promotion or link updates wastes effort. We propose phases your SEO, legal, and engineering teams can actually ship. Each phase ends with a change log for compliance and client reporting when agencies resell the work.
Accuracy, compliance, and dated claims
Refresh work often surfaces claims that were true three years ago and are not true now: pricing language, regulatory references, product names, integration lists. We flag removed claims in the change log so legal can sign off. Screenshots and example workflows get updated descriptions even when design assets stay the same.
Measuring refresh outcomes
We define success in the brief before rewriting: recover rankings on a target query, improve click-through from search, update compliance language, or consolidate cannibalizing URLs. Rankings move on their own schedule; accuracy and coverage improvements are visible immediately to sales and support teams who stopped linking to embarrassing pages.
After publish, track the URL for eight to twelve weeks before declaring failure. Minor heading changes sometimes need a full crawl cycle to reflect. If performance stays flat with a materially better page, the blocker may be technical, internal links, or competition rather than copy alone.
Working with your SEO and dev teams
Refresh deliverables include redirect recommendations, but implementation stays with your team unless scoped otherwise. We coordinate timing so copy goes live when redirects and internal link updates ship together. Half-updated clusters confuse crawlers as much as stale paragraphs confuse readers.
What we change on the page besides the body copy
Refreshes often include title tags, meta descriptions, header hierarchy, internal links, and outdated screenshots called out for replacement. Body prose is only one layer. A beautiful rewrite that keeps a misleading H1 still fails the SERP.
We document what changed so your team can QA quickly. Editors and SEOs should not have to diff blindly. When pruning is the recommendation, we explain why a redirect target is safer than another rewrite pass on a thin URL.
Batch refreshes work well beside an active blog programme. New URLs and recovered URLs should share one cluster map so you do not publish into your own overlap.