Old Posts Audit (2007-2010)

Audit Date: 2024-11-16 Total Old Posts: 105 out of 137 (77%)

Distribution by Year

Why Update Old Content?

1. Broken Links: Technology links from 15+ years ago are likely dead
2. Outdated Information: Tech changes rapidly; what was true in 2008 may not be now
3. SEO Value: Updated content ranks better
4. Historical Context: Add perspective on how things have evolved
5. Screenshot/Images: Old images may be broken or low quality

Recommended Actions

Option 1: Update & Refresh

For posts with evergreen topics:

• Add “Updated [Date]” notice
• Update broken links or remove them
• Add modern context in an “Update” section
• Keep historical perspective but add current relevance

Option 2: Archive with Context

For dated content that’s still interesting:

• Add historical context banner
• Note what has changed since
• Keep as-is but with disclaimers
• Add “Read this for historical perspective” note

Option 3: Consolidate

For related old posts:

• Combine multiple short posts into one comprehensive post
• Keep URL redirects for SEO
• Create new comprehensive guide from old content

Option 4: Remove/Redirect

For truly obsolete content:

• Remove posts about dead services/products
• 301 redirect to relevant current content
• Keep URL structure for SEO

Priority Categories

🔴 High Priority - Update Immediately

Technology-focused posts (likely have broken links and outdated info):

• Posts about specific tools/services that may be defunct
• Technical tutorials that reference old versions
• Posts with external links to old services

Action: Review for broken links, update or add historical context

🟡 Medium Priority - Review and Decide

General tech commentary (may still be relevant):

• Industry observations
• Startup stories
• Tech philosophy posts

Action: Add update section with current perspective

🟢 Low Priority - Archive with Notice

Personal updates (historical value only):

• Personal blog announcements
• Event recaps
• Time-specific updates

Action: Add archive notice, keep for historical record

Sample Posts to Review

Based on the search, here are some old posts that likely need attention:

1. 2008-02-12-outsourcing-development-work-to-india.md

   • Topic: Still relevant
   • Action: Add 2024 perspective on outsourcing

2. 2007-10-10-google-phone-will-take-on-microsoft-not-apple.md

   • Topic: Android predictions (historical interest!)
   • Action: Add “How this prediction turned out” section

3. 2009-01-28-kwippy-feed-for-wordpress.md

   • Topic: Defunct service
   • Action: Add context about Kwippy’s closure, link to main Kwippy story

4. 2008-12-02-pownce-gone-use-kwippy.md

   • Topic: Both services now defunct
   • Action: Historical perspective on early social media competition

5. 2007-09-20-payment-gateways.md

   • Topic: Likely outdated payment info
   • Action: Update with current payment landscape or archive

Update Template

When updating old posts, use this template:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

---
title: "Original Title"
date: "YYYY-MM-DD"  # Keep original date
lastmod: "2024-11-16"  # Add modification date
# ... rest of frontmatter
---

> **📅 Historical Note:** This post was originally published in [YEAR]. While the core insights remain valuable, some details may be outdated. I've added updates where relevant.

[Original content]

## Update [2024]

[Add modern perspective, what changed, how things evolved, etc.]

---
*Originally published: [Date]*
*Last updated: [Date]*

Bulk Operations Checklist

Week 1: Broken Link Audit

• Run broken link checker on all 2007-2010 posts
• Identify posts with most broken links
• Fix or remove broken links

Week 2: Kwippy-related Posts

• Find all posts mentioning Kwippy
• Add consistent historical context
• Cross-link to main Kwippy story post

Week 3: Technical Posts

• Review posts about specific technologies
• Add “Update” sections with current tools
• Update code examples if still relevant

Week 4: Personal/Event Posts

• Add archive notices
• Ensure images still work
• Add “For historical perspective” notes

SEO Considerations

Keep:

• Original URLs (don’t break external links)
• Original publish dates (shows longevity)
• Original titles (if they rank)

Add:

• lastmod field in frontmatter
• Update/modification notes in content
• Current keywords in updates

Update:

• Meta descriptions to mention historical perspective
• Add schema markup for article updates
• Internal links to newer, related content

Tools Needed

1. Broken Link Checker ✅

   • Created: scripts/check-broken-links.sh
   • Run monthly

2. Content Update Tracker

   • Track which posts have been updated
   • Record what changes were made

3. Archive Banner Generator

   • Automatic notice for posts > 10 years old
   • Template system for updates

Success Metrics

Track these after updating old content:

• Reduction in bounce rate for old posts
• Increase in time on page
• Reduction in 404s from broken links
• Improved search rankings for updated posts
• Social media shares of refreshed content

Next Steps

1. Immediate (This Week)

   • Run broken link checker
   • Identify top 10 posts to update first
   • Create update template

2. Short-term (This Month)

   • Update 5 high-traffic old posts
   • Add archive notices to personal posts
   • Fix broken links in top 20 posts

3. Long-term (This Quarter)

   • Review all 105 old posts
   • Update or archive each one
   • Create content refresh schedule

Status: Ready for implementation Owner: Content team Next Review: 2025-Q1