How to Fix a Content Pruning Backlog of Zero-Impression Posts
A content pruning backlog is a set of blog posts or articles that earned no Google search impressions at all in the last 12 months. In this guide you will list every article, match it against 12 months of Search Console data, decide whether to update, merge or remove each zero-impression post, and apply the right redirects and status codes.

Why it matters
An article with zero impressions in a year is not ranking for any query, not even on page 10. A large pool of these posts spreads crawl budget and internal links across pages Google has effectively ignored, and it can weigh on how Google's helpful content signals judge the site as a whole. AI answer engines that cite web pages draw from the same index, so these posts are not earning citations there either.
Pruning or consolidating them concentrates links and topical relevance on the pages that do perform.
What you need
Step-by-step fix
Export 12 months of page data from Search Console
Open Search Console and go to Performance > Search results. Set Date > Last 12 months, open the Pages tab, then click Export > Google Sheets. The UI export stops at 1,000 rows.
If your site has more pages than that, use the Search Console API (dimension page) or the Looker Studio Search Console connector to get the full list. Pages with zero impressions never appear in this export, so you will find them by checking which articles are missing from it.
Match your article list against the export
Put every article URL in column A of a sheet. xml, a CMS export or a crawl filtered to /blog/. Paste the Search Console export into a second tab called GSC.
Normalise both lists to the same format before you look them up: same protocol, same host, no query strings, and trailing slashes either removed from both or kept on both. Then look up the impressions for each article. Rows that return 0 are your pruning backlog.
=IFERROR(VLOOKUP(REGEXREPLACE(LOWER(A2),"/?(\?.*)?$",""),ARRAYFORMULA({REGEXREPLACE(LOWER(GSC!A2:A),"/?(\?.*)?$",""),GSC!C2:C}),2,FALSE),0)Rule out indexing problems first
Zero impressions often means a post is not indexed at all, not that the content is weak. Paste a sample of the zero-impression URLs into the URL Inspection bar. Also check Indexing > Pages under "Why pages aren't indexed".
If you see any of the following, fix that cause before you judge the content:
- Excluded by 'noindex' tag
- Alternate page with proper canonical tag
- Crawled - currently not indexed
- Discovered - currently not indexed
Triage each post: update, merge, remove or keep
Add a Decision column and pull extra data for each zero-impression post: backlinks (from Ahrefs, Semrush or Search Console Links), sessions from other channels in GA4, and conversions. Then assign one action:
- Update: the topic has search demand and you are the right site to cover it.
- Merge: another article covers the same intent better.
- Remove (410): the post is outdated, thin or off-topic, and has no links or traffic.
- Keep: it serves email, social or customers, but it will stay flagged.
Update posts worth saving
Rewrite each post around one specific query that people actually search. Check that the query exists in Google autocomplete or a keyword tool. Make these changes:
- Rewrite the title tag and H1.
- Add current facts, examples and dates.
- Remove padding.
- Add 2-3 internal links from related posts that already get impressions.
Keep the same URL. Change the visible updated date and dateModified only when the content has materially changed.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"BlogPosting","headline":"How to Choose a Standing Desk in 2026","datePublished":"2021-03-10","dateModified":"2026-02-14","author":{"@type":"Organization","name":"Example Co"}}</script>Merge overlapping posts with 301 redirects
Copy any unique, useful paragraphs from the weak post into the stronger target article. Unpublish the weak post and add a permanent 301 redirect from its URL to the target. Update internal links so they point straight to the target instead of going through the redirect.
Remove the old URL from your XML sitemap.
# Nginx (inside the server block for example.com)
location = /blog/standing-desk-tips-2019 { return 301 https://www.example.com/blog/choose-standing-desk; }
# Apache (.htaccess)
Redirect 301 /blog/standing-desk-tips-2019 https://www.example.com/blog/choose-standing-deskRemove dead-weight posts with a 410
For posts with no links, no traffic and no merge target, delete them and return 410 Gone. Google drops 410 URLs slightly faster than 404s. Then clean up behind them:
- Remove internal links to the deleted posts.
- Remove them from the sitemap.
- Remove them from category and tag archive pages.
# Nginx
location = /blog/company-picnic-2018 { return 410; }
# Apache (.htaccess)
Redirect gone /blog/company-picnic-2018Re-check impressions and re-run the audit
Wait 4-8 weeks for Google to recrawl the changed URLs. Then re-export Performance > Pages for the last 3 months and confirm the updated posts now show impressions. Check Indexing > Pages to confirm redirected URLs appear under Page with redirect and 410 URLs under Not found (404).
Finally, re-run the site audit. Its count of zero-impression articles should be lower.
curl -sI https://www.example.com/blog/standing-desk-tips-2019 | head -n 3
Platform-specific notes
WordPress
Use the free Redirection plugin (Tools > Redirection) or Rank Math > Redirections to add 301s and 410s. Yoast's redirect manager requires Yoast SEO Premium. Moving a post to Trash returns a 404, not a 410, unless you add a 410 rule. Yoast and Rank Math remove trashed posts from the sitemap automatically.
Shopify
Blog posts live at /blogs/{blog}/{handle}. Add 301s under Online Store > Navigation > URL Redirects, or create them in bulk with a CSV import. Shopify cannot return a 410, so deleted posts return 404, which is acceptable. Delete or merge posts from Online Store > Blog posts.
Webflow
Add 301 redirects in Site settings > Publishing > 301 redirects, then republish the site. Delete or archive the CMS item from the Blog Posts collection. Archived items return 404 and drop out of the auto-generated sitemap.
Next.js
Add entries to redirects() in next.config.js. Setting permanent: true sends a 308, which Google treats the same as a 301. To return a 410, use middleware that returns new Response(null, { status: 410 }) for the retired paths.
Cloudflare
Use Rules > Redirect Rules for single URLs, or Bulk Redirects (Lists) for hundreds of merged posts with status 301. For 410s, use a Snippet or a Worker that returns status 410 on the retired paths.
Check that it worked
✅ How to verify
- In Search Console, Performance > Search results > Pages (last 3 months): every updated article shows at least some impressions.
- URL Inspection on a merged URL reports 'Page with redirect' to the target, and curl -I shows HTTP 301 with the correct Location header.
- curl -I on a removed URL returns HTTP 410 (or 404), and the URL no longer appears in your XML sitemap.
- Re-run the audit and confirm the number of articles with no Google impressions in 12 months has dropped.
⚠️ Common mistakes
- Deleting posts that are actually blocked by noindex, a wrong canonical or a robots.txt rule, which throws away content that never had a chance to rank.
- Redirecting every pruned post to the blog homepage instead of a topically matching article, which Google treats as a soft 404.
- Comparing URLs without normalising trailing slashes, http/https or www, so posts that do get impressions are wrongly marked as zero.
- Leaving internal links, sitemap entries and tag pages pointing at redirected or deleted URLs.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Does deleting old blog posts improve SEO?
It can help when the posts are thin, outdated or duplicate, because it concentrates internal links and crawling on stronger pages. Deleting posts that have backlinks or real traffic can hurt. Merge those with a 301 instead.
Should I use a 404 or a 410 for deleted posts?
Both remove the page from Google's index. A 410 signals that the removal is intentional and is often processed slightly faster. A 404 is fine on platforms like Shopify that cannot send a 410.
How do I find pages with zero impressions in Google Search Console?
Search Console only lists pages that had impressions, so you cannot filter for zero directly. Export Performance > Pages for the last 12 months, then compare it against a full list of your article URLs from your sitemap or a crawl. Any article missing from the export had zero impressions.
Is noindexing low-quality posts as good as deleting them?
Noindex removes a post from search results. However, the page is still crawled and still linked from your blog, so it keeps using crawl budget and stays in your article count. If a post has no value for users, merge or remove it instead.
How to Find and Remove Scraped Copies of Your Content
How to Replace Stock Photos With Original Site Images
How to Add Downloadable Resources That Earn Links and Leads
How to Fix Low Long-Tail Question Coverage on Your Site
How to Add Expert Review to YMYL Health and Finance Pages
How to Write Answer-First Introductions for Your Articles