I have been building websites for more than 15 years, and I have run content sites with a lot of pages on them. One thing I learned the hard way is that publishing is only half the job. A post you wrote two years ago can still be getting found in Google every single day, and if it's out of date, it's quietly telling every one of those visitors that nobody is home.

Most people treat their blog like a conveyor belt. Write it, publish it, forget it, write the next one. I get it. New posts feel like progress. But some of the easiest wins on any site are sitting in the archive.

Here is how I update old blog posts without wasting time on changes that don't matter.

Why updating old posts is worth your time

A new post starts from zero. Nobody has linked to it, Google hasn't figured out what it's about yet, and it has no history. An old post that already gets some impressions in search has a head start. You're improving something that's already in the race instead of building a new car.

Updating also protects your reputation. If someone lands on your post about building a website and the screenshots show a tool that doesn't look like that anymore, or the prices are from three years ago, they're gone. Worse, they remember your name as the site with the stale info.

And there's a practical reason. Google's guidance on creating helpful, people-first content asks questions like whether your content gives a substantial, complete description of the topic and whether it has easily verified factual errors. An outdated post fails those questions over time even if it was great the day you hit publish.

What updating does not mean

Before we get into the how, let's clear up the biggest myth.

Updating a post does not mean changing the date and hitting save. Google calls this out directly. In that same helpful content guide, one of the warning signs it lists is "changing the date of pages to make them seem fresh when the content has not substantially changed." It also says adding or removing a lot of content just to make your site seem "fresh" won't help.

So if the only thing you changed was a comma and the date at the top, leave the date alone. A real update means the post is genuinely more useful, more accurate, or more complete than it was before.

Step 1. Find the posts worth updating

You can't update everything, and you shouldn't try. Start with the posts where an update has the best chance of mattering.

My go-to place is the Performance report in Google Search Console. It shows how often your pages appear in search (impressions), how often people click, your click-through rate, and your average position. Here's what I look for:

  • Posts with lots of impressions but few clicks. Google is showing them, but people aren't choosing them. Usually that's a title or description problem, or the post looks dated.
  • Posts that used to do better. Compare a recent date range to an older one. If clicks have been sliding, something changed. Maybe competitors published better pages, or your info got stale.
  • Posts sitting just off page one. If a post averages somewhere on page two for a search you care about, it's often closer to page one than a brand new post would be.
  • Posts tied to your business. A post that leads to a service, product, or signup is worth more attention than a random post that will never bring you a customer. I wrote more about that problem in why your blog gets traffic but no leads.

Then I add my own common sense. Any post with dates, prices, tool names, rules, or screenshots in it is a candidate, because those things go out of date fastest.

Make a simple list. Post URL, the search it should show up for, and what you think is wrong with it. That list is your update queue.

Step 2. Figure out what the post is supposed to rank for

Before touching a word, get clear on the search you want the post to show up for. Sometimes the post was written without a real target, and that's the whole problem.

In the Performance report, click into a single page and look at the queries it already shows up for. You'll often find it's getting impressions for searches you never planned on. That's useful. It tells you what Google already thinks the page is about, and what people actually want when they land there.

Then search that phrase yourself and look at what's ranking. Are the top results step-by-step guides, lists, or quick answers? Are they longer and more detailed than yours, or shorter and more direct? You're not copying anyone. You're figuring out what the searcher expects so your post doesn't miss the point.

If you need a refresher on picking the right phrase, my post on how to do keyword research for a blog walks through it without expensive tools.

Step 3. Fix what's wrong or out of date

This is the part that actually makes the post better. I go through the post top to bottom and ask one question on every section: is this still true, and is this still the best answer?

Here's my checklist:

  • Facts, numbers, and rules. Re-check anything that can change. Prices, limits, laws, tool features, and statistics. If you can't verify something anymore, cut it or soften it. Don't leave a claim on your site you can't back up.
  • Steps and screenshots. Walk through any how-to steps yourself. Apps and websites change their menus all the time. If a step doesn't match what someone sees today, rewrite it.
  • Links. Click every link. Replace broken ones, and swap out links that now go somewhere weaker than when you added them.
  • Missing answers. Look at what the top results cover that you don't. If there's an obvious question your post skips, add a section that answers it.
  • Your own experience. Have you learned something since you wrote it? Done it more times, tried a better tool, made a mistake worth warning people about? That's the stuff no other page has. Add it.
  • Dead weight. Cut the long intro, the filler paragraph, and anything that wanders off topic. Shorter and clearer often beats longer.

The goal isn't to make the post longer. Google's own guide literally asks whether you're writing to a particular word count because you heard Google prefers one, and answers, "No, we don't." The goal is to make it the most useful page for that search.

Step 4. Rework the title, intro, and description

If a post gets impressions but no clicks, this step is usually where the win is.

