Half of every content site’s traffic comes from posts published more than a year ago — and most of those are quietly decaying. This tutorial uses AI to spot the highest-leverage refresh candidates (posts that lost rankings but are one solid update away from reclaiming top-3), draft the changes, and ship in a single PR. Expect 20-40% traffic recovery on refreshed pages within 6-8 weeks. The workflow takes about 30 minutes per article, and you can batch 5-10 in an afternoon.
What this covers
A two-stage workflow: detection (Search Console position decay over 90 days) plus refresh drafting (AI rewrites the weak sections, keeps the strong ones, updates the dates). Refresh is not the same as rewrite. A refresh changes 20-40% of the article; a rewrite is a new article on the same URL. We focus on refresh because it preserves accrued authority.
Who this is for
Content sites with 100+ articles and a tail of older posts. SEO managers running a monthly “decay sweep”. Solo bloggers staring at a 2023 post that used to bring traffic and no longer does. Skip if your articles are evergreen by design (philosophy, fiction) — refresh logic does not apply.
When to reach for it
Monthly maintenance, after a Google update that downranked older posts, when a competitor publishes a stronger version of your top post, or before any seasonal traffic spike when your top posts should be in their best shape. Pair with a cannibalization audit so you do not refresh a post that should be merged.
Before you start
- Pull 12 months of Search Console data for impressions and average position per URL. The decay pattern is invisible without time-series data.
- Decide your refresh threshold: typical rule is “position dropped 3+ spots over 90 days while impressions are still meaningful”. Articles that never ranked do not qualify for refresh — they need a rewrite.
- Have the article’s primary keyword on hand. Refresh without a target keyword is renovation without a blueprint.
- Snapshot the current ranking and top SERP competitors. The refresh has to clear the bar set by what is ranking today, not what ranked when you wrote it.
Step by step
- Export Search Console: URL, primary query, position 90 days ago, position now, current impressions. Filter to URLs where position dropped 3+ spots and impressions remain meaningful.
- Sort by impression volume. The top 20 articles in this filter carry most of the recovery upside.
- For each candidate, ask AI: “Read this article and the top 3 currently-ranking SERP results. What is the article missing? What is outdated? What is fine and should stay?” Provide the article body and competitor article URLs or excerpts.
- AI produces a section-by-section diff plan: keep / refresh / replace / add. Reject any plan that wants to touch more than 50% of the article — that is a rewrite, not a refresh.
- Draft the refreshed sections with AI, then human-edit. Update statistics, examples, screenshots, and any product names that have changed. Push the publish date forward.
- Ship in one PR per article. Bulk PRs lose review quality; one PR per article keeps the diff focused.
- Resubmit the URL in Search Console (URL Inspection -> Request Indexing) so the refresh gets crawled within 24-48 hours instead of waiting for the next cycle.
First-run exercise
- Pick the single highest-impression decayed article (one URL, not ten). The narrow scope teaches the workflow before you scale.
- Run the diff-plan step and review AI’s keep / refresh / replace assignments against your own read. Disagreement rate of 20-30% is normal; over 50% means the prompt is too vague.
- Time the full refresh end to end. Most articles take 30-45 minutes once you have the diff plan. If you are spending 90+ minutes, the article needs a rewrite, not a refresh.
- Measure the position 14 and 28 days after refresh. Most refreshes show a 2-4 position lift within 4 weeks.
Quality check
- Refresh preserves the URL, the H1, and the article’s spine. If those change, it is a rewrite — and rewrites lose authority during the transition.
- Updated publish date appears in the visible metadata and the schema. Search engines weight freshness from schema, users weight it from visible byline.
- Every dated claim is verified. “As of 2023” sentences are landmines; either remove them or update them.
- The intro paragraph reflects the refreshed scope. Stale intros undermine fresh bodies.
- Internal links still resolve. Refresh often touches link targets without updating the source — re-run a link check.
How to reuse this workflow
- Keep a “refresh ledger” with URL, refresh date, position-before, position-after. After three months, you can prove which refreshes worked.
- Re-refresh frequency depends on the topic: evergreen tutorials need a touch yearly, tool comparisons need quarterly attention, year-keyword articles need annual.
- After every Google update, scan the ledger. Articles you refreshed within the last 90 days are usually safest; older refreshes may need another pass.
Recommended workflow
12-month Search Console export -> filter to position-decay candidates -> sort by impressions -> AI produces section-by-section diff plan -> human-edit and update dates / stats / examples -> single PR per article -> request indexing in Search Console -> measure position at 14 and 28 days.
Common mistakes
- Refreshing articles that never ranked. Those need a rewrite or a deletion, not a refresh.
- Updating only the publish date with no content change. Search engines see the lack of substantive change and weight the date less.
- Adding 1000 words of fluff to “make it longer”. Length without value triggers algorithmic suspicion.
- Removing the article spine. The refresh should feel like a polished version of the same article, not a different article.
- Refreshing 20 articles at once with no measurement plan. Without per-article tracking you cannot tell which refreshes worked.
- Ignoring SERP shifts. If the top 3 today is comparison-focused and your article is tutorial-focused, refresh cannot close that gap — that is a new article.
FAQ
- How big should a refresh be?: 20-40% of the content changes. Below 20% is cosmetic and ignored; above 50% is a rewrite.
- Should I change the URL?: No. The URL carries the authority. Change the title and H1 if needed, never the slug.
- What about the publish date?: Update it to the refresh date. Use schema datePublished for the original date and dateModified for the refresh.
- How often can I refresh the same article?: Twice a year at most. More frequently signals churn rather than improvement.
- Does adding an FAQ section help?: Yes, when there are real FAQs. An FAQ section pasted in to chase rich snippets without answering real questions fails fast.
- Should I refresh articles ranking on page 2?: Page 2 with rising impressions is a strong refresh candidate. Page 2 with flat impressions is a topic problem, not a content problem.
Related
Tags: #SEO #content-refresh #Tutorial