.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiThis is the first in a series of internal audit notes we're publishing as we clean up Trivas's own site. The page in question: /autodoc, a customer story URL that's quietly been doing nothing for three months straight. Here's what we found, and what we're doing about it.
The numbers are blunt. Under 10 impressions and zero clicks over a 90-day window in Search Console. Not "underperforming." Not "needs optimization." Zero.
That distinction matters. A page ranking on page 3 for a decent keyword has a demand signal you can work with: tweak the title, add internal links, build out the content. /autodoc has none of that. Nobody is searching for it, nobody is finding it by accident, and there's no keyword gap to close because there's no keyword it's remotely competitive for.
Worse, a page like this isn't just sitting there neutrally. Google evaluates site quality in aggregate, and a thin, orphaned, zero-engagement page is a small negative weight on that evaluation, not a dormant asset waiting for its moment. It's actively doing nothing good.
Worth being clear on what this page actually is, too. /autodoc isn't a generic blog post or guide that happens to be underperforming. It's a single-customer brand story, built around one client's results. Pages like that are useful for sales and credibility, but they were never designed to carry standalone organic weight.
Single-customer story pages almost never earn their own organic search intent. Think about how buyers actually search. They look for "ecommerce analytics for Shopify brands" or "Amazon and Shopify reporting tool," not "Trivas Autodoc results." Nobody types a vendor's client name into Google unless they already know the relationship exists, which defeats the purpose of ranking for it in the first place.
Then there's the link graph problem. We checked, and there are currently no internal links pointing to /autodoc. It's an orphan. That's not a small technical footnote, it means there's zero link equity being protected by keeping the page live as-is. If this were a heavily linked page, redirecting it would need more care. It isn't, so it doesn't.
The content itself is also just thin by nature. One customer, one narrative, one set of results. That's never going to compete against a broader pillar page that aggregates multiple customer outcomes across categories like Amazon and Shopify. Breadth wins here, and a single-story page can't fake breadth.
Net effect of leaving it alone: it drags on crawl budget and site-quality signals, with literally no traffic upside to offset it. That's not a close call.
The primary move is straightforward: fold the Autodoc story into the case studies hub, or into whichever case-study pillar entry fits best, then 301 redirect /autodoc straight to that destination.
If there's no appropriate case-study destination (say, the content genuinely doesn't fit anywhere else), the fallback is to noindex the page but leave it live. That keeps it usable for sales decks or direct links in outreach emails without pretending it'll ever pull organic traffic. Noindex-but-live is a perfectly fine outcome for assets that serve a sales function rather than a search one.
Either way, don't lose the substance. Any real metrics, quotes, or results tied to the Autodoc story should get folded into the merged destination. The goal is to preserve the proof point, not the URL. Rebuilding it as a new standalone page later would just recreate the same problem.
One technical note worth stating plainly: redirect directly to the final pillar URL. Don't route it through an intermediate page that then redirects again elsewhere. Redirect chains add latency, make auditing harder down the line, and occasionally get Google to just... not follow all the way through. Point it once, point it correctly, done.
If the destination is /resources/case-studies, the Autodoc data shouldn't become its own full page there either. It should show up as one entry or card, consistent with how other customer stories are already surfaced on that index. The point of merging is consolidation, not duplication under a different URL.
The pillar itself works best when it stays focused on aggregate proof, not individual narratives. Multiple customers, multiple categories (Amazon results sitting next to Shopify results, for instance), gives visitors and search engines a much stronger signal than any single story could on its own. That's the entire logic behind doing this merge in the first place.
This is also a decent opportunity to strengthen the pillar generally while you're in there. Adding real structured data points to an existing hub is a lot more defensible in search than letting single-customer pages scatter across the site each trying to rank on their own. One strong page beats five weak ones.
Before closing this out, it's worth checking whether other brand pages on the site have the identical problem (near-zero traffic, no inbound links, single-customer scope). If they do, this becomes a template, not a one-off. More on that below.
Here's the actual sequence, in order:
None of this is complicated. It's just sequencing, and skipping a step (like forgetting the sitemap) is how these cleanups get half-done.
Treat this audit as the template, not the endpoint. The same criteria apply to any other low-traffic, single-customer page on the site: near-zero impressions and clicks over a rolling three-month window, combined with no inbound internal links. Any page that hits both of those is a pruning candidate, full stop.
Work through them one at a time rather than batch-redirecting everything at once. Each page deserves the same check: is there unique data worth preserving, is there a sensible merge destination, is a redirect actually appropriate or is noindex the better call. Rushing a batch job risks losing content or creating redirect chains nobody catches until later.
Whatever crawl budget and quality signal gets freed up here should go toward strengthening the pages that already show real search demand, the pillar content and solution pages people are actually finding. That's where the growth is. If you're newer to how we think about structuring that kind of content, the getting started guide is a decent starting point.
Worth revisiting, too: if Autodoc-specific search demand ever actually shows up in a future audit, that's a different conversation. Right now it hasn't, so this is the right call.
If you want more of these audit breakdowns as we work through the rest of the site, our blog is where we'll keep posting them.
explore more insights
3 min read
3 min read
3 min read