.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiThis is an internal audit note, written up for anyone else who touches our content pruning process. The page in question: /bloom-wolf. Over a 3-month window it pulled fewer than 10 impressions and exactly zero clicks. That's not a slow page. That's a page nobody is finding.
Under 10 impressions and zero clicks across three months isn't a rounding error, it's a signal. A page at that volume isn't underperforming, it's invisible.
Here's the part people miss: a near-zero-traffic page with thin or duplicated content isn't neutral for the rest of the site. Google doesn't evaluate pages in isolation. A pattern of low-value URLs tells the crawler something about the whole domain, and that assessment can bleed into crawl budget allocation and how much topical authority the site gets credited with elsewhere.
/bloom-wolf is a standalone customer page. No internal links point to it. Nothing in the nav, nothing in a related-resources block, nothing contextual pulling a reader there. It also has no supporting content ecosystem, no companion blog post, no linked guide, nothing building a topic cluster around it. It's an orphan page with a brand name on it, sitting there collecting dust and quietly telling search engines "this site has filler."
Pulled up the live page to see what we're actually dealing with. It's a single customer brief. Short. Generic. The kind of copy that reads like a template with a logo swapped in.
There's no unique data point anywhere on the page. No metric tied to a specific outcome, no timeline, nothing that couldn't apply to a dozen other brand pages on the site. The "results" section uses the same boilerplate language we're running on several other customer pages, phrases like strong growth and improved visibility that say nothing concrete.
That overlap is the real problem. When two or more pages use near-identical phrasing to describe different customers, it reads as duplicate content even if the brand name technically changes. Search engines are good at pattern-matching this kind of template reuse now.
Bottom line: there's no case-study proof point here. No quote, no workflow detail, no specific metric strong enough to justify this living at its own indexed URL. If we can't point to one concrete thing that makes this page worth a standalone address, it shouldn't have one.
If there's anything on /bloom-wolf genuinely worth keeping, even a single sentence of unique detail, the move is to fold it into case studies as a supporting entry rather than its own URL. One paragraph in a larger roundup carries more weight than a thin standalone page ever will.
Once that content is merged, set up a 301 redirect from /bloom-wolf to the case studies index. This matters for one reason: it consolidates whatever residual link equity the page has instead of just letting it evaporate. Doesn't have to be much equity to be worth capturing.
One caution here. When merging, keep the brand name mention short and factual. Don't pad the merged section with invented stats or quotes that weren't already documented on the original page. If the only thing to say about bloom-wolf is a sentence, say the sentence. Resist the urge to dress it up into something it isn't. That's how thin content problems start in the first place, by inflating a page past what it actually earned.
If there's genuinely nothing reusable on the page, don't redirect it. Noindex it instead.
This is a distinction worth being strict about. A 301 redirect implies there's a legitimate content relationship between the old page and the destination. If /bloom-wolf has nothing worth preserving and we redirect it anyway, we're manufacturing a relationship that isn't real. Do that across a handful of thin brand pages and you get what looks, to a crawler, like a soft 404 pattern: redirects that don't actually lead to equivalent content. That's worse than leaving a thin page alone.
So the decision criteria, written down plainly:
For /bloom-wolf, based on what's actually on the page right now, it leans toward option B. But that call should get revisited once someone checks whether there's a draft, a quote, or an internal note somewhere that didn't make it onto the live page.
Once noindexed, pull the URL from any sitemap.xml entries too. A noindex tag tells search engines not to show the page, but leaving it in the sitemap keeps inviting a crawl and a recheck. No reason to keep asking the question once the answer's decided.
/bloom-wolf isn't going to be the only page like this. We've got a long list of customer and brand pages: alessi, altex, autodoc, bluevua, carturesti, and plenty more down the list. Each one deserves the same gut check: under 10 impressions, zero clicks, same 3-month window.
The right move is batching these into a single prune pass, not picking them off one at a time over months. Search engines don't evaluate thin-content problems page by page, they read it as a site-level pattern. Fixing one orphaned brand page while five others sit in the same state barely moves the needle. Fixing all of them in one pass sends a much clearer signal that the site is actively maintained.
Worth building this into a recurring check too; quarterly makes sense. Customer pages get added as deals close and partnerships get announced, and if nobody's watching, new thin pages will quietly pile up the exact same way /bloom-wolf did. Better to catch that at the 3-month mark than let it sit for a year.
Whoever owns case studies needs to confirm the merged content, if there is any, actually fits the page's existing structure before any 301 goes live. Don't ship a redirect to a page that can't cleanly absorb what's being merged into it.
Set a firm date to implement whichever fix applies, the 301 or the noindex tag, and confirm it's reflected in Search Console within two weeks. Two weeks is enough time to catch a bad deploy before it sits unnoticed for a month.
Then circle back in 30 days. Check impressions, check indexing status, confirm the fix actually did what it was supposed to. If /bloom-wolf is noindexed and still showing up in search results after 30 days, something in the implementation didn't take, and that's worth catching early rather than finding out at the next quarterly audit.
If you're building out your own version of this kind of audit process, our resources and guides section has more on setting up recurring content checks, and it's worth subscribing if you want these kinds of notes as we publish them.
explore more insights
3 min read
3 min read
3 min read