Updating old posts is one of the highest-leverage things a blogger can do for SEO. A post that already ranks page 1 has earned authority. A small content refresh — better stats, current screenshots, addressing the queries Search Console reveals — often moves that post up several positions without writing a new one.
But updating wrong can hurt rankings. This post is how to do it carefully.
Why updates outperform new posts
A post that already ranks has earned:
- Backlinks (other sites linking to it).
- Time-on-page data Google has observed.
- Internal links from your other posts.
- Social shares.
- Google’s accumulated understanding of the post’s topic.
A new post has none of these. Updating builds on what already exists. Writing a new post starts from zero.
For most blogs after the first year, updating older posts produces more traffic gains per hour of work than writing new ones.
Which posts to update
Open Google Search Console. Look at the “Search results” report. Sort by position. The sweet spot is:
- Position 4–15: almost ranking. Small improvements push them onto page 1.
- Position 20–50: ranking somewhere but not getting clicks. Larger refresh can move them up.
- Posts with high impressions but low click-through rate. Often a meta description or title issue, not a content issue.
What not to update:
- Posts that are already #1 for their main keyword. Don’t fix what isn’t broken.
- Posts with no impressions at all. The content or keyword targeting is wrong; an update won’t help.
- Truly outdated posts on dead topics. Either rewrite as a different post or delete and redirect.
What to update
1. Dates and stats
Any reference to “in 2024” or “this year” needs to be current. Numbers, prices, and statistics that have changed should be refreshed.
2. Screenshots
Software interfaces change. WordPress 6.x looks different from WordPress 5.x. Update screenshots to match the current version.
3. Recommendations
“The best X plugin” lists need to reflect what’s actually best now, not 2 years ago. Add new contenders. Remove discontinued ones.
4. Sections that don’t answer the actual queries
Check Search Console for queries bringing impressions to the post. If your post is showing up for a question and not answering it well, add a section that does.
5. Internal links
Add links to posts you’ve published since the original. Old posts are valuable link sources for new posts.
6. Meta description
Often the original was weak or auto-generated. Rewrite it.
7. Title (carefully)
If the title is dated (“Best Plugins 2023”) or doesn’t match what people search, rewrite it. Don’t change every title — only when there’s a real reason.
What NOT to change
The URL / slug
Never change the URL of a post that ranks. If you must (e.g., the URL contains a year), set up a 301 redirect from old to new. Better: leave the URL alone and update only the title.
The structure too aggressively
If a post ranks for a specific section, deleting that section can drop rankings. Refresh content within sections. Don’t restructure unless you have a clear reason.
Sections that already perform
If a paragraph or example is what’s pulling search traffic, don’t delete it because it feels outdated. Update it. Keep it.
The process
- Pick one post to update. Start with one in the “almost ranking” range.
- Read it as if you’re a new reader. What feels dated? What’s missing? What doesn’t answer the question well?
- Check Search Console for the post. What queries are bringing it impressions? Does the post answer them?
- Edit in the WordPress editor. Update stats, screenshots, examples. Add sections for unanswered queries. Refresh internal links.
- Update the meta description.
- Save. Update modified date. WordPress does this automatically.
- Optional: add a “Last updated: [date]” line to the post.
- Submit the URL to Google Search Console for re-crawling. Use the URL Inspection tool, click “Request indexing.”
Total time per post: 30 minutes to 2 hours depending on how much needs updating.
How often to update each post
- Pillar posts: annually at minimum. These are your most valuable assets.
- Strong supporting posts: annually or as needed when topics shift.
- Date-sensitive posts (e.g., “in 2026”): annually, with year update.
- Tier 3 posts: only when something significant changes.
Build the cadence into your calendar. One post per month = 12 updates per year, which is more than most blogs ever do.
The “Last updated” question
Showing a “Last updated: [date]” line on posts is good for readers (they know it’s current) and good for search (Google notices fresh content).
WordPress doesn’t show this by default. Most modern themes have an option to display the modified date. Some show “Updated: [date]” instead of or alongside “Published: [date].” Either is fine.
The “complete rewrite” exception
Sometimes a post is so outdated that an update is really a rewrite. If 80%+ of the content needs to change, consider:
- Rewriting the post entirely while keeping the URL.
- Or, retire the old post (redirect it to a new, better post).
For high-traffic posts, the rewrite-in-place option preserves more SEO value. For low-traffic posts, retiring and consolidating is fine.
The audit cadence
Once a quarter:
- Pull your top 20 posts by traffic from your analytics or Search Console.
- Check the last update date on each.
- Any post not updated in 12 months: review and update if needed.
- Pull posts in positions 5–15. Pick 3–5 for refresh.
This 1–2 hour quarterly audit reliably surfaces the highest-leverage updates.
The short version
Updating old posts beats writing new ones for most blogs after year one. Focus on posts almost ranking (position 4–15) and posts with high impressions but low CTR. Refresh stats, screenshots, recommendations, and add sections for unanswered queries. Keep the URL. Keep what already works. Update modified date. Request re-indexing. Run a quarterly audit. Compounds over years.
