.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiThree months. Under 10 impressions. Zero clicks.
That's the full performance record for /mind-the-beauty, a case study page sitting on the site. Not "underperforming." Not "needs better keywords." Just... not there, as far as search traffic is concerned.
It's tempting to shrug this off. Low traffic isn't the same as harmful, right? A page just sitting quietly in a folder somewhere isn't costing you anything.
Except that's not quite true. The real question isn't whether /mind-the-beauty is helping. It's whether it's actively dragging down the pages that are supposed to be working. That's a different audit entirely, and it's the one most teams skip.
Here's the part that gets missed: crawl budget isn't infinite, and it isn't evenly distributed by merit. Search engines allocate crawl time based on signals across the whole site. Every thin, orphaned page you leave live is competing for that attention against the pages actually driving revenue.
A one-off customer page that's mostly boilerplate, same layout, same three sentences about "results," same stock testimonial structure as a dozen other case studies, isn't adding unique value. It's adding overlap. And overlap reads as duplication, even when no two pages are word-for-word identical.
This matters more at the site level than at the page level. Google doesn't evaluate /mind-the-beauty in isolation and decide "fine, harmless, leave it." It factors into a broader read of site quality: how much of your content is substantive versus how much is filler wearing a different customer's logo.
A long tail of these pages can suppress ranking potential for the content that actually deserves to rank. That's the mechanism worth worrying about, not the zero clicks on one page.
Once you've flagged a page like this, there are really only three moves.
Merge. Pull anything genuinely unique from the page, usually the specific customer detail or result, and fold it into a stronger page that already earns traffic. A pillar page, a resource hub, something with existing authority to absorb it into.
301 redirect. Point the old URL at that stronger page so any backlink equity or lingering authority doesn't just evaporate.
Noindex. Reserve this for pages with nothing worth saving and no inbound links worth protecting. If removing it loses you nothing, don't bother merging, just pull it from the index.
The decision rule is simple once you frame it that way: zero unique value and zero backlinks means noindex. A usable customer story with at least some narrative worth keeping means merge and 301. Most pages fall into the second bucket more often than teams expect, because even thin case studies usually have one real detail buried in them.
For /mind-the-beauty specifically, the content had a usable story buried under generic structure. Not enough to justify a standalone page nobody was finding anyway, but enough to be worth keeping somewhere.
So it got merged into the case studies hub, and the old URL was 301'd there. That consolidation target made sense for one simple reason: it's the page actually getting found. Folding the Mind The Beauty story into an index that already has organic visibility means the content lives somewhere people will actually see it, instead of sitting on an orphaned URL collecting zero clicks quarter after quarter.
This isn't deletion. It's relocation. The customer story stays intact, it just stops demanding its own dedicated page with its own crawl budget and its own quality signal to drag down.
The process that caught /mind-the-beauty isn't complicated, and you don't need a specialized tool to start it.
Pull impressions and clicks per URL over a 90-day window. Flag anything under 10 impressions with zero clicks. That's your starting list.
From there, check for structural overlap. Case studies, location pages, product variant pages, these are the usual suspects because they're built from templates and tend to repeat the same boilerplate with minor swaps. If five pages on your site follow an identical structure and only one of them gets found, the other four are candidates for the merge-or-noindex conversation, not just the one with zero traffic.
A few things worth checking before you decide:
If you're managing a growing content library, this kind of audit gets harder to do by hand as the page count climbs. Running pages through a content scoring tool before they pile up is a faster way to catch thin pages while there are still a dozen of them instead of a hundred.
Pruning isn't about making a site smaller for its own sake. It's about making sure the authority you've built concentrates on the pages that actually earn traffic, instead of getting spread thin across pages nobody lands on.
/mind-the-beauty wasn't a disaster. It was a quiet drag, the kind every growing content library accumulates without anyone noticing until someone pulls the impressions report.
If you're running an ecommerce blog or case study library that's grown past the point where you can eyeball every page's performance, it's worth running this same exercise. Pull the 90-day data, flag the zeros, decide merge or noindex for each one.
For a more repeatable version of this process, the guides and reports library has more on building a content audit workflow you can run quarterly instead of once by accident.
explore more insights
3 min read
3 min read
3 min read