Content Pruning Plan: Consolidating /polleo-adria Into the Case Studies Pillar
by Trivas.ai
|
7 min read
Oct 10, 2026
Every SaaS site accumulates pages nobody asked for. Customer logos get a landing page because sales wanted a link to send a prospect, and then two years later that page is still sitting in the index doing nothing. That's exactly what we found when we pulled Search Console data on /polleo-adria: under 10 impressions and zero clicks over a full 3-month window. Not low traffic. No traffic. This post walks through why that page is getting pruned, what we checked before deciding, and how the same process applies to the rest of our customer page set.
Why This Page Is Flagged for Pruning
Under 10 impressions and zero clicks across 90 days isn't a slow page, it's a page Google barely bothers to show anyone. Nobody is searching "Polleo Adria Trivas" or anything close to it in meaningful volume, so there's no search demand to serve here in the first place.
Here's the part people miss: a thin, orphaned customer page doesn't just sit there harmlessly. It actively works against the rest of the site. Every customer page built off the same boilerplate template, with a logo swapped in and a paragraph of near-identical copy, adds to your site's thin content ratio. Crawlers spend budget on pages like this instead of pages that actually rank. And when a search engine sees a pattern of near-duplicate, low-value pages across a domain, it doesn't treat each one in isolation. It starts adjusting how it crawls and indexes the whole site.
So this isn't a "leave it alone, it's not hurting anything" situation. A pile of pages that look like /polleo-adria is a sitewide quality signal problem, not a one-off.
What's Actually on the Page Today
The page itself is what you'd expect from a template-driven customer snapshot: a short use-case blurb describing Polleo Adria's setup on Trivas, a logo, and the standard structural elements shared across every other customer page on the site.
There's no specific metric on the page. No quote. No workflow detail that couldn't be swapped onto any other customer's page with a find-and-replace. That's the real problem, not the traffic number by itself. Low traffic on a genuinely unique, substantive page is a search visibility problem you fix with better targeting. Low traffic on a page with nothing unique in it is a content problem you fix by removing the page.
Right now, /polleo-adria doesn't have enough standalone substance to justify its own URL in the index. It reads like a placeholder that happened to go live.
Decision Criteria: Merge + 301 vs. Noindex
Not every thin page gets the same treatment, and it shouldn't. We use a simple test before touching anything:
Merge + 301 when there's a genuine, specific detail worth keeping: a real metric (reporting time cut, revenue lift, hours saved), a specific integration mentioned, or a workflow detail that's actually unique to that customer's setup. That detail deserves to live inside a stronger page, with a redirect carrying over whatever link equity the old URL accumulated.
Noindex, no redirect when the page is pure template filler. Logo, generic blurb, done. There's nothing to preserve, so there's nothing to merge. Redirecting a page with zero unique content just to keep a URL "alive" doesn't help anyone. It just adds another entry to a redirect map for no reason.
Based on what's on the page now, /polleo-adria falls into the second bucket. There's no metric, no quote, no workflow specific enough to stand out. Our recommendation is noindex over a forced merge, unless whoever manages the Polleo Adria account confirms there's a real customer detail that never made it onto the page. If that detail exists, this moves to a merge. If it doesn't, noindex is the right call and there's no reason to manufacture content just to justify a redirect.
Recommended Consolidation Target
If the account team comes back with something real, a specific metric, a specific integration, a specific before/after, that detail gets folded into the case studies hub as a short entry rather than propped up as its own thin page. One strong, consolidated page beats a dozen pages that each say almost nothing.
In that scenario, /polleo-adria gets a 301 redirect pointed at the case studies page, so any residual link equity and crawl signal routes somewhere that actually has traffic and matches real search intent. That's the whole point of a 301 here, not preserving the URL for its own sake, but making sure nothing of value gets dropped on the floor.
If no usable detail turns up, skip the redirect entirely. Apply noindex, follow instead. That keeps the URL technically crawlable, so any internal link equity still passes through the links on the page, but it stops competing for index space against pages that are actually built to rank. A redirect implies "this content lives somewhere else now." Noindex says "this content isn't worth indexing, period." Those are different situations, and /polleo-adria is looking like the second one.
Implementation Checklist
Before anything gets deleted or redirected, here's the sequence:
Confirm with the account or customer success team whether Polleo Adria has a quotable metric, a specific workflow, or any detail worth retaining. Don't assume the page is final just because it's thin, check first.
Set up the redirect rule (if a merge target applies) at the CMS or CDN layer, and verify it resolves in a single hop. No chains, no redirect-to-a-redirect.
Update every internal link currently pointing to /polleo-adria, including the sitemap, nav references, and any "related customers" module that might be pulling it in automatically.
Pull the URL from the XML sitemap once the redirect or noindex tag is live. Leaving it in the sitemap after a noindex just sends mixed signals to crawlers.
Check back in Search Console in 4 to 6 weeks. You're looking for the page to drop out of the index, and for whatever minimal impressions it had to shift onto the consolidated page (or simply not reappear anywhere, which is also a fine outcome for a page with zero search demand).
None of these steps are optional. Skipping the internal link cleanup is the most common miss: the redirect works fine, but half the site's nav or footer still links straight to the old URL, which just recreates the crawl waste you were trying to eliminate.
What This Means for the Rest of the Customer Page Set
/polleo-adria isn't a one-off problem, it's a template case. The same under-10-impressions, zero-click threshold should get run against every customer page on the site: /alessi, /altex, /bloom-wolf, and the rest of the list. Some of those pages probably have real detail worth keeping. Others are almost certainly in the same spot as Polleo Adria's page: a logo and a paragraph nobody reads.
The fix isn't a one-time cleanup. It's a recurring quarterly pass, pulling impression and click data for every customer page and applying the same merge-or-noindex decision tree. Thin pages accumulate quietly if nobody's checking. One page like this barely moves the needle. Twenty of them start to look like a pattern to a crawler, and that's when sitewide quality signals start taking the hit.
Going forward, a customer page only earns a standalone, indexed URL if it has something specific and defensible in it: a named metric, a concrete workflow detail, something that couldn't be copy-pasted onto a competitor's logo and still make sense. If a founder or CEO is reading one of these pages to decide whether Trivas fits their specific role and stage, the page needs to actually tell them something. Generic logos and generic blurbs don't do that job, no matter how many of them you publish. And if trust and credibility is the goal, a page like our trust center does more real work than ten thin customer snapshots combined.
If you're running a similar audit on your own site and want to see how we're thinking about analytics, reporting, and the data behind decisions like this one, our resources section has more of this kind of breakdown. Worth a subscribe if content audits and ecommerce data practices are your thing.
Content author and contributor at Trivas.ai, sharing insights on e-commerce analytics, business intelligence, and data-driven strategies to help businesses grow.
Continue Reading
explore more insights
Shopify Store Performance Tracking in 2025: 13 Metrics That Actually Move Revenue
3 min read
Compare Trilio and Other Ecommerce Analytics Tools: A Buyer's Framework
3 min read
Ecommerce Data Platform Comparison: 7 Honest Options Ranked
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.ai
