How Often Should You Update Old Blog Posts? Follow the Evidence

By Katleen, Founder of PARCHMNT · Updated October 29, 2026

Update old blog posts when the evidence says so, not on a schedule. The honest answer to how often you should update old blog posts is: as often as one of four things happens. The post loses positions, its clicks fall, Google shows it for searches it does not answer, or its facts are two or more years old.

This post is built on Google's helpful content guidance, its documentation on byline dates and recrawling, and the Search Console Performance report, plus the refresh rules we built into PARCHMNT.

Why doesn't a calendar tell you how often to update old blog posts?

A calendar tells you that time has passed, not that anything has changed. Most pages ranking for this search recommend a fixed rhythm. Semrush, for example, says "You should update much of your blog content once every three to six months". That rhythm is easy to follow and often wasted.

A schedule fails in two directions. A post whose facts are still right and whose position is steady gains nothing from an edit, and Google says so. Its helpful content guidance asks whether you change content because you believe "it will help your search rankings overall by somehow making your site seem "fresh?" (No, it won't)".

In the other direction, a quarterly review misses the post that broke three weeks after you last looked. The right time to refresh old content is when something changed, and evidence catches both cases: you look at the data monthly and edit only what it flags. The cost is that you need Search Console connected and read.

Which signals say a blog post needs an update?

Four signals say a post needs an update. It lost three or more places in four weeks. Its clicks fell by a third or more. Google shows it for searches it does not answer. Or it cites facts from two or more years ago. Any one is reason enough; none of them is a date.

Signal	Where you see it	What it usually means	What to change
Lost three or more places in four weeks	Performance, Pages, compare periods	A page above you now covers more	Add what the pages that passed you answer
Clicks down a third, position steady	Same place, compare clicks	Often an AI answer above the results, not your text	Make the title and opening worth citing
Shown for searches it does not answer	Filter by page, read Queries	The question under the page moved	Add a section that answers it
Facts two or more years old	Your own text and links	Numbers and rules changed	Re-source each figure

The second row deserves care, because falling clicks with a steady position are often not the post's fault. Ryan Law of Ahrefs wrote in February 2026 that "the presence of an AI Overview now correlates with a 58% lower average clickthrough rate for the top-ranking page". Before you rewrite anything, look at what now sits above the results.

PARCHMNT is a writing tool that researches what ranks for a search, writes the page, checks every claim and tracks where it lands in Google and AI answers. Its refresh reasons are these four signals plus one more: research older than a year. Each article shows the reason it was flagged, not a generic nudge.

How do you find those signals in Search Console?

Open Performance in Google Search Console and compare the last 28 days with the 28 before. Sort the Pages tab by the change in clicks and in position. Search Console keeps "data for the last 16 months", so you can also compare this month with the same month last year.

Open Performance, then Search results. Google defines position there as "the average position of the topmost result from your site". A post shown at 2 and 9 for two searches reads as about 5.5.
Turn on Compare in the date filter: last 28 days against the previous period. The tables gain a difference column.
Sort Pages by click difference. The posts that lost most sit at the bottom. If position did not move, you have the AI answer case above.
Click a losing post, then Queries. Searches with real impressions that use words your post lacks are the shifted question.
Check the year on each fact. Anything from two or more years ago goes on the list.

Our line of three places in four weeks is one we chose, not a Google figure. In our experience a post's average position wanders by a place or two week to week, so a smaller change is noise. Our guide to tracking where your pages rank for free walks through the report screen by screen.

What should an update actually change?

An update changes what the evidence flagged and leaves the rest alone. Re-source every figure older than two years, add a section for the search Google now shows the page for, and cover what the pages that passed you answer. Keep the address, the headings that still hold a position, and the voice.

Rewriting the whole post throws away the evidence of what worked; the sections that hold their positions are the parts Google already agrees with. Google's quality questions include "Does the content have any easily-verified factual errors?" That is the plainest reason to fix facts and the weakest reason to touch anything else.

Take Clockbird, a fictional time-tracking app we use as an example. Its 2024 post on rounding billable hours cited a 2023 survey, and Search Console now shows impressions for "rounding billable hours to six minutes". The content refresh is one new section on six-minute increments, a current source for the survey figure, and an opening that mentions increments. Nothing else moves.

When the change would touch more than half the page, you have a new page, not an update. Write it, link the old post to it, and redirect only if the old post has no reason left to exist. If a post stopped ranking entirely, the cause is often outside the text; our post on why a blog post is not ranking covers those causes.

How do you change the date on an updated post honestly?

Change the visible date only when the text substantially changed, show it as an updated date rather than a new publication date, and make the structured data match. Google's helpful content guidance asks, word for word, "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?"

Google's documentation on byline dates covers the mechanics. Dates "must describe the publication or update date of the page, not the stories or events described therein". Visible dates and structured data should match, with datePublished and dateModified as separate fields. The same page says to "Minimize the presence of other dates on the page" so Google picks the right one.

In practice, keep Published with the original date, add Updated with the new one, and set dateModified to match. A fixed typo is not an update, and moving the date for it is the behavior Google's question describes. As of October 2026 that question is still on Google's guidance page, last revised on October 5, 2026.

How long does it take Google to notice an update?

Google notices an update when it next crawls the page. Its documentation says that "can take anywhere from a few days to a few weeks". You can ask for a recrawl with the URL Inspection tool, but Google adds that "requesting a recrawl multiple times for the same URL won't get it crawled any faster".

To ask once, paste the address into the inspection bar at the top of Search Console and choose Request indexing. The tool's documentation notes "There is a daily limit to how many index requests you can submit". It adds that a request "does not guarantee that the page will appear in the Google Index". Then leave it alone.

Judge the update after four weeks in the Performance report, not after four days. In our experience, posts linked from the home page or from newer posts get recrawled sooner than posts nothing points to; that is an observation, not a statistic. For a brand-new page, our post on how long Google takes to index a new page covers the wait from scratch.

Key takeaways

Update a post when the evidence says so: lost places, falling clicks, searches it is shown for but does not answer, or facts two or more years old.
Google's own guidance says making content seem fresh does not help rankings, in so many words.
Compare two 28-day periods in Search Console to find all four signals in a few minutes.
Change the visible date and dateModified only when the text substantially changed, and show it as an update.
Request a recrawl once, expect days to weeks, and judge the result after four weeks.

Frequently asked questions

Does updating a post reset its rankings?

No. An update to the same address keeps the page's history: its links, its indexed status and its record in Search Console. Positions can move after a substantial change, up or down, because Google re-evaluates the new text, and that is the point. Keep the address and the sections that hold positions, and the risk stays small.

Should you delete old posts that get no traffic?

Not by default. Check 16 months of impressions in Search Console first, because impressions, not clicks, show whether Google still considers the page for anything. A post with no impressions, no links and no facts anyone needs can be removed or merged into a stronger post with a redirect. A post with impressions but few clicks needs a better title, not deletion.

Do AI assistants care about the updated date?

They read the dates you show and tend to favor current, accurate pages, so an honest updated date with matching structured data helps. A changed date over unchanged text does not, because the facts underneath are what the assistant quotes. Our post on getting cited by Perplexity covers how dates show up there.

How often should you update old blog posts, in one rule

Update when the data says so: lost places, lost clicks, a shifted question or aged facts. Then date it honestly and give Google a few weeks to notice. If you would rather have the signals watched and the reason shown for every refresh, try one article free.

Sources

This post was written and checked with the same rules PARCHMNT applies to every page it writes for a customer: researched against what ranks today, answer first, every figure with a source.

Try 1 article free