To refresh an old blog post, pick one that already gets impressions, fix anything wrong or out of date, add what readers now expect, keep the same URL, and update the visible date only if the content changed substantially. Google warns against changing dates to make pages look fresh.
Why refresh instead of writing something new
An old post already has a URL, links from other pages and a place in the index. Rewriting it keeps all of that. A new post starts from nothing. For a small team that publishes a few times a week, a refresh is often the cheaper way to move a page that sits just off the first page.
Step 1: choose the right posts
Do not refresh by age. Refresh by evidence. In Search Console, look for pages that get impressions but few clicks, or that lost traffic. Google's helpful content guidance suggests this approach for audits: review the pages that lost traffic, see which were affected and for what searches, then check them against its questions.
A short list to start with:
- Posts that show impressions but a low click rate.
- Posts whose traffic fell after months of being steady.
- Posts that mention tools, rules or numbers that have since changed.
Step 2: find what is wrong with the current page
Search the post's keyword and read the top results. Write down the question each one answers in its first paragraph, then check whether yours does. Common faults in old posts:
- The answer is buried below a long introduction.
- A statement was true when written and is now out of date.
- Links point to pages that moved or no longer exist.
- The post covers the topic but never answers the exact question people type.
Our own posts show how fast things shift. The guide to FAQ schema had to reflect that Google stopped showing the rich result. A post written before that change would now give bad advice.
A worked example
Take a post called "How to write a robots.txt file" that got steady impressions for a year, then slipped. You search the keyword and see that the top results open with a two-line answer and a short example file, while yours opens with three paragraphs of history. The fix is not a rewrite from scratch. Move the answer to the top, add an example file, remove the history, correct the one rule that changed, and update the date because the answer itself changed. Then note the date and check the page's clicks and position again in a few weeks.
Step 3: change what matters
Google's guidance asks whether a post offers "original information, reporting, research, or analysis" and whether it has easily verified factual errors. Use that as your edit list:
- Fix facts first. Check each claim against its source and replace anything stale.
- Put the answer at the top. A 40 to 60 word direct answer makes the page easier to quote.
- Add something the other results lack. A worked example, a decision table or your own data.
- Repair links. Replace dead ones and link to your newer related posts.
- Cut padding. Delete paragraphs that restate the heading.
Google also says not to add or remove content mainly to look fresh to search systems. Every edit should serve a reader.
Step 4: handle the date honestly
Google's date guidance says dates should describe when the page was published or updated, be consistent between visible text and structured data, and never be in the future. Its helpful content page lists changing dates when the content has not substantially changed as a warning sign.
A workable rule: if you corrected a typo, leave the date. If you rewrote the answer or replaced the facts, show a "Last updated" date. Sitemaps follow the same logic. Google says to update lastmod only for significant changes, as covered in the XML sitemap guide.
Step 5: keep the URL and measure
Keep the address the same so existing links and rankings carry over. Then wait. Google's starter guide suggests waiting a few weeks before judging whether changes worked. Compare impressions, clicks and average position for that page before and after, and write down what you changed so you can learn which edits help.
When to rewrite, merge or delete
| Situation | Action |
|---|---|
| Right topic, weak or outdated content | Refresh in place |
| Two posts answer the same question | Merge into the stronger one and redirect the other |
| Topic no longer matters to your readers | Remove it or leave it alone |
| Post is fine but gets no impressions | Check indexing first, using this guide |
Frequently Asked Questions
How often should I update a blog post?
There is no schedule that Google endorses. Update when facts change, traffic drops, or you can improve the answer.
Does updating the date improve rankings?
Not by itself. Google lists changing dates without substantial changes as a warning sign.
Should I change the URL when I refresh a post?
No. Keep it, so links and rankings stay attached to the page.
Can I refresh a post that gets no traffic?
First confirm it is indexed. If it is not in the index, no edit to the text will matter yet.
Is it better to refresh or publish a new post?
Refresh when the topic is right and the page is weak. Publish new when you have a question no existing post answers.