.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiWe're pruning a page. Specifically, /resources/data-dictionary/live-sessions is getting folded into a bigger resource and redirected. If you landed here wondering why the old URL doesn't work anymore, or you're just curious how we decide what stays and what goes on our site, here's the full reasoning.
The numbers made this an easy call. Under 10 impressions and zero clicks over three months. Not "underperforming," not "needs better SEO," just not getting found and not getting used.
A thin definition page sitting at near-zero traffic isn't neutral. That's the part people get wrong. It's not just taking up space quietly in the background. An orphaned, single-metric glossary entry competes with our own better resources for crawl budget and relevance signals, and it tells search engines our site has a bunch of shallow pages instead of a few comprehensive ones.
So this isn't "let's clean up some clutter because it looks nicer." It's "this page is actively working against the pages we actually want to rank." Once you frame it that way, pruning stops being optional.
We're not losing the definition, just its standalone home. For the record: live sessions means the number of concurrent active user sessions on a storefront or app at a given moment. It's a snapshot, not a sum.
That's different from total sessions (a count over a time period, like a day or a week) or pageviews (every page load, regardless of whether it's a new session or an old one). Confusing those three is extremely common, and honestly that confusion was probably the whole reason this page got created in the first place.
The definition isn't disappearing. It's moving into a consolidated metrics glossary where it has company: other related terms that help explain what makes it different, instead of sitting alone with no context.
Here's the structural problem with one-metric-per-URL glossary pages: most of them will never earn enough search volume on their own to justify a dedicated page. "Live sessions" as a search term just doesn't have standalone demand. But "real-time ecommerce metrics explained" or an analytics glossary pillar does, because people searching for one term in this space are usually trying to understand several related ones at once.
So instead of dozens of near-empty definition pages each targeting a term nobody searches in isolation, we're folding live sessions into a broader pillar page covering real-time and dashboard metrics together. Active users, live sessions, concurrent visitors: these get grouped because that's how people actually think about them when they're staring at a dashboard trying to figure out what they're looking at.
A single comprehensive page converts better too. Someone comparing active users vs. live sessions doesn't want two separate tab opens, they want it on one page, with the distinction laid out next to the related metric they're actually trying to understand.
The technical cleanup here is straightforward, but we're doing it in order so nothing breaks along the way.
First, a 301 redirect from /resources/data-dictionary/live-sessions to the relevant section inside the consolidated metrics pillar. If that pillar section isn't live yet by the time this page gets pulled, the fallback is to noindex the old page immediately rather than leave a thin page indexed while we wait on the merge to get scheduled and built.
Alongside the redirect, we're pulling the URL from sitemap.xml and auditing internal nav and footer links that still point to it, so nothing in our own site architecture is routing people (or crawlers) to a dead end.
Worth setting expectations here: organic demand for this specific URL is close to zero, so this isn't about "saving" meaningful traffic. It's about preserving whatever residual link equity exists and making sure nobody, human or bot, hits a 404.
We didn't invent this process for one page. It's a standing rule now, applied across the whole data dictionary.
The threshold: any page under 10 impressions and zero clicks over a rolling three month window gets flagged for review. Flagged doesn't mean automatically deleted, it means someone actually looks at it and decides between three outcomes:
One thing we're not doing: pruning definition pages tied to terms with real search demand. ROAS, CAC, that kind of thing. Those stay standalone because people genuinely search those terms directly, often before they've even picked an analytics tool. Live sessions never had that kind of demand on its own, which is exactly why it's a merge candidate and ROAS isn't.
If you're looking for metric definitions generally, the data dictionary index is still the right entry point, it'll route you to wherever live sessions and its neighboring terms end up living.
If you want the practical side, how to actually read and configure this stuff on a live dashboard rather than just define it, our dashboards and analytics help content is the better resource. The glossary tells you what a metric means. The help docs tell you what to do with it.
And if you're in the middle of evaluating your analytics stack and tired of needing a glossary open in a second tab just to read your own dashboard, that's a sign worth paying attention to. Trivas surfaces metrics like live sessions in context automatically, so you're not stopping to look up a definition in the first place. Worth a look if that sounds familiar, or just subscribe to see what else we're building.
explore more insights
3 min read
3 min read
3 min read