.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiThis is an internal content audit, published here for transparency into how we clean up our own resource library. The page in question: /alessi, a standalone customer story that's been live for a while but doing basically nothing for anyone. Here's the reasoning behind pulling it, and where that content is headed instead.
/alessi was built as a one-off customer story page. No other page on the site links to it, not the nav, not the footer, not a related blog post. It just sits there, orphaned.
The numbers confirm it. Over the last three months, /alessi pulled in under 10 impressions and zero clicks in Search Console. Zero. Not "low conversion," not "needs better copy." Nobody's finding it, and nobody's reading it.
The instinct with a page like this is to shrug and leave it alone. Low traffic, low stakes, right? Wrong. A thin, orphaned page with near-zero engagement doesn't sit neutral in Google's eyes. It's a data point in your site's overall quality signal, and a stale one at that. Enough pages like this scattered across a domain, and you're quietly dragging down how the rest of your content gets evaluated.
This document is the audit record for that decision. It's not written to rank, it's written to explain our own reasoning, for us and for anyone curious how we handle content pruning.
Two options were on the table. Fold the Alessi story into a broader case-studies hub, or noindex the page and let it fade out entirely.
We're going with merge-and-301. The underlying detail, what Alessi used Trivas for, which part of the product mattered to them, still has some narrative value. It's just not enough value to justify its own URL, its own meta tags, its own crawl budget. Consolidated into a bigger resource, that same detail actually gets seen.
Noindex is the fallback, not the first move. We'd reach for it only if there were no pillar page that could absorb the content without turning into a bloated mess. That's not the case here.
The destination is our case studies hub, the dynamic index where customer stories already live. It's the natural home for this kind of content, built specifically to hold multiple short narratives without needing a dedicated URL for each one.
Alessi's specifics, the product line, the use case, get folded in as a short entry or reference inside that page rather than resurrected as a standalone piece. No new URL, no new thin page to manage down the line.
Before finalizing, we checked for duplication. Nothing else on the site covers this same ground, so merging it in doesn't create a redundant thin page somewhere else. That's the failure mode worth watching for anytime you consolidate: you fix one problem and accidentally create its twin.
Once the merged content is live on /resources/case-studies, we set a 301 redirect from /alessi to that page. Standard move, but worth stating plainly since this is the actual audit trail.
From there, cleanup is mechanical but necessary:
/alessi from the sitemap, if it's listed there at all./alessi directly, and update those where we can.None of this is glamorous. It's the unglamorous part of SEO that actually matters more than people think.
Pruning a page like /alessi isn't going to move rankings on its own. Nobody should expect a traffic bump from retiring one near-zero-impression page.
What it does is stop the page from acting as a drag. Google evaluates sites in aggregate, and average page quality is part of that picture. Thin, orphaned, zero-engagement pages pull that average down even when they're individually invisible to users. Removing them is addition by subtraction.
This isn't a one-off either. /alessi is one page out of a larger content-bucket cleanup pass we're running across the site, hunting for other pages with the same profile: standalone, unlinked, and quietly underperforming. Treating this as an isolated fix would miss the point. The value is in doing it systematically.
Here's what happens from here, concretely:
/resources/case-studies and set the 301, with a target date on the calendar rather than a vague "soon."/alessi slipped through once, there's a good chance a few others are sitting in the same state right now.If you're curious how we think about content decisions like this one, or want to see what else is on our radar for cleanup, our resources section is a reasonable place to poke around. And if internal audits like this are useful to you, our newsletter covers more of the behind-the-scenes decisions we don't usually publish.
explore more insights
3 min read
3 min read
3 min read