You have years of blog posts. Some are good. Some are embarrassing. Most you have not opened since the day you published them.
So the question comes up. Do old blog posts help AI search visibility, or are they dead weight?
Our answer: they help when they meet three conditions. When they do not, they are clutter, or worse.
Do years-old posts help or just clutter the site?
They help when they still do a job. A post that explains how to prep a deck for staining can still be the clearest answer to that question, years after you wrote it.
Age is not the problem. Three things decide it:
- The post is reachable at its original address.
- It still says something true.
- It is clearly labeled as an article.
Miss one and the post stops earning its keep. Meet all three and you are sitting on an asset that a new post would take time to match.
What does an AI answer need from a post?
A stable address and a clear subject. That is the short list.
The address matters because everything that knows about your post knows it by that address. Search indexes. Links from other sites. Saved citations. Change it carelessly and all of that points at nothing.
The subject matters because an assistant is trying to answer a specific question. "Our Thoughts on Summer" gives it nothing. "How Long Should Exterior Paint Last?" gives it a question and an answer.
If a post has both, it is a candidate to be cited. If it lacks either, it gets passed over, however well it was written.
Why does a post that redirects to your homepage vanish?
Because your homepage is not an answer to anything.
When a site is rebuilt, old addresses often get lazily redirected to the homepage. It feels safe. Nobody sees an error page. But the specific post is gone, and something generic has taken its place.
The question it answered is no longer answered anywhere on your site.
This is the quietest way to lose years of work. Nothing looks broken. Your homepage loads fine. The posts are simply gone from the places that used to send you visitors.
How does missing article markup leave a good post unlabeled?
Article markup is a small block of structured data in the page. In plain terms it says: this is an article, here is its headline, here is when it was published.
Without it, a search system has to guess what the page is. Often it guesses fine. Sometimes it does not.
Platform changes strip this out all the time. A theme is swapped, a plugin is removed, and the markup disappears from every post at once. The words are still on the page. The label is gone.
Restoring it costs far less than writing new content. It is also invisible to visitors, which is exactly why nobody notices it is missing.
What is the keep, update or retire test?
Run each old post through three questions, in order.
- Is it reachable, and does it answer something customers still ask? If not, skip to retire.
- Is it still true? Prices, rules, products, phone numbers, photos of work you no longer do. If anything is stale, update it.
- Is it distinct? If another post of yours says nearly the same thing, one of them goes.
Then act:
- Keep. Reachable, true, distinct. Leave it alone. Do not touch the address.
- Update. Good topic, stale details. Fix the details, keep the address, and change the visible date honestly.
- Retire. Thin, duplicated, or about something you no longer do. Remove it properly.
Do not decide by age. Decide by the answers.
What did A New Leaf Painting keep when its blog moved platforms?
Nearly everything, and that was the whole point.
A New Leaf Painting Contractors has painted homes and businesses across Jacksonville and Northeast Florida since 2010. Its site grew to hundreds of blog posts and paint guides. Then a move to a new platform went badly. Hundreds of old addresses were redirected to the homepage, pages that search engines still listed were gone, and the blog had lost the markup that tells Google what a post is.
The rebuild did three things for the blog:
- Every post and guide went back to its original address with its own words carried over.
- Every address the site had published was traced and made to answer in a single hop.
- Article markup was restored on every post.
The old writing survived because the addresses and the words survived. The full story is in the A New Leaf Painting case study.
When should a thin or near-identical post go?
Sooner than you think.
Some old posts should never have been published. Five paragraphs that repeat another post with the town name swapped. A page with two sentences and a stock photo. They answer nothing, and they make your better pages look like part of a pile.
Retiring is not the same as redirecting. In the A New Leaf Painting rebuild, the thin, near-identical pages were not sent to the homepage. They got a clean "gone." That tells search systems the page was removed on purpose.
Redirect a retired post only when a genuinely related page can take its place. Otherwise, let it go cleanly.
Which five checks should you run on your oldest posts this month?
Pick your twenty oldest posts and work through this list.
- Does each address still load? Open it. Do not assume.
- Does any old address land on your homepage? Point it at the matching post, or give it a clean "gone."
- Is article markup present? Check the page source or use a testing tool and look for article data.
- Is anything stale? Prices, rules, phone numbers, names.
- Does another post say the same thing? Merge them or retire the weaker one.
Fix redirects first. A lost address costs you the most and takes the least time to repair.
If you would like a second set of eyes on the whole site, our SEO and analytics work starts with exactly this kind of audit.
Where to start today
Open your five oldest posts and click each address. Write down every one that lands somewhere unexpected. That list is your first week of work.