Should You Delete Old Blog Posts?
You should not delete old blog posts in most cases. Google’s Search Liaison has said deleting content because it is old is “not a thing,” and most old posts still hold links, rankings, or impressions the rest of your site uses. The posts worth deleting are thin pages, duplicates, and posts competing with a better page.
Here is how I sort every post into keep, update, merge, or cut before touching a single URL.
Is Deleting Old Posts Good for SEO?
No, deleting old posts is not good for SEO by itself. Google’s Search Liaison answered the question directly: “Are you deleting content from your site because you somehow believe Google doesn’t like ‘old’ content? That’s not a thing!” Age is not a quality signal, and removing pages does not lift the rest of your site.
The warning came after CNET deleted thousands of old articles hoping the cleanup would read as freshness. Google rejected the idea in public, and its helpful content guidance explains why: it rewards pages that help people, not sites that groom their archives for the crawler.
So Google does not penalize a site for keeping old content. What it penalizes, quietly and by omission, is content that never helped anyone in the first place.
Old posts also do work you cannot see in a traffic report. They hold internal links, catch long-tail searches, and fill out the subject coverage that builds topical authority for your whole site. Delete them carelessly and the posts you kept lose support.
That support is easy to measure on a store blog. Open Search Console, filter to the post, and look at impressions, not clicks. A post with 300 impressions a month and 4 clicks is not dead. It is a page Google already shows, one title rewrite away from paying.
When Does Deleting Old Posts Make Sense?
Deleting old posts makes sense when a post has no traffic, no links, no impressions, and no job. Think tag-page fluff, five near-identical posts from 2019, or announcements for products you no longer sell. Deleting is cleanup for content that failed at everything, not maintenance for content that aged.
The delete pile is usually some mix of these:
- Thin posts under a few hundred words that answer nothing
- Near-duplicates covering the same question with different titles
- Expired content: dead products, past events, old promotions
- Auto-generated tag and archive pages dressed up as content
There is one more case, and it is the sneaky one. Two decent posts competing for the same keyword can both rank worse than either would alone. There the fix is picking a winner, not deleting both.
Whatever the case, delete only what has no traffic, no links, and no job. If a post has even one of the three, it belongs in a different pile.
I will concede the counterpoint, with the numbers attached. Google’s own crawl budget guide says the budget only matters for sites with about a million unique pages, or 10,000 pages that change daily, and that smaller sites whose pages get crawled the day they publish can skip the guide entirely. Cutting junk pages helps crawling at 50,000 URLs and does nothing at 200. A store blog does not have a crawl budget problem; it has a content quality question.
How Do You Decide Which Posts to Keep?
You decide which posts to keep by pulling three numbers for every post, impressions, backlinks, and internal links, and keeping anything that scores on at least one. The sort takes an afternoon on a 200-post blog, and most of the afternoon is the export, not the decisions.
Start in Search Console. Open the Performance report, set the date range to the full 16 months, switch to the Pages tab, and export it. The export caps at 1,000 rows, which covers nearly every store blog, and it gives you impressions and clicks per URL in one sheet. Any post that is not in the export at all had zero impressions in 16 months, and that is the first clue it has no job.
From there, add two columns by hand. Backlinks come from any link tool’s free tier, or from the Links report in Search Console, which lists the external sites pointing at each page. Internal links come from a crawl, or from searching your own blog for the post’s URL. A post with three other posts pointing at it is holding those posts up, whatever its traffic says.
My thresholds for a store blog are simple:
| Signal | Threshold | Call |
|---|---|---|
| Impressions | 50 or more a month | Keep and update |
| Backlinks | Any link from a real site | Keep, or merge and redirect |
| Internal links | Two or more posts point at it | Keep, or redirect carefully |
| None of the above | Zero on all three | Delete pile, pending one last read |
That last read catches the post that is thin in data and still useful. A how-to for a product you still sell, with zero impressions because the title is bad, is an update, not a delete. The data finds the candidates; a person makes the call.
What Should You Do Instead of Deleting?
Instead of deleting, update, merge, or leave the post alone, in that order. A post with impressions gets refreshed, overlapping posts get merged into the strongest one, and a post quietly doing its job gets left in peace. Deleting is what remains when none of those apply.
| Situation | Action | Why |
|---|---|---|
| Has impressions or clicks | Update | The hardest part, being seen, is done |
| Several posts, one topic | Merge | One strong page beats three weak ones |
| No traffic, has backlinks | Merge or redirect | The links keep their value |
| No traffic, no links, no job | Delete | Nothing to lose |
The update row is where most of the money hides. A page Google already shows is far closer to paying than a new one, which is the whole argument in updating old content vs writing new. Deleting a post with impressions throws away rankings someone spent months earning.
Merging, the next option down, is underused because it feels like admitting the extra posts were a mistake. They were, and that is fine. Fold the best paragraphs into the winner, then redirect the losers to it. Three posts on “how to wash a heated vest,” “can you wash a heated vest,” and “heated vest care” become one page that answers all three, and that one page usually outranks the best of the three within a month.
The leave-alone row surprises people. A post with 20 clicks a month and nothing wrong with it is not a problem to solve. It is one of the dozens of small pages that add up to a blog that ranks, and the hour you would spend touching it is better spent on the post at position 11.
How Do You Retire a Blog Post the Right Way?
The right way to retire a blog post is to check its data, then redirect it to the closest related page. Google’s redirect documentation says a permanent redirect tells Search to show the new target in results, so the old URL’s standing passes to the page that replaced it.
The retirement checklist, in order:
- Pull the post’s clicks, impressions, and position in Search Console for the last 16 months.
- Check its backlinks and which of your own pages link to it.
- If anything shows life, update or merge instead.
- If not, 301 it to the closest related page and fix the internal links pointing at it.
- No related page at all? Let it 404 and move on.
That last step surprises people, but Google’s John Mueller has said 404s do not hurt the rest of your site. Google’s documentation on HTTP status codes treats 404 and 410 the same way: the URL drops out of the index and gets crawled less and less. A dead URL with nothing to pass on is allowed to just die.
Also, do the whole cleanup in one batch rather than deleting a post here and there for months. One batch means one redirect map, one internal link pass, and one before-and-after you can measure. My content audit template is the sheet I use for that batch.
The Search Console check matters most, because impressions without clicks are hidden inventory. Those pages are one position jump from paying, and they are the first thing I look for when a store asks me to clean up its blog. Every removed URL gets a redirect or a reason.
How Do You Delete a Blog Post on Shopify Without Losing Rankings?
You delete a blog post on Shopify without losing rankings by deleting the post first and adding the redirect second. Shopify’s URL redirect help says a redirect only works from a broken URL, so if the old post still loads, the redirect is ignored.
Delete or hide the post, then go to Content, Menus, View URL redirects, and point the old path at the replacement.
The order trips up almost everyone the first time. They create the redirect while the post is live, see it do nothing, and assume redirects are broken. The redirect was fine; the post was in the way. Hiding the post instead of deleting it works too, since a hidden post stops loading on the storefront, and it leaves you a copy to pull paragraphs from during the merge.
Beyond the order, two Shopify details matter. The old blog URL keeps its /blogs/news/ path, so the redirect has to match that exact path, not the title. And a standard store can hold 100,000 redirects, so a cleanup of 40 posts is nowhere near a limit; stores that have migrated twice and carry thousands of legacy paths are the only ones that need to count.
One more Shopify habit worth keeping is to fix the internal links before you delete. Shopify will not update the links in your other posts for you, so a deleted post leaves every link that pointed at it running through a redirect. A five-minute search of your blog for the old URL cleans that up, and it is part of the monthly maintenance in my SEO services for Shopify stores.
Should You Redirect a Deleted Post to the Homepage?
No, you should not redirect a deleted post to the homepage, since the homepage is not a replacement for the post and Google reads a redirect as “this content moved here.” Point the old URL at the closest related post or collection. If nothing related exists, a 404 is the honest answer, and it does not hurt the rest of your site.
What If a Deleted Post Had Backlinks?
A deleted post that had backlinks should be redirected, never left as a 404, since every link pointing at a dead URL stops passing anything the day the page goes. Point it at the merged post or the closest collection and the links keep working. On Shopify, that means deleting the post and adding the redirect in the same sitting, so the links are never pointing at a 404 for longer than a few minutes.
Does Deleting Old Posts Improve Crawl Budget?
Deleting old posts improves crawl budget only on sites large enough to have one, which Google puts at about a million pages, or 10,000 pages changing daily. A store blog with 150 posts is crawled in full whenever Google wants. Deleting 30 of them changes nothing about how often the other 120 get seen.
Want a Cut, Keep, or Merge Call on Every Post?
Deleting old posts is not an SEO strategy, it is housekeeping. Google says age alone is no reason to remove anything, the posts worth cutting are the ones doing nothing at all, and everything else earns more from an update, a merge, or being left alone.
If your blog has years of posts and you are not sure which pile each one is in, book a call and I will pull your Search Console, sort every post into keep, update, merge, or cut, and hand you the redirect map before you delete a single URL.
Sources:
- Search Engine Land: Google warns against content pruning as CNET deletes thousands of pages
- Google Search Central: Creating helpful, reliable, people-first content
- Google Search Central: Optimize your crawl budget
- Google Search Central: Redirects and Google Search
- Search Engine Roundtable: Google says 404 pages do not hurt your website
- Google Search Central: How HTTP status codes and network errors affect Google Search
- Shopify Help Center: Creating and managing URL redirects
