Prune to Grow: Deleting Weak Posts Can Lift the Whole Site
Learn how deleting thin, duplicate, or dated posts can improve your site's rankings. Includes an audit framework and real case studies.
Learn how deleting thin, duplicate, or dated posts can improve your site's rankings. Includes an audit framework and real case studies.
More pages do not automatically mean better rankings, and that assumption has cost a lot of Shopify stores traffic they should have kept. That is the idea behind prune to grow: deleting weak posts can lift the whole site, and it is one of the most underused levers in ecommerce SEO. If your blog has been running for a year or more, there is a good chance a meaningful slice of your posts are quietly dragging everything else down, and the fix is not always writing something new. Sometimes it is removing what should never have stayed.
This is the logic behind content pruning, and the results it produces are hard to argue with. This article shows which posts qualify, how to find them, and what to do with each one.
Thin, outdated, or redundant pages can make a site less useful, so review them alongside your strongest posts.
Think of it like a classroom graded on average marks. Your ten best students can only carry the average so far before twenty underperformers drag it below where it should be. Your blog works the same way.
Three specific mechanisms make this concrete:
Content pruning is not about deleting everything old. Some older posts are still driving traffic and earning backlinks. Those stay. The goal is identifying pages that provide no genuine value and no realistic path to providing it. Here are the five types most common in ecommerce blogs.
Thin content is any page that provides little or no value to the reader: too short, too generic, or too shallow to satisfy the search intent it was supposed to address. A 250-word post broadly covering a topic that needs 1,000 words of specific guidance qualifies. So does a post that simply restates a product description without adding context, comparison, or insight.
Word count alone is not the threshold. A 400-word post that answers one precise question clearly can outperform a 1,500-word post that says nothing specific. The test is whether a reader who lands on it actually gets what they came for.
A post about a shipping policy that changed two years ago, a roundup of apps that no longer exist, or a how-to based on a platform interface that has since been redesigned will send visitors away frustrated. High bounce rates and low engagement time in Google Analytics are the telltale signs. Outdated information also erodes trust in the pages around it.
When two posts on your blog target the same search term, they compete against each other. Google has to choose which one to rank, and often ranks neither particularly well. Check Google Search Console's Performance report, filter by a keyword you care about, and look for multiple URLs appearing in the results. That is cannibalization in action.
One industry study found that 29% of websites face duplicate-content issues. For ecommerce blogs, this often appears as near-identical posts covering seasonal topics ("best gifts for dad" repeated across three Junes), or product category posts that recycle the same copy with minor variations. Even when Google does not issue a direct penalty, duplicate pages split ranking signals and waste crawl budget.
A post that no other page on your site links to is invisible to crawlers unless they find it via a sitemap. These orphaned pages rarely accumulate authority and rarely rank. If a post has not earned a single internal link from the rest of your blog, that signals a problem: either it needs to be woven into your site's structure, or it probably should not exist at all. See our guide on pillar pages and hub-and-spoke content structures for how to build a site architecture where no post gets left behind.
You do not need expensive tools to start. Google Search Console and Google Analytics cover most of what you need. Here is a simple process.
From there, it is a matter of reading the data and making a call on each flagged URL. The decision framework below makes that easier.
Most underperforming pages come down to one of four choices. Here is how to decide which action to take.
Keep any page that still earns meaningful organic traffic, has backlinks that pass authority to your domain, or covers a topic central to your store's subject matter, even if its current performance is modest. Some posts are slow builders. A post six months old with low traffic but strong engagement signals (long time on page, low bounce rate) may simply need more time.
Choose refresh for posts that rank on pages 2–3, have some backlinks, and cover topics your audience still searches for, but contain outdated information or thin sections that could be expanded. Refreshing old content can be worthwhile. If the post was written with AI, our article on the human editing pass that keeps AI content ranking covers what to check before you republish.
Consolidation is the right move when you have two or more posts covering the same topic with overlapping content. Pick the stronger URL, merge the best material from the others into it, and 301-redirect the weaker URLs to the surviving page. This combines whatever link equity existed across the duplicates into a single, more authoritative resource. One strong page beats three mediocre ones every time.
Delete posts that have no traffic, no backlinks, no engagement, and no realistic potential. This includes topics too narrow to ever attract search volume, or posts so outdated their subject matter no longer exists. When a genuinely relevant replacement exists, 301-redirect the deleted URL to it. Leaving a broken URL wastes crawl budget and removes whatever small amount of link equity the page may have accumulated.
One practical signal: if a post has fewer than 50 clicks in the past 12 months and ranks below position 40, that is a strong indicator it belongs on the cut list rather than a refresh queue.
The payoff from content pruning is well-documented. These are real outcomes from published cases:
These cases point the same way: removing low-value pages can free up crawl budget, concentrate authority on the pages that remain, and send a cleaner quality signal to Google. Results vary, and some of these gains may have other causes.
Content pruning is not a one-time event. Blogs accumulate underperforming pages the same way closets accumulate clothes that no longer fit: gradually, invisibly, until the problem is hard to ignore.
A practical schedule:
The right time to start is immediately after your next Google Search Console export. Pull your lowest-traffic pages and run them through the five-column spreadsheet. You will almost certainly find posts that have been sitting quietly, costing your better content its rightful rankings.
If you are also thinking about where AI visibility fits into this, note that AI search tools like ChatGPT and Perplexity are increasingly selective about which pages they surface. Pruned, high-quality content is far more likely to earn citations than a domain cluttered with thin posts. For more on how AI systems choose what to cite, see our piece on how to get cited by AI search engines.
Start small. Export your URLs this week, mark the weakest twenty, and decide keep, refresh, consolidate or delete for each one. Then check Search Console again in two to three months to see what moved.
Not if you do it strategically. Removing low-quality pages, those with no traffic, no backlinks, and no clear topic value, with a proper 301 redirect to a related page is a quality improvement Google responds to positively. The risk comes from deleting pages that still earn traffic or backlinks without redirecting them.
A practical threshold: any post with fewer than 50 organic clicks in the past 12 months (from Google Search Console) that ranks below position 40, has no meaningful backlinks, and covers a topic that doesn't align with your store's core subject matter is a strong candidate. Cross-check word count and engagement time before you decide.
Deleting removes a page; redirect its URL to a closely related page when one exists, and let it return a 404 when none does. Consolidating merges two or more thin posts on the same topic into one stronger resource, keeping the best URL and redirecting the others. Refreshing updates an existing page with new information, better structure, or additional depth and works best for posts that still carry traffic or backlinks that would be lost if the URL were removed.
Smaller blogs (fewer than 100 posts) can audit once or twice a year. If you publish weekly or use AI-assisted publishing at scale, audit in batches every 1–3 months so underperformers don't accumulate. A quarterly review takes a couple of hours in Google Search Console and a simple spreadsheet.
Cannibalization is a separate but related issue. When two posts target the same keyword, they split ranking signals rather than combining them, so both end up weaker. The fix is consolidation: merge the weaker post into the stronger one, redirect the old URL, and let one page own the keyword cleanly.
The playbook
The playbook first, then a few short emails to help you publish your first great article, then just the occasional update. No spam, and you can unsubscribe anytime.