How to Update Old Blog Posts (and Which Ones to Refresh First)

To update old blog posts, start with Search Console. Find posts whose clicks have fallen against an earlier period, queries sitting just off page one, and pages with a weak click-through rate. Then decide whether each one needs a refresh, a merge, a redirect or removal. Make real improvements, and only change the "updated" date when the content has substantially changed.

After a few years, most small business blogs have a handful of posts bringing in the traffic and the rest slowly going out of date. Refreshing old content for SEO is often a faster win than writing new posts, because those pages already have URLs Google knows, some links, and impressions you can measure.

Why update old blog posts at all

Old posts lose ground for ordinary reasons. Prices, laws and screenshots change, a competitor publishes something more complete, the intent behind a query shifts, or your own newer posts start competing with the older ones.

None of this means Google dislikes old content. When CNET deleted thousands of older articles in 2023, Google's Danny Sullivan asked whether people were deleting content "because you somehow believe Google doesn't like 'old' content?" and answered: "That's not a thing! Our guidance doesn't encourage this" (MediaPost). Age isn't the problem. Being out of date, thin or unhelpful is. The goal of a refresh is to make the page the most useful answer again, not to look new.

How to choose which posts to refresh

Don't refresh at random. Google Search Console is free and gives you the three signals that matter most.

1. Posts with declining clicks

In the Performance report, open the Date filter, choose Compare, and pick two periods, such as the last three months against the same months last year to allow for seasonality. Google suggests weekly or monthly granularity to smooth out day-of-week differences (Search Console Help: advanced filtering and comparison).

Then open the Pages tab and sort by the Difference column to find "queries or pages with significant change from a previous period" (Search Console Help: common tasks). The biggest losers are your first candidates.

Before you rewrite anything, rule out a site-wide cause. If everything dropped on the same day, suspect a technical problem or a core update, not one stale post. Our guide on how to recover from a traffic drop covers that diagnosis.

2. Page-two queries

Click into a page, switch to the Queries tab, and look at average position. Queries averaging roughly positions 8 to 20 are close enough to page one that a better answer can move them. Remember that average position is "the average position of the topmost result from your site" (Search Console Help: Performance report), so treat it as a trend, not an exact rank.

These queries also tell you what to add. If a boiler servicing post gets impressions for "how often should a boiler be serviced UK" but never answers it, you've found a new section.

3. Low click-through rate

CTR is "the click count divided by the impression count" (Search Console Help: Performance report). A page with lots of impressions and a weak CTR for its position usually has a title or snippet that doesn't match what people want, or looks dated. Select the CTR metric, open the Pages tab and sort by CTR ascending (Search Console Help: common tasks). Our post on title tags and meta descriptions covers the fix.

Doing this without spreadsheets

Make It Flow's Search Console dashboard is free on every plan. It pulls in your top pages and keywords, lists "quick wins" (keywords in positions 8 to 20) and flags titles losing clicks, which covers the first pass of this triage. It works from your own Search Console data. Our keyword opportunities finder goes further, listing low-CTR, rising and question queries. It won't tell you search volumes or what competitors rank for.

Refresh, merge, redirect or delete

Once you have a shortlist, decide what each post needs. Most need a refresh. Some shouldn't exist as separate pages at all.

Merging and redirecting

Merging is the usual fix for keyword cannibalisation. Pick the URL with the most clicks and links, fold in anything useful from the others, then 301 the old URLs to it.

Google's site move documentation recommends server-side permanent redirects such as 301 or 308, says to avoid redirect chains, and advises keeping redirects in place for at least a year. It also says not to send lots of old URLs to an unrelated page like the homepage, though redirecting several old pages to one page that consolidates their content is fine (Google Search Central: site moves with URL changes). See 301 vs 302 redirects if you're unsure which to use, then test live redirects with our free redirect checker.

Deleting: be careful

Content pruning is often sold as a quick ranking boost. Google is more cautious. In the same exchange about CNET, Sullivan said an old, irrelevant page "isn't likely to rank well," and that removing it "might mean if you have a massive site that we're better able to crawl other content on the site." But he added that "it doesn't mean we go 'oh, now the whole site is so much better'" because of one page (MediaPost).

Google's helpful content guidance also lists this as a warning sign: "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?'" Google's answer, in brackets: "No, it won't" (Google Search Central: creating helpful content).

Delete a post when it has no value to readers, not to chase a sitewide lift. When you do, let the URL return a 404 or 410 status code, which is what Google's site move documentation recommends for content you aren't keeping (Google Search Central). Then check your other pages don't still link to it.

What a real content refresh involves

A refresh means going through the post as if you were publishing it today.

Accuracy

Check every fact, price, law and screenshot. Tax thresholds, regulator names and rules change. Remove claims you can't back up, and link sources for the rest.

Search intent

Search the main query on Google in your target country and look at what ranks now. If the top results are step-by-step guides and yours is an opinion piece, the format needs to change. Our guide to search intent explains how to read the results.

New sections

Turn the page-two queries into short sections or FAQ entries, and cut sections that no longer earn their place.

Length and readability

Longer isn't automatically better. Our post on how long a blog post should be covers why length should follow the topic. Paste the draft into the free word counter to see where you stand, and run it through the readability checker to catch sentences that have grown tangled over years of edits.

Internal links

Link from the refreshed post to relevant pages you've published since, and from newer related posts back to it. Our internal linking strategy covers anchors.

Images

Replace outdated screenshots, compress anything heavy, and write proper alt text.

