GEO

Your Old Blog Posts Are Answering for You

An old post with the wrong facts can outrank the page you meant people to find. How to audit and retire stale content.

Kevin Wall · November 3, 2026 · 5 min read

Row of worn antique books with yellowed page edges facing out against a blue wall

The page you meant them to find is on page two

Run a search on your own site for your most important offering. Often the top result is a blog post from three years ago, describing something that has since changed. Answer engines read the same content and can repeat it.

This happens on well-run sites. A post written years ago to explain an offering keeps its rankings after the offering changes, and the description it gives no longer matches how the organization works today.

Why stale posts win

Older posts collect links and history. They often have exact-match titles. The current page may be newer, thinner, or titled for brand rather than for the question people ask. Search engines and site search do not know which one you consider canonical unless you tell them.

Run a stale-content audit

Start with your money questions

List the ten to twenty questions that drive real inquiries: program names, deadlines, services, eligibility. Search each one on your site and in a few AI assistants. Note which page answers.

Flag three kinds of problems

  • Wrong facts. Dates, prices, names, and requirements that changed.
  • Off-message framing. Content that describes your offering in a way you no longer stand behind.
  • Competing pages. Several posts answering the same question differently.

Decide: update, redirect, or retire

Update

If the post still earns traffic and the topic is still right, correct it, add a dated “Updated” note at the top, and link to the current page.

Close-up of a wooden broom resting in a black dustpan on a wood floor

Redirect

If a newer page fully covers the topic, a 301 redirect to that live page keeps the link value. Never redirect to a page that is not published yet.

Retire

If nothing replaces it and the content is wrong, unpublish it and let it return a clean 404 or 410.

Regulatory content needs a dated note

Accessibility, privacy, and compliance posts age fastest. When the DOJ extended the Title II web dates in April 2026, any post with the old dates became wrong overnight. Source: the DOJ interim final rule extending the Title II compliance dates (91 FR 20902). A short dated note, such as “Updated October 2026: compliance dates extended,” tells readers and machines that the page is current.

Fix site search too

Most CMS search tools let you boost important pages, exclude legal boilerplate, and add synonyms. A search for “ADA” should find your accessibility page, not your privacy policy.

A hypothetical: the policy post from three years ago

Imagine an institution that published a helpful post explaining a regulation when it was new. The post earned links and ranks well. The regulation’s dates later changed, and the institution published a new page with the current facts. Site search and some assistants still surface the old post first, so readers get the outdated dates from the organization they trust to know better.

The fix takes an afternoon: a dated update note at the top of the old post, corrected facts, and a link to the current page.

An audit worksheet

For each post that answers one of your key questions, record:

  • URL and publish date.
  • The question it answers.
  • Whether its facts are still correct.
  • Whether it describes your work the way you describe it today.
  • Traffic and inbound links, from analytics and search tools.
  • Which current page should own the answer.
  • Decision: update, redirect, or retire, with an owner and a date.

Decision criteria

  1. Wrong facts and real traffic: update now, with a visible dated note.
  2. Correct but duplicated by a better page: redirect to the better page.
  3. Wrong facts, no traffic, no replacement: retire.
  4. Right facts, off-message framing: revise the framing and link to the current offering page.

How to write the update note

Keep it short, dated, and specific. Say what changed and where the current information lives. For example: “Updated October 2026: the compliance dates in this post have changed. See our current page for the latest dates.” Put it at the top of the post, as plain text, not only in a colored box, so it reads correctly for everyone.

Prevent the next round

  • Tag posts that cover regulations, dates, or offerings so they are easy to find later.
  • Set a review date on those posts when you publish them.
  • Link new posts to the page that owns the answer instead of restating every fact.

Frequently asked questions

Will deleting old posts hurt our SEO?

Deleting posts with links and traffic can. Redirecting them to a live, relevant page usually preserves that value.

How often should we audit?

Twice a year for most sites, plus right after any regulatory change that affects what you publish.

Should we change the publish date when we update a post?

Keep the original date and add a visible “Updated” line. Changing dates without real changes erodes trust.

Do answer engines notice updates?

They recrawl on their own schedules. Clear, consistent pages give them the best chance of picking up the correction.

Who should run the audit?

Content owners with help from whoever manages analytics. The people who know the facts need to sign off on corrections.

Should we add a banner to every old post?

Only where facts changed. A blanket “this may be outdated” banner on everything erodes trust in the posts that are still right.

What if an old post has comments or social shares?

Update it in place rather than replacing it. The note and corrections keep the post useful without breaking links.

Next step

If you want help auditing what your site says about you, tell us what you are working on.

Let’s chat about your project.

Whether you have a fully-formed RFP or just an idea on a napkin, we’d love to hear about it. Our team is ready to listen and explore possibilities with you.

You’ll be talking to actual strategists, not a sales bot

"*" indicates required fields

This field is for validation purposes and should be left unchanged.