.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiWe're pruning a page. Here's the internal memo version of why, written out so the logic is on record instead of living in someone's head.
The page in question: /resources/blog-insights/top-10-features-ecommerce-analytics-platform-m. Three months of data, under 10 impressions, zero clicks. That's not a slow page. That's a dead one.
Under 10 impressions and zero clicks over 90 days isn't a traffic problem you fix with better internal linking or a fresh meta description. It's a signal the page shouldn't exist in its current form.
Here's the part people miss: a thin, zero-traffic page doesn't just sit there neutrally, waiting for its moment. It actively drags down sitewide quality signals. Google's crawling it, finding a page that doesn't earn a visit even after ranking impressions, and quietly folding that into how it reads the rest of your blog. Low-value pages aren't free to keep around. They cost you crawl budget and, over enough of them, they cost you topical authority on the pages that do deserve to rank.
So this isn't a rewrite project. We're not going to punch up the copy on "top 10 features of an ecommerce analytics platform" and hope round two performs better. The content's premise was always thin: a listicle format bolted onto a topic that already has a real home. The decision here is consolidation and redirect, full stop. If a redirect target doesn't make sense (more on that below), the fallback is noindex, not a content refresh.
Before touching the redirect, we need to pick where this content's remaining value actually belongs.
First candidate: /products/bi-reporting. It already covers dashboarding depth: custom reports, cross-channel reporting, the stuff that made up most of the original "features" list. If the old post was mostly describing reporting capability dressed up as a listicle, this is the obvious landing spot.
Second candidate: /products/insights. This one fits better if the original page leaned on AI-driven insight features, the Wingman-style "here's what changed and why" layer, rather than raw dashboard mechanics. Worth a reread of the original ten points before deciding.
Pick one. Not both. Splitting the redirect, or worse, linking to both pillars and letting readers sort it out, splits authority instead of consolidating it. That defeats the entire point of the prune. Read the original draft, tag each of the ten points as "reporting" or "insight" in nature, see which bucket wins, and send the redirect there. If it's a near-even split, default to bi-reporting since that's the more established, higher-traffic pillar.
Don't copy-paste all ten points into the pillar page. Most of them are already said better, elsewhere, on the site.
Audit the list first. Out of ten features, you're typically left with two or three that actually say something the pillar page doesn't already cover. Those get folded in, as a sentence or two, not a new subsection.
Anything platform-specific doesn't belong on a pillar at all. If the original post name-checked Shopify order sync, Amazon settlement reconciliation, or GA4 funnel tracking as a "feature," that detail belongs on the relevant solutions page (/solutions/shopify, /solutions/amazon, /solutions/ga4), not diluted into a general product pillar. Pillars should stay platform-agnostic. Specifics go where someone's actually searching for that specific integration.
Everything else gets cut. "Real-time dashboards." "Custom reports." "Exportable data." These are filler points that every analytics listicle on the internet includes, and the pillar page already covers them in more detail with actual screenshots and specifics. Keeping them doesn't add information, it just adds word count. Cut them without mercy.
Once the pillar's picked, the technical side is simple but easy to half-do.
Set a 301 from the old URL to the chosen pillar. One hop, not two. If any other page on the site links to /resources/blog-insights/top-10-features-ecommerce-analytics-platform-m directly, update those links to point straight at the new pillar URL. Don't let a redirect chain form where an internal link hits the old URL, bounces to the pillar, and a crawler has to follow two hops to get there. Chains are the kind of thing that look fine to a human clicking through and get flagged in a crawl audit three months later.
Check the sitemap too. If the old URL is still listed there post-redirect, pull it. A sitemap entry pointing at a redirected URL tells crawlers "here's content to index" when the actual answer is "there's nothing here anymore, go to the pillar."
And pull it from the blog index listing immediately. Not after the redirect settles, not next sprint. If it's still showing up in the /resources/blog-insights feed while also 301ing elsewhere, that's a confusing signal to send both to users and to Google, and it's a five-minute fix.
Redirects aren't always the right call. If you force one where there's no real content overlap, you're sending someone who searched "top 10 features ecommerce analytics platform" to a pillar page that doesn't actually answer what they were looking for. That's a worse user experience than the thin page itself.
Noindex is the fallback, not a laid-back shortcut to the same place. Use it when the audit comes back genuinely empty: no unique points worth saving, no real topical match to bi-reporting or insights. In that case, redirecting would be misleading rather than helpful, so just remove it from indexing instead.
Even then, strip the internal links pointing to it. An orphaned, noindexed page floating around with internal links still pointing at it doesn't help anyone. It's just a dead end with extra steps.
Set a reminder to check back in 90 days. Confirm it's actually fallen out of the index (Search Console's coverage report will show it as "excluded by noindex"), and once that's confirmed, it's a candidate for full deletion rather than a page that lingers in noindex limbo forever.
Pruning isn't a one-and-done action. Check back.
At 30, 60, and 90 days post-redirect, pull Search Console and look at the pillar page's impressions. You're looking for a small, real absorption of whatever residual search volume the old page had. It won't be dramatic given the page started under 10 impressions, but the pillar should show some lift tied to the same query terms, which confirms the redirect's doing its job rather than just existing as a technical formality.
Also check for crawl errors on the old path. A redirect that's misconfigured, or that creates an unexpected loop, won't always announce itself. It just quietly shows up in the crawl stats report a few weeks later as a 404 or a loop warning. Catch it early.
Last thing: this page is a pattern, not a one-off. Any blog post sitting under 10 impressions and zero clicks over a rolling 90-day window should get flagged for the same treatment. Build this into a quarterly prune sweep instead of handling it as a one-time cleanup. If the content's genuinely useless at that threshold once, it'll happen again, and a standing process beats a one-time fire drill.
If you want a hand setting up that audit process, or want to see how we handle this kind of content and reporting cleanup at the account level, our guides and reports library has a few breakdowns worth a look. Worth a subscribe if quarterly content audits are new territory.
explore more insights
3 min read
3 min read
3 min read