Content Freshness: Why Updating Old Posts Beats Writing New Ones
The highest-return content work is usually not writing another post. It is fixing the ones already ranking on page two.
Content Freshness: Why Updating Old Posts Beats Writing New Ones
Most content strategies are built around a single verb: publish. More posts, more often, more topics covered.
That instinct is understandable and, for the first year, roughly correct — you need a body of work before anything can compound. But past a certain point it becomes the wrong priority, and teams keep following it because publishing feels like progress in a way that editing does not.
The higher-return work is usually sitting in your archive: posts that already rank somewhere on page two, already have some authority, and are one revision away from being genuinely competitive.
Why old posts have an advantage
A new post starts from zero. No history, no links, no accumulated signals. It has to earn everything.
A post published fourteen months ago has assets a new post cannot buy:
- Crawl history. Search engines know the URL and check it periodically.
- Whatever links it accumulated. Even a handful matters at small scale.
- Query data. Search Console can tell you exactly what it already ranks for, including terms you never targeted.
- Established position. Moving from position 12 to position 6 is a far smaller task than getting a brand-new page to position 12.
That last point carries most of the weight. Click-through rate falls off a cliff below the top few results. Moving a page from 12 to 6 can multiply its traffic several times over, and that is a smaller, better-defined job than producing a new post and hoping.
Why content decays
Content does not hold its position by default. It degrades, for reasons that have nothing to do with writing quality.
The facts change. Pricing moves, APIs deprecate, the tool you recommended got acquired and shut down. A post that was accurate at publication becomes wrong without anyone touching it.
Competitors publish something better. Someone covered your topic more thoroughly last month. You did not get worse; the bar moved.
Search intent shifts. What people mean by a query changes over time as a market matures. A post written for the old interpretation drifts out of alignment with what searchers now want.
Freshness signals fade. For queries where recency matters — anything involving tools, versions, or fast-moving practice — a 2023 date is itself a negative signal, regardless of whether the content is still correct.
Only the first of these is your fault, and all four are fixable.
How to find what is worth updating
Do not update at random. Search Console makes the targeting straightforward.
Step 1 — Find near-miss pages. In the Performance report, filter for queries where your average position is between 5 and 20. These pages are visible but not earning clicks. They have proven relevance and are close to a threshold where traffic changes materially.
Step 2 — Find declining pages. Compare the last three months to the previous three. Pages losing impressions are decaying. Catching this early is much cheaper than reviving a post that has already fallen out of the index.
Step 3 — Find accidental rankings. Look for queries a page ranks for that you never intended. This is the most valuable signal in the entire report — search engines are telling you what the market actually wants from that page. Frequently the right move is to lean into the accidental query rather than the one you originally targeted.
Step 4 — Check factual currency. Any post naming a specific version, price, or third-party tool has a shelf life. These need review on a schedule regardless of performance, because inaccuracy costs credibility even when traffic is fine.
What an update should change
Changing the date is not an update. Search engines evaluate the content, not the timestamp, and superficial edits to trigger a freshness signal are both detectable and pointless.
Substantive updates do one or more of the following:
Answer the question more directly. Often the answer is buried under three paragraphs of preamble. Move it up. Many page-two posts are page-one posts wrapped in a slow opening.
Cover the sub-questions you missed. Look at "People also ask" for your target query. If competitors address a related question and you do not, that gap is likely why you sit below them.
Correct what is now wrong. Update versions, prices, screenshots, deprecated recommendations. Say plainly what changed if the change matters to a reader who saw the old version.
Cut what is padding. Word count is not a ranking factor, and inflated posts perform worse because readers bounce. Removing 400 words of filler is a real improvement.
Realign to actual intent. If Search Console shows the page ranking for something adjacent to your target, consider whether that adjacent query is the better target. The market's opinion beats your original plan.
A maintenance rhythm that survives contact with reality
The reason freshness work does not happen is the same reason blogging stops: it is important, never urgent, and always loses to whatever is on fire.
The rhythms that survive have two properties — they are small enough to fit into a normal week, and they do not depend on someone remembering.
A workable cadence:
- Monthly: pull the near-miss list, update two posts. Not ten. Two is small enough to actually happen.
- Quarterly: audit posts naming versions, prices, or third-party tools for factual drift.
- Annually: decide what to retire. Posts that never gained traction and no longer reflect your positioning are better consolidated into a stronger page or removed than left to dilute the site.
That last one is uncomfortable and worth doing anyway. A site of 30 strong posts outperforms a site of 120 where 90 are dead weight.
Frequently asked questions
Does updating hurt existing rankings?
It can, temporarily, if you change the page substantially — the search engine has to re-evaluate. Improvements usually settle within a few weeks. The risk is real but small compared to the cost of letting a page decay, and it is lower when the update genuinely improves the page rather than shuffling it.
Should I change the URL when I update?
Almost never. The URL carries the history and links that make the page valuable. Change it only if the topic has genuinely shifted, and then redirect properly.
How much should change to count as an update?
There is no threshold that triggers a reward, because the reward comes from being a better answer, not from a change percentage. If a reader who saw the old version would find the new one meaningfully more useful, it counts. If not, you rearranged furniture.
Is it better to update or write a new post on the same topic?
Update, in almost all cases. Two pages on the same topic compete with each other and split whatever authority you have. Consolidating into one strong page beats maintaining two mediocre ones.
How do I know if a post is beyond saving?
If it targets a query with no search volume, or a topic outside what you now do, updating will not help. Retire or consolidate it. Effort spent reviving genuinely dead content is better spent on page-two pages that already have momentum.
The pattern underneath
Both halves of this — publishing consistently and maintaining what you published — fail for the same structural reason. They are recurring, never urgent, and depend on a person choosing to do them during a week when more pressing things exist.
The teams that compound over years are not the ones with more discipline. They are the ones who removed the decision from the loop.
The Bason treats freshness as a first-class part of publishing rather than an afterthought: published posts can be revisited on a schedule and either partially revised or fully rewritten, with the updates flowing back into your sitemap and out through IndexNow automatically.