What Do I Do With Old Blog Posts?

Every old blog post runs through this decision tree:

Action 1: Keep and update

Posts that pass any one of these tests:

• 50+ organic sessions per month from Search Console
• Earned backlinks from 3+ referring domains
• High keyword position (1-15) for a target keyword
• Recently linked from a high-value referring domain

For each keeper:

• Update date stamp in title and meta (if relevant)
• Refresh outdated stats, prices, or examples
• Add or update an internal link section pointing to your service pages
• Improve schema (Article, FAQ if applicable)
• Tighten introduction for stronger hook
• Republish with the original URL preserved

Time investment: 30-60 minutes per post. Result: posts gain rankings instead of losing them in a refresh.

Action 2: Consolidate

When two or more posts cover similar topics shallowly, merge them into one stronger post. Example: you have three posts on “WordPress security tips” from 2019, 2020, and 2022. Each is 600 words. Combined and updated, you get one 1,800-word definitive post.

The consolidation process:

• Pick the strongest URL of the candidates (most backlinks, best ranking)
• Combine the best content from all candidates into that URL
• 301 redirect the other URLs to the surviving one
• Update internal links pointing to the redirected posts

Result: one strong post beats three weak ones, every time.

Action 3: Redirect

Posts that aren’t worth updating but have some history (backlinks, occasional traffic, or just an indexed URL) get 301 redirected to the closest topical match. Priority order:

1. The nearest blog post that still exists
2. The relevant service page
3. The blog index or category page
4. The homepage (last resort only)

Never 404 a post that has any backlink history. Always 301 it.

Action 4: Delete (with redirect)

Truly worthless posts — abandoned drafts, duplicate content from a previous developer, test posts, content from a different business — get deleted. But even these need 301 redirects to the closest replacement, because some search engines or referring sites may still link to them.

Tampa businesses have specific seasonal content patterns:

• Hurricane prep posts — keep, update annually
• Gasparilla event coverage — usually consolidate annual posts into one evergreen “Gasparilla for [your business]” piece
• Annual prediction posts (“Best Tampa restaurants 2019”) — either update yearly to current year, or convert to evergreen (remove year, focus on selection criteria)
• Specific promotion announcements — redirect to current promotions or service page

The rule: time-stamped content either gets updated annually or converted to evergreen. Letting it sit unupdated harms your topical authority.

Republishing an old post (updating the publish date so it appears recent) is sometimes useful, sometimes harmful:

Republish when:

• The post has been substantially updated (new content, new examples, new structure)
• The original publish date is so old it appears stale in search results
• You want to feature the post in newer sections (homepage, newsletter)

Don’t republish when:

• You only made minor tweaks (typo fixes, broken link updates)
• The post is ranking well — don’t disturb a working signal
• You’re worried about “looking old” but haven’t actually updated content

Misusing republish dates (without actually updating content) can be perceived by Google as a signal manipulation. Update the content meaningfully before changing the date.

For a typical Tampa SMB blog with 30-100 posts:

1. Export Search Console queries for the last 16 months — every post that received impressions
2. Export GA4 page report — sessions per post for the last 12 months
3. Run Ahrefs Site Explorer at the post-URL level — backlinks per post
4. Combine into a single spreadsheet — one row per post, four columns: sessions, impressions, backlinks, content quality
5. Tag each row — keep / update / consolidate / redirect / delete
6. Owner reviews — usually 1-hour call
7. Final action list locks the post audit

This audit takes a day. It usually identifies 10-20 hours of update work — well worth doing during a redesign rather than as a separate project later.

Three questions before you decide what to do with your blog archive:

1. What’s currently driving traffic? If you don’t know, run the GA4 report before doing anything. Posts you assume are dead may be quietly bringing 30% of your traffic.
2. What’s earned backlinks over time? Search Console and Ahrefs answer this. Don’t destroy backlink equity by deleting indexed URLs without 301s.
3. What’s the future plan for blog content? If you’ll publish 1-2 posts a month going forward, the old archive matters more (less new content to dilute it). If you’re publishing 8 posts a month, old archive matters less.

The full keep-cut-merge framework for non-blog pages is in which pages should I keep in a redesign. Same logic, applied to blog posts.