Broken links

Outbound links rot as sites move and close. Run the page through our free broken link checker and fix anything returning an error.

Title and meta description

Rewrite these last, and drop any year you won't keep updating.

Dates: when to change them and when not to

This is where many content refreshes go wrong.

What Google says about byline dates

Google's documentation describes a byline date as "the date that Google estimates that the web page was updated or published." It recommends labelling dates clearly, "with text like 'Publish' or 'Last updated'", and says you can show a publication date, a last updated date, or both. It also says dates "must describe the publication or update date of the page," and that visible and structured dates should be consistent (Google Search Central: publication dates).

Don't fake freshness

Google's helpful content guidance asks site owners directly: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" (Google Search Central: creating helpful content). It appears in a list of warning signs of content made for search engines rather than people.

The practical rule: fixing a typo or swapping one link is not an update. Rewriting sections, correcting facts, adding new material or restructuring the post is. Only change the "Last updated" date for the second kind, and keep the original publication date visible where it helps readers.

dateModified in Article structured data

If your blog uses Article or BlogPosting structured data, Google lists datePublished and dateModified as recommended properties. It describes dateModified as "the date and time the article was most recently modified, in ISO 8601 format," and recommends including timezone information (Google Search Central: Article structured data). For example:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Choose a Boiler for a Victorian Terrace",
  "datePublished": "2023-03-14T09:00:00+00:00",
  "dateModified": "2026-11-20T10:30:00+00:00"
}

Make sure dateModified matches the visible "Last updated" date. Some CMS themes change it on every save, including trivial ones, so check what yours does.

Getting the refreshed post recrawled

Request indexing in URL Inspection

For your most important refreshed posts, paste the URL into Search Console's URL Inspection tool and click Request indexing. Google says there's a quota for individual URL submissions, that asking repeatedly won't speed things up, that a request doesn't guarantee inclusion, and that crawling "can take anywhere from a few days to a few weeks." For larger batches it recommends submitting a sitemap instead (Google Search Central: ask Google to recrawl your URLs).

Keep sitemap lastmod honest

Google's sitemap documentation says it "uses the <lastmod> value if it's consistently and verifiably accurate." It counts a change to the main content, the structured data or the links on the page as significant, and notes that updating a copyright date isn't (Google Search Central: build and submit a sitemap). If your sitemap bumps lastmod on every URL each night, it isn't accurate, so Google has little reason to trust it.

Your content refresh checklist

1. Compare two periods in Search Console and list the biggest click losers.
2. Rule out site-wide causes first.
3. Note each candidate's page-two queries and CTR.
4. Decide: refresh, merge, redirect, delete or keep.
5. Set up 301s for merges and redirects, and test for chains.
6. Let deleted URLs return 404 or 410, and remove internal links to them.
7. Check facts, prices and screenshots, and cite sources.
8. Match the format to what ranks now.
9. Add sections for page-two queries, and cut dead weight.
10. Check length, readability, images and broken links.
11. Add internal links to and from newer posts.
12. Rewrite the title and meta description.
13. If changes are substantial, update the visible date, dateModified and lastmod together.
14. Request indexing for key URLs, then compare clicks and CTR after a few weeks.

Keep a simple log of what you changed and when, so you can tell later which refreshes worked.

FAQ

How often should you update old blog posts?

There's no fixed schedule from Google. Review your posts against Search Console data every few months and refresh the ones losing clicks, sitting on page two or going out of date. Time-sensitive topics such as tax rules, prices or software need checking more often than evergreen explainers. Update when something has actually changed, not to hit a calendar.

Should I change the date when I update a blog post?

Only if the update is substantial. Google's helpful content guidance warns against changing dates to make pages seem fresh when the content hasn't substantially changed. If you rewrote sections or corrected facts, show a clear "Last updated" date and match dateModified and sitemap lastmod to it. For typo fixes, leave the date alone.

Is it better to update old content or write new posts?

Often, updating comes first. A post that already gets impressions has a URL Google knows and queries you can measure, so improvements can show up sooner. Write a new post when the topic is genuinely different. If a new post would target the same query as an existing one, improve the existing post instead to avoid cannibalisation.

Does deleting old blog posts help SEO?

Not by itself. Google's Danny Sullivan said the idea that Google dislikes old content is "not a thing," and that removing a page doesn't make the whole site seem better. Delete posts with no value to readers, no traffic and no links. Merge or redirect anything with overlap or backlinks, and let removed URLs return 404 or 410.

Should I change the URL when refreshing a post?

Usually not. Keeping the same URL keeps its history and any links pointing at it. Only change it if the current slug is misleading, such as one with an old year in it, and if you do, add a permanent 301 redirect from the old URL to the new one and update your internal links.

How long does it take to see results from a content refresh?

Google says crawling can take from a few days to a few weeks, and you can request indexing for important URLs to prompt a recrawl. Rankings may take longer to settle after that. Compare the same length of period before and after the update in Search Console, and give it several weeks before judging.

Sources

• Google Search Central: Influence your byline dates in Google Search
• Google Search Central: Creating helpful, reliable, people-first content
• Google Search Central: Article structured data
• Google Search Central: Build and submit a sitemap
• Google Search Central: Ask Google to recrawl your URLs
• Google Search Central: Site moves with URL changes
• Search Console Help: Performance report (Search results)
• Search Console Help: Advanced filtering and comparison
• Search Console Help: Common tasks and use cases
• MediaPost: Google warns against content pruning as CNET deletes pages