A post that is out of date but still brings in search traffic is worth more than a new one that brings in none, which is why touching it feels risky. The safe way to update it is to keep the URL, keep whatever already answers the searches it is shown for, change the substance rather than the date, and then give Google a few weeks before reading anything into the numbers.
- Look first — Search Console shows the queries the page already ranks for. Whatever answers them stays
- Same URL — or a permanent server-side redirect if it truly has to change
- Substance, not the date — Google asks whether you are “changing the date of pages to make them seem fresh”
- One date, three places — the visible “Last updated” line,
dateModifiedand the sitemap’slastmodshould move together - Wait before judging — recrawling “can take anywhere from a few days to a few weeks”
Check what the page already ranks for
Before changing a word, open Search Console’s Performance report, filter to the page and read the Queries tab. Those are the searches it is shown for today. Whatever answers them, whether a heading, a table or a two-line definition, should survive the rewrite in some form, even if every sentence around it changes. Retitling a post away from its main query is the quickest way to lose it.
Write down the page’s weekly impressions and average position as well. You will need a before figure, because Google’s guide to traffic drops tells you to “Compare the drop period to a similar period”.
Keep the URL, or redirect it permanently
The URL carries the page’s links and its place in the index, so change it only when the old one is actively wrong. If you must, Google is direct about how:
If you need to change the URL of a page as it is shown in search engine results, we recommend that you use a permanent server-side redirect whenever possible.
Even a correct redirect costs something for a while. Google’s traffic-drop guide warns that if you change the URLs of existing pages, “you may experience ranking fluctuations while Google recrawls and reindexes your site”. When this site moved off WordPress in August 2026, every blog post kept its slug, and our build now fails if a redirect would shadow a live page.
Change the substance, not the date
A new date on old text is the update Google is most explicit about. Its list of questions for spotting search-engine-first content includes this one:
Are you changing the date of pages to make them seem fresh when the content has not substantially changed?
— Google Search Central, Creating helpful, reliable, people-first content
Sitemaps work the same way. Google’s sitemap documentation says lastmod “should reflect the date and time of the last significant update to the page”, and that Google only uses it when it is consistently and verifiably accurate.
A real update replaces dead or wrong sources, re-checks every number, answers the questions the page’s queries now ask and cuts what is no longer true. When we refreshed our AI marketing automation tools roundup on 15 October, HubSpot had moved to per-seat pricing since our last check, which made every HubSpot figure in the post wrong. That is a reason to change the date. Re-saving the file is not.
Keep the dates in step
When the update is real, show it. Google’s byline guidance asks for a visible date labelled “with text like "Publish" or "Last updated"”, and for the datePublished and dateModified fields in the page’s structured data. Keep the original published date and move only the updated one. On this site the visible line, dateModified and the sitemap’s lastmod all come from one updatedDate field. Before we audited it, five posts had drifted by up to four weeks, because nothing else catches a missed bump.
Tell Google, then wait before you judge
Once the update is live, request indexing for the URL in Search Console’s URL Inspection tool, once. Google is candid about what that buys. Its recrawl documentation says “Crawling can take anywhere from a few days to a few weeks”, that “Requesting a crawl does not guarantee that inclusion in search results will happen instantly or even at all”, and that asking again for the same URL “won’t get it crawled any faster”.
What happened when we rewrote our own post
On 1 September we rewrote the same roundup end to end, from about 3,050 words to 4,650 with a changed roster, and replaced most of its images on 24 September. For ten days it held at around 29 impressions a day. Then it all but disappeared, averaging 4.5 a day from 11 to 28 September. URL Inspection shows the page’s latest crawl on 28 September, and by the next day it was back above its pre-rewrite level. From 1 to 13 October it averaged 104 impressions a day at an average position of 17.8, against 32.5 a day at 19.5 in the eleven days before the rewrite.
That is not a clean experiment. The whole site lost about half its impressions over the same weeks and roughly doubled them in October, and Google’s September 2026 spam update began rolling out on 24 September. What the numbers do show is the cost of judging early. In mid-September they looked like a verdict, and rolling back would have discarded the version that now earns three times the daily impressions. Google’s traffic-drop guide warns that “positions aren’t static or fixed in place”.
Also Read: Why Isn’t My Page Indexed? A Search Console Diagnostic
Key Takeaways
- Read the page’s queries in Search Console before editing, and keep whatever answers them
- Keep the URL. If it has to change, use a permanent server-side redirect and expect fluctuations while Google recrawls
- Change the date only when the content substantially changed, and keep the visible date,
dateModifiedandlastmodin step - Request indexing once, then compare the page against a similar earlier period, not against last week
- A rewrite can go quiet for weeks before it settles, so don’t roll back on two weeks of data
Frequently Asked Questions
Should I keep the original publish date when I update a post?
Yes. Keep the published date and change only the updated one. Google says “our systems look at several factors to determine our best estimate of when a page was published or significantly updated”, so resetting the publish date to make an old post look new is the kind of date change its helpful content guidance warns about. Showing both dates also tells a reader the post has a history and has been looked after.
Is it better to update an old post or write a new one?
Update it when the new material answers the same search the old post ranks for. Write a new post when it answers a different question, and link the two. Two posts chasing the same query compete with each other, and the older one usually has the links and history the new one lacks. A content brief that says what each post must not cover is the cheapest way to keep them apart.
Should I delete old blog posts that get no traffic?
Not as a freshness tactic. Google’s own self-assessment asks: “Are you adding a lot of new content or removing a lot of older content primarily because you believe it will help your search rankings overall by somehow making your site seem "fresh?" (No, it won't)”. Fix a post that is wrong, merge it into a closely related one with a permanent redirect, or leave it alone. Deleting it only removes an entry point.
Will changing an old post’s title hurt its rankings?
It can if the new title stops matching the searches the post is shown for, so check those in Search Console first. Either way, the change will not show straight away. Google says it “has to recrawl and reprocess the page to notice updates to these sources, which may take a few days to a few weeks”, and that “If you’ve made changes, you can request that Google recrawl your pages.”
How often should an old blog post be updated?
When something in it stops being true, and on a schedule set by how fast the topic moves. On this blog, posts about AI search, tool roundups and platform specifications get a full pass every two quarters, because prices, rosters and limits change that fast. Evergreen how-tos get one a year, or sooner if a cited source disappears. The SEO blog best practices that every post has to meet don’t change on refresh.
Final Thoughts
Start with the post on your site that has the most impressions and the oldest sources. Export its queries and its weekly impressions today, fix what is no longer true, request indexing once, and put a date four weeks out in the calendar to compare it against the same stretch before the edit.
Got posts that rank but have gone stale?
ClubUnbrick plans, writes and refreshes long-form content for businesses, starting from the Search Console data behind each post.
What We Offer
- Content refreshes — Older posts re-sourced and relinked so they keep earning traffic.
- Content calendars — Monthly plans built from your own Search Console queries.
- Content briefs — The searches, boundaries, sources and links for each post, settled before writing starts.
- Researched articles — Blog posts and guides with every citation checked against its original source.
You can start with a single post and see how it performs.
