Your blog has a few dozen posts. Some were written when the site launched, a few by a writer you no longer work with, and one or two still mention a price or a phone number that changed long ago. You know some of them are out of date, but you do not know which ones matter, and writing something new always feels more productive than going back.
It often is not. When you update old blog posts carefully, you build on pages that are already indexed, already linked and sometimes already appearing in searches. This guide shows how to choose which posts to refresh using Search Console, what to change, how to keep the address and its search history intact, and how to handle the published date honestly. Deleting posts is a separate decision and not covered here.
Why a content refresh can beat a new post
A new post starts from nothing. Google has to find it, decide what it is about and work out whether it deserves to be shown. An existing post has already been through some of that. If it is close to being useful for a search but not quite there, improving it can be the quickest way to more visitors from that topic.
A refresh also protects your reputation. A reader who lands on a post with old fees, discontinued products or rules that have changed does not think “this post is old”. They think “this business is careless”. Fixing that has value even if search traffic never changes.
Finding which posts to update in Search Console
Search Console’s Performance report is the best free source for choosing candidates. Set the date range to a long period, switch to the Pages view and work through these patterns. Our guide to reading the Search Console Performance report explains each control if you are new to it.
Posts that are slipping
Compare a recent period with the same length of time earlier. Pages whose clicks have fallen noticeably are worth a look. Often a competitor has published something more complete, or the post’s facts have aged.
Posts seen often but rarely clicked
Sort by impressions. A page that appears in many searches but gets few clicks may have a title and description that do not match what people want, or it may appear for searches it does not really answer.
Posts ranking for questions they do not answer
Click into a page and look at the queries it appears for. If people find it for a question the post only mentions in passing, that is a clear instruction: answer that question properly, either in this post or, if it is a different topic, in a new one.
Posts close to the first page
A page whose average position sits just below the top results for a relevant query is a good candidate. Small improvements in completeness and clarity can matter here.
Posts nobody sees but you know are important
Search Console will not flag every post with wrong information. Make a separate list of posts that mention prices, rules, opening hours, staff, products or anything else that changes. Check those on a regular schedule regardless of traffic.
How to update old blog posts: deciding what to change
Open the post next to the current top results for its main search, and read both as a customer would. Then work through this list:
- Facts. Correct anything that is no longer true. Check every price, rule, procedure, product name and contact detail.
- The answer. Is it near the top? If the post takes several paragraphs to reach the point, move the answer up.
- Gaps. Add the follow-up questions the post misses, including the ones Search Console shows people are searching.
- Your knowledge. Add examples and details from doing the work since the post was written. This is the part competitors cannot copy.
- Clutter. Remove outdated sections, generic filler and anything that no longer serves the reader.
- Headings. Make sure they describe the sections and follow the order a reader thinks in.
- Links. Fix broken links, update links to pages that have moved and link to newer related posts. Our broken link checker can find dead links quickly.
- Title and description. If impressions are high and clicks low, rewrite them to describe what the page now offers.
- Images. Replace outdated screenshots and photos, and check they are compressed with alt text.
Not every post needs all of this. A post with one wrong price needs one fix. A post that has slipped behind competitors may need a substantial rewrite.
Keeping the URL and its history
The most common mistake when refreshing a post is changing its address. The page’s address is what Google has indexed and what other pages link to. Change it, and you start much of that over, unless you redirect the old address properly.
- Keep the slug even if it is not perfect. A slightly awkward address that has a history is usually worth more than a neat new one.
- If you must change it, set up a permanent redirect from the old address to the new one, then update your own internal links. See how to set up a 301 redirect in WordPress.
- Do not publish the refresh as a new post while leaving the old one live. You end up with two pages competing for the same search.
- If two old posts overlap, combine them into the stronger one and redirect the weaker address to it.
Handling dates honestly
WordPress records when a post was first published and when it was last modified. Many themes show one or both. How you handle these affects trust.
- Show an “updated” date only for real updates. Changing a comma does not make a post current. Revising facts, adding sections or rewriting the answer does.
- Do not change the original published date to make an old post look new. Readers and search engines can often tell, and it undermines trust when they do.
- Consider a short note for significant changes, such as a line near the top saying what was updated. This helps returning readers and shows care.
- Check your theme. Some themes show only the published date, some only the modified date. Make sure what is displayed is accurate and useful to readers.
Google uses several signals to work out a page’s date, and its guidance for site owners discourages freshening dates when the content has not really changed. Trying to look newer than you are is not worth the risk.
Making the update safely in WordPress
- Copy the current version before you start. WordPress keeps revisions, which let you roll back if needed; our post on WordPress revisions explains how they work.
- Edit in place. Work on the existing post rather than creating a new one.
- Preview on a phone before updating, to check headings, tables and images.
- Update, then check the live page loads correctly and the address has not changed.
- Request indexing in Search Console’s URL inspection tool if the changes are significant. It is a request, not an instruction, but it can help Google notice the change.
- Note the date and what you changed, so you can compare performance later.
Judging whether the refresh worked
Give it time. Search results can move around for a while after a page changes. Compare a period after the update with a similar period before it, using the same Search Console view you used to choose the post. Look at impressions, clicks, the queries it appears for and, if you track them, enquiries from the page.
If nothing improves after a reasonable wait, look again. The page may need a deeper rewrite, or the topic may simply attract few searches, in which case accuracy for the readers who do arrive is the goal.
Refreshing is one part of a wider content routine covered in the guide to content marketing for small businesses. For how content work fits alongside search, ads and email, see our overview of digital marketing services.
Frequently asked questions
How do I keep track of which posts I have already refreshed?
A simple spreadsheet works: one row per post with its address, the date you last reviewed it, what you changed and anything that needs checking again, such as prices. Sort by the review date to see which posts have gone longest without attention.
Will updating a post make it drop in search for a while?
It can move around briefly while Google processes the changes, especially after a large rewrite. As long as the address stays the same and the page answers its question better than before, any wobble is usually temporary. Avoid changing many important pages at once so you can see what each change did.
Should I update a post that is doing well already?
Check its facts and links, but be careful with big changes. If a post brings steady visitors and enquiries, keep the structure and answer that work. Add missing detail or correct anything outdated, then watch how it performs before doing more.
If you have a backlog of posts that need reviewing and no time to work through them, our content writing and refresh work includes going through older pages each month, starting with the ones Search Console suggests matter most.
Next in this series: FAQ Content for Websites: Real Questions, Short Answers
