Content Refresh: How to Update Old Blog Posts and Recover Rankings

A content refresh is the process of updating an existing page to restore or improve its search rankings — without starting from scratch. The insight behind the practice: Google re-evaluates pages each time it crawls them, meaning an updated page can recover rankings that were lost to content decay, new competitors, or shifting search intent.

The economics of a content refresh are compelling. A post that once ranked in position 3 and is now at position 15 took months or years to earn those initial rankings — links, topical authority signals, historical click data. A well-executed refresh can recover that ranking in weeks, much faster than a new post starting from zero with no authority.

Identifying pages worth refreshing

Not every declining page deserves a refresh. The selection criteria:

Pages with historical ranking evidence — a page that never ranked isn't a content decay candidate, it may simply be targeting the wrong query or have insufficient authority. Look in Google Search Console's Performance report for pages that show significant impression volume with declining position or click trends. A page at position 12–25 with 500–2,000 monthly impressions is typically in the "just outside the good zone" range where a refresh can push it back to page 1.

Pages losing impressions year-over-year — in GSC, filter Performance by comparing the last 3 months to the same period in the prior year. Pages showing declining impressions (not just clicks) indicate Google is serving them less often, a strong signal of content decay. Declining clicks alone could be a CTR issue; declining impressions means the page is losing ranking ground.

Pages on time-sensitive topics — content that references years ("best practices in 2023"), specific tools, statistics, or technology versions decays faster than evergreen content. A guide that mentions "WordPress 6.3" or "iOS 16" signals to readers (and implicitly to Google, through engagement signals) that the page may be outdated.

Pages with qualified traffic but low conversions — if a page drives traffic but the conversion rate or next-page engagement is low, the content may not be matching current search intent. Intent shifts as a topic matures — what users expected to find for a query in 2022 may be different from what they expect in 2026.

Diagnosing why a page is declining

Before writing anything, understand why the page is losing ground:

New competitors in the SERP — search the target query and examine what now ranks in positions 1–5. If competitors have published comprehensive guides in the last 12–18 months that are significantly longer, better structured, or more up-to-date than your page, the refresh needs to match or exceed their depth. If the SERP is dominated by a new format (video results, featured snippets, People Also Ask boxes), the refresh may need to change the content format.

Changed search intent — compare the current top-ranking pages against what your page delivers. If your page was a listicle and the top results are now how-to guides, or your page is informational and the top results are commercial/transactional, there's an intent mismatch. Intent shifts require more than copy updates — they may require restructuring the page.

Missing subtopics — use the "People Also Ask" boxes for the target query and review the subheadings of the top-ranking pages. Identify which subtopics they cover that your page doesn't address. Missing coverage of a significant subtopic is often a straightforward fix that can materially improve ranking.

Outdated information — check whether statistics, tool recommendations, pricing, best practices, or examples are outdated. A single visibly outdated statistic ("according to a 2019 study...") signals to the reader that the page may not reflect current state, increasing bounce rate and reducing time-on-page — both indirect ranking signals.

Thin or unclear FAQ coverage — compare the FAQs on your page against the PAA boxes, related searches, and AlsoAsked data for the target query. If the page lacks FAQ coverage for common questions and a competitor's FAQPage Rich Result is occupying real estate in the SERP, adding a FAQ section with FAQPage schema can both address the content gap and improve search appearance.

What to update in a content refresh

A content refresh is not just changing the publication date. Superficial changes (updating the year in the title, adding a sentence or two) are detectable and don't produce meaningful ranking recovery. What moves rankings:

Structural improvements — if the top-ranking pages for the target query use a different structural approach (H2s that address specific questions rather than generic topics, numbered steps rather than prose, tables for comparisons), restructure the page to match the winning format. This often matters more than word count.

Filling content gaps — add dedicated sections for the subtopics that top-ranking pages cover and your page doesn't. Don't just mention a subtopic in passing — if competitors have a 300-word section on a subtopic, your coverage needs to be at least equivalent.

Updating time-sensitive content — replace outdated statistics with current data (with sources and dates), update tool recommendations to reflect the current market, and remove references to deprecated features or versions. Update the date frontmatter in MDX or the post publication date in your CMS to signal the update to search engines and users.

