.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiWe pull up the analytics for /underlining every quarter as part of our content audit, and every quarter the story's the same: under 10 impressions, zero clicks, three months running. That's not a slow page. That's a page nobody's finding, and the handful of people who stumble onto it aren't clicking through from search at all.
This post walks through why we're retiring it, what "retiring" actually means in practice, and the decision framework we use any time a page shows this pattern.
Let's just sit with the numbers for a second. Under 10 impressions across 90 days. Zero clicks. Not "low" clicks, zero.
A page like this isn't neutral. It's tempting to think a quiet page just sits there, doing no harm, waiting for its moment. That's not how Google evaluates a domain. Pages with near-zero engagement contribute to the overall quality picture search engines build of your site, and that picture informs how much trust gets extended to everything else you publish.
To be clear: this isn't a knock on the customer story or brand content that originally lived on /underlining. The underlying narrative might be solid. The problem is structural. As a standalone URL, this page has no search demand attached to it, no internal traffic funneling to it, and no ranking signal worth protecting. Those are two different judgments, and conflating them is how teams end up keeping dead weight around out of sentimentality.
Every page on your site costs something to maintain in a search engine's eyes. Crawlers spend time and resources indexing it, and if that spend produces zero return, you've essentially burned crawl budget on a page that was never going to rank for anything.
That's the direct cost. The indirect cost is bigger. A domain full of thin pages with near-zero traffic tends to get assessed as lower overall quality, and that assessment can quietly suppress ranking potential even on your pages that are actually performing well. One orphaned page won't tank your site. A pattern of them will.
And /underlining fits the pattern exactly. It has no meaningful internal link equity pointing to it, nothing from the nav, nothing from related content, no editorial links from other pages on the site. That absence is itself diagnostic. If a page were genuinely valuable, something elsewhere on the site would be pointing to it. Nothing is, which tells you it was never structurally positioned to rank in the first place.
We don't delete pages just because they're underperforming. Deleting throws away whatever residual value exists, however small. Merging preserves it.
Before touching anything, we go through the content on /underlining and pull out anything with actual substance: a customer outcome, a specific data point, a detail that doesn't exist anywhere else on the site. That content doesn't get lost. It gets folded into a stronger, more relevant page where it has a shot at actually being found.
In this case, that destination is our case studies hub. Any customer-story content currently stranded on this orphaned URL belongs there instead, alongside other brand stories that already have the internal linking and topical context to support them.
Once the content's consolidated, we set up a 301 redirect from /underlining to that destination. This does two things: it passes along whatever residual link equity the old URL had accumulated, and it means the small number of people who do land on that link (an old bookmark, a stray backlink, whatever) don't hit a dead end. A redirect respects the handful of visitors who still show up, even when search engines have mostly stopped sending anyone there.
Merging isn't always the right call. Sometimes the content on a thin page has zero unique value, no customer outcome worth preserving, nothing that isn't already covered elsewhere. Maybe it's a near-duplicate of another customer page. Maybe it's boilerplate that got spun up and forgotten. Maybe it's just outdated.
In that case, don't force a redirect. Redirecting content with no real topical overlap into a stronger page dilutes that page's relevance instead of strengthening it. You're better off noindexing the thin page and letting it fade out on its own.
The rule we use is simple: redirect when there's a clear topical match for the content somewhere else on the site. Noindex when there isn't. Forcing a redirect just to "do something" with a dying page usually causes more harm than leaving it alone.
One catch with noindexing: the page still needs to stay crawlable in the short term. Search engines have to actually see the noindex tag to act on it. Pull the page from the sitemap too early or block it from crawlers entirely, and that directive might never get processed. Keep it crawlable, then monitor over the following weeks to confirm it drops out of the index.
Whichever path you take, the cleanup work is the same shape. Here's what we run through for every page we prune:
/underlining isn't a one-off fix. It's one output of a process we run on a recurring basis, and it shouldn't be treated as a special case just because this particular page happened to surface it.
Every quarter, we flag any page falling under a defined impression and click threshold and run it through the same merge-or-noindex decision. Some pages get folded into stronger pillars. Some get noindexed and left to quietly disappear. Either way, the thin page doesn't just sit there accumulating as dead weight on the domain.
Fewer thin pages means a higher average quality signal per page across the whole site, and that compounds. It's not that pruning one page moves the needle much on its own. It's that doing this consistently, every quarter, means the pages that are actually worth ranking get a cleaner shot at it.
If you want to see how we think about content structure more broadly, our resources and guides hub covers more of this kind of audit work, and our getting started guide is a decent starting point if you're setting up your own content review process from scratch. Worth a subscribe if this is the kind of operational detail you want more of.
explore more insights
3 min read
3 min read
3 min read