The title. Make sure it says plainly what the post is and matches what people search. Google's helpful content guide asks whether the title gives a descriptive, helpful summary and whether it avoids exaggerating or being shocking. Clear beats clever almost every time.

The intro. Most old intros take too long to get going. Get to the point in the first few lines so the reader knows they're in the right place.

The meta description. Rewrite it so it sells the updated post. I covered my simple formula in how to write a meta description that gets clicks.

Step 5. Keep the same URL

This one is simple, and it's where I see people hurt themselves. When you update a post, keep the URL exactly the same.

That URL is where the history lives. Other sites may link to it, it's in your own internal links, and it's the address Google already knows. Change it and you risk losing that history unless you set up redirects properly.

If you truly have to change a URL, for example because the old slug has a year in it, use a permanent redirect from the old address to the new one. Google explains how in its guide to redirects and Google Search. But my default advice is don't change it at all. It's also why I never put a year in a slug anymore. The post can be updated forever, and the URL never looks out of date.

Step 6. Add internal links both ways

An updated post is a good excuse to tighten up your internal links.

First, link out from the updated post to your other related posts where it genuinely helps the reader. Second, and people forget this one, go find your other posts that mention the same topic and link back to the updated post. That's how you tell visitors, and Google, that this page matters.

Use plain, descriptive anchor text. "How to update old blog posts" is better than "click here." If you want more ways to get links pointing at your best pages, I wrote about getting backlinks without begging for guest posts.

Step 7. Update the date honestly and let Google know

Now, and only now, change the date. If you made real, meaningful changes, show it. Google's guide on influencing byline dates recommends a visible date labeled clearly, like "Published" or "Last updated," and it says the dates you show on the page should match the dates in your structured data. On a blog, that's usually the datePublished and dateModified fields.

I like showing an "Updated" date on posts that got a real refresh. It's honest, and it tells the reader the info is current.

Then you can ask Google to take a fresh look. The URL Inspection tool in Search Console lets you check a page and request indexing. It's not a magic button, and you don't need to do it for every tiny tweak, but after a big update it's worth the 30 seconds.

Step 8. Check back in a few weeks

Write down the date you updated the post. Then come back in a few weeks and compare the Performance report for the period after the update to a similar period before it.

Did impressions go up? Did the click-through rate improve? If not, look again. Maybe the title still isn't matching what people want, or the competition simply has a better page and you need a bigger rewrite.

This is what turns updating from a one-time chore into a habit. You learn what kinds of changes actually move the needle on your site.

How often should you update old blog posts?

There's no magic schedule. I don't update posts just because a calendar says so. I update them when there's a reason, like something in the post changed, the numbers in Search Console are slipping, or I have something genuinely better to say.

What does help is having a routine. Even a little time each month going through your update queue adds up. A blog that gets maintained beats a blog that only gets added to.

Mistakes to avoid

  • Changing the date without changing the post. Google specifically warns against it, and readers can tell.
  • Changing the URL for no reason. Keep the address unless you absolutely have to move it, and redirect if you do.
  • Padding the post. More words isn't the goal. Better answers are.
  • Deleting posts in bulk to look fresh. Google says removing a lot of older content just to seem fresh won't help your rankings.
  • Forgetting the reader. Every change should make the post more useful to the person who searched for it. If it doesn't, skip it.

Final thoughts

If you have a blog with more than a handful of posts, you're probably sitting on some easy wins. Pull up Search Console, find the posts Google is already showing, and make them the best answer they can be. Keep the URL, update the date honestly, and check back.

New content is fun. But updating old content is often the faster way to get more out of what you've already built.

If you want help getting your website and content set up to actually bring in business, that's what I do with Built by Knup.

FAQ

Does updating old blog posts help SEO?

It can, when the update makes the post genuinely more accurate, complete, or useful. Google's guidance is focused on helpful content, and it warns that changing dates or adding and removing content just to look fresh won't help.

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

Only if you made meaningful changes. Google lists changing a page's date to make it seem fresh, when the content hasn't substantially changed, as a warning sign. When you do update it, show a clearly labeled date like "Last updated" and keep it consistent with your structured data.

Should I change the URL of an old blog post?

Usually no. The existing URL carries the post's links and history. If you must change it, use a permanent redirect from the old URL to the new one.

How do I know which old posts to update first?

Start with Google Search Console's Performance report. Look for posts with lots of impressions but low clicks, posts whose clicks have dropped over time, posts sitting just off page one, and posts tied to your business.

Should I delete old blog posts?

Not in bulk just to make the site look fresh, since Google says that won't help. Look at each post on its own. If it's still useful, update it. If it's truly outdated and nobody needs it, decide carefully and redirect it to a related page when that makes sense.

Built by Knup

Skip the guesswork

You can do it yourself, have me build it for you, or build it together so you understand how it all works.