Should a Small Business Delete Old Blog Posts? What Google Says, and a 4-Way Decision Table (2026)
Should a small business delete old blog posts for SEO?
Not because they are old. Google's Search Liaison said in August 2023 that deleting content because you believe Google doesn't like "old" content is "not a thing", and that older content can still be helpful. Delete a post only when it is wrong, irrelevant to the business now, or a weaker duplicate of another page, and even then update or redirect it first if it still earns visits or links. This guide was checked on 2026-11-11 and ends with a 4-way decision table.
PilotaSEO is a done-for-you SEO blog service that writes SEO posts for your site and publishes them automatically. A growing blog raises this question within a year, so it helps to have a rule before the first clean-up.
What did Google actually say about deleting old content?
Google's public position is that age alone is not a reason to delete. As Search Engine Roundtable reported on 9 August 2023, Danny Sullivan, Google's Search Liaison, wrote: "Are you deleting content from your site because you somehow believe Google doesn't like 'old' content? That's not a thing! Our guidance doesn't encourage this." The posts came after CNET was reported to be removing thousands of old articles.
In the same thread Google's John Mueller added the balancing point: "Delete what you don't want to keep - regular maintenance and cleaning up is always good. Just don't assume that deleting something only because it's old will improve your site's SEO magically." For a small business blog with 30 or 300 posts, that is the whole policy in two sentences: clean up for readers, not for an imagined age penalty.
What happens in Google when you delete a post?
A deleted post that returns a 404 or 410 drops out of Google's index over time, and that is not a penalty for the rest of your site. Google's documentation on HTTP status codes says it doesn't index URLs that return a 4xx code, removes already indexed ones, and treats all 4xx errors except 429 the same way.
What you lose is whatever that URL had: the searches it appeared for, the visits it got and any links other sites gave it. That is why the order matters. Look at the numbers first, then decide.
Update, merge, redirect or delete: how do you decide?
Every old post fits one of four outcomes, and two questions sort them: is the topic still useful to your customers, and does the URL still earn anything? Check the second one in Search Console's Pages report (clicks and impressions over the last 12 months) and in any backlink tool you already use.
| The post is... | Earns visits or links? | Do this | Status code |
|---|---|---|---|
| Useful but out of date | Yes or no | Update it at the same URL | 200 |
| A near-duplicate of a better post | Some | Merge the useful parts, then redirect | 301 to the kept post |
| About something you no longer offer | Yes | Redirect to the closest equivalent page | 301 |
| About something you no longer offer | No | Delete it | 404 or 410 |
Worked example. A bakery has 60 posts. "Our 2021 Christmas opening hours" gets no visits and has no equivalent page: delete it and let it return 404. "How to store sourdough" still gets 40 clicks a month but cites an old fridge guideline: update it in place. Two posts on "gluten-free bread tips" compete for the same searches: keep the stronger one, fold in the other's best section, and 301 the weaker URL to it.
The update path is covered in refresh or write new, and the duplicate case overlaps with when a small business blog needs a canonical tag.
Where should a redirect point?
Only to a page that genuinely replaces the old one. A permanent redirect tells Google to show the target instead of the old URL, according to its guide to redirects, so the target has to answer the same need. Sending every deleted post to the homepage looks like a missing page dressed up as a redirect; if nothing equivalent exists, an honest 404 or 410 is the better answer.
After any redirect or deletion, fix your own links. Search your blog for the old URL and point each link at the kept page, so readers and Google don't hit a dead end. Our guide to internal linking from blog posts to service pages shows the pattern.
Does deleting thin posts help the rest of the site?
Not directly. In the same 2023 thread Sullivan said removing a page "might mean if you have a massive site that we're better able to crawl other content", but that Google doesn't decide "the whole site is so much better" because one page went. A small business blog is nowhere near the size where crawling is the bottleneck.
The real gain is for readers and for you: fewer outdated answers, fewer posts competing for one search, and a blog that is easier to maintain. If a new post isn't being indexed, deleting old ones rarely fixes it; check the reasons in why a new blog post isn't indexed first.
A yearly clean-up routine in 4 steps
- Export the list. In Search Console, export pages with their clicks and impressions for the last 12 months.
- Mark each post as update, merge, redirect or delete using the table above. Leave anything you are unsure about alone.
- Make the change and the status code match: 200 for updates, 301 for merges and redirects, 404 or 410 for deletions.
- Fix internal links to every changed URL, and change the visible date only on posts you really updated.
When you update a post, the date rules in should blog posts show dates apply: change the "last updated" date only for a real change.
Does a done-for-you blog service delete old posts?
Ask before you sign. A good provider updates useful posts in place, never deletes or redirects without your approval, and tells you which URLs it changed. PilotaSEO's plans are Autopilot at €322 a year and Growth at €8,250 a year; the PilotaSEO plans list what each includes.
FAQ
Does Google penalize old blog posts?
No. Google's Search Liaison said in 2023 that the idea Google dislikes old content is "not a thing" and that older content can still be helpful. Outdated or wrong information is the problem, not the publish date.
Is a 404 bad for SEO?
A 404 on a page you deliberately removed is normal. Google drops 4xx URLs from its index over time, and the rest of the site isn't penalized for it.
Should I use 404 or 410 for a deleted blog post?
Google's documentation says it treats all 4xx codes except 429 the same way, so either works. Use 410 if your platform supports it and you want to state the removal was deliberate.
Should I redirect deleted posts to my homepage?
No. Redirect only to a page that replaces the old one. If there is no real equivalent, let the URL return 404 or 410.
Sources
- Search Engine Roundtable: Google says don't delete older content if it's helpful (Aug 2023) (checked 2026-11-11)
- Google Search Central: How HTTP status codes affect Google's crawlers (checked 2026-11-11)
- Google Search Central: Redirects and Google Search (checked 2026-11-11)
- Google Search Central: Creating helpful, reliable, people-first content (checked 2026-11-11)