Adding FAQ schema — if the current page lacks a FAQ section with FAQPage JSON-LD, adding one addresses two issues: content gaps (FAQ sections address user questions the body content may not fully answer) and AI visibility (FAQPage schema is one of the five signals for AI Overview eligibility).

Improving internal links — add internal links from the refreshed page to newer cluster articles published since the original post, and add internal links from newer high-authority pages pointing back to the refreshed page. Both update the topical authority signal.

Improving CTR signals — if impressions are healthy but clicks are low, update the title tag and meta description to better match current search intent. Examine what the title tags of position 1–3 pages use and test a more competitive title that promises the same specificity or value.

After making changes, request reindexing via Google Search Console's URL Inspection tool (for pages that haven't been crawled recently) and monitor GSC for position changes over the following 4–6 weeks.

Measuring content refresh impact

GSC position tracking by page — set a date range comparison in GSC Performance (e.g., 28 days pre-refresh vs 28 days post-refresh, or same period year-over-year) for the specific page URL. An improvement of 3–5 positions often produces significant traffic recovery due to the logarithmic relationship between position and click-through rate.

Impression recovery — if impressions were declining and recover after the refresh, it indicates Google is re-evaluating the page positively. Impressions typically recover before click improvement, so impressions growth is an early positive signal.

Organic traffic trend — use Google Analytics or GSC's click data to measure actual organic traffic to the page. A successful refresh often shows a traffic recovery curve: flat or declining for the first 2–4 weeks post-refresh (while Google re-evaluates), then accelerating improvement over weeks 4–10.

Run the DeepSEOAnalysis free audit on refreshed pages to validate the technical foundation: canonical tags (ensuring the refreshed page has the correct canonical, not one pointing elsewhere from an old redirect chain), FAQPage schema correctness if you added FAQ content (property-level validation against Google's Rich Results specifications), Core Web Vitals (a refreshed page that added heavy images or embeds may have degraded LCP), and AI visibility signals (FAQPage schema, question-heading ratio, content chunkability).

---

Frequently asked questions

How often should you refresh content?

The refresh cadence depends on topic velocity — how quickly the subject area changes. For fast-moving topics (AI tools, platform pricing, Google algorithm updates), refreshing annually or more frequently may be necessary. For evergreen topics (canonical URL basics, robots.txt configuration), refreshing every 18–24 months is usually sufficient. The practical trigger for a refresh isn't a fixed calendar but observable ranking decline: if a page drops 5+ positions in GSC over a rolling 3-month period, that's the signal to audit it for decay and schedule a refresh. For a content inventory with hundreds of posts, prioritise by potential: pages with the most impressions and the biggest position decline offer the highest-leverage refresh opportunities.

Does updating the date alone improve rankings?

No. Updating the publication date or "last modified" date without substantive content changes does not reliably improve rankings, and Google's systems can typically detect whether a page's content has substantively changed versus just having its date metadata updated. Google has stated that freshness signals are evaluated on actual content changes, not date metadata alone. The date update does serve a legitimate purpose when paired with real content updates — it signals to users browsing the SERP that the content is current, which can improve CTR. But it is not a substitute for addressing the underlying reasons the page declined.

Should you 301-redirect an old post to a new one instead of refreshing it?

A 301 redirect makes sense when: the old URL is no longer the correct destination for the query (the content has fundamentally changed scope or topic), the URL slug is significantly suboptimal, or the page is being consolidated into a broader piece that better serves the intent. In these cases, the 301 passes the old page's link equity to the new URL. However, for most content refresh scenarios — updating a well-structured post that targeted the right query — refreshing in place is preferable. A 301 redirect resets some ranking signals (the new URL starts fresh for click data and some query-association signals), while an in-place refresh preserves all historical signals associated with the URL. Refresh in place unless there is a specific structural reason to change the URL.

What's the difference between a content refresh and a content audit?

A content audit is a site-wide inventory and assessment — reviewing every piece of content to categorise it as: keep (performing well, no action needed), refresh (declining, needs updating), consolidate (multiple thin posts on the same topic should be merged), or remove (no-index or delete low-quality pages with no traffic and no ranking potential). A content refresh is one of the actions that results from a content audit — the execution step for the "refresh" category. Audits happen at the portfolio level; refreshes happen at the individual page level. The content audit guide covers the full audit process; a content refresh is what you do with the pages the audit flags for updating.