.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiWe're pruning /resources/data-dictionary/video-gmv. Under 10 impressions and zero clicks over the last three months, which is about as clear a signal as you can get that a page isn't earning its keep. This post walks through why it's getting merged and redirected instead of just left alone, and what that means for the rest of the data dictionary.
The trigger is simple: fewer than 10 impressions and zero clicks across a 3-month window. That's not "needs an SEO refresh" territory. That's a page nobody is finding, and nobody is clicking on when they do.
Here's the part that's easy to miss. A page like this isn't neutral just because it's not actively hurting anything you can point to. Google crawls it, indexes it, and factors it into how it evaluates the whole domain's quality. A near-zero-traffic definitional page sitting in your site architecture is a small drag on sitewide signals, not a harmless placeholder.
There's also a consolidation problem. Thin, single-metric glossary pages like this one end up competing against each other, and against broader guides, for the exact same search intent. Instead of one strong page ranking for "video GMV" and related terms, you get three weak ones splitting whatever authority exists between them.
This isn't a one-off decision. It's part of an ongoing pruning pass across the entire data dictionary section, where every entry gets checked against the same impressions and clicks threshold.
For the record: video GMV is gross merchandise value attributed to video-driven commerce. Live shopping events, shoppable video embeds, TikTok Shop style placements where a purchase traces back to a video interaction. It's a real metric, just a narrow one.
The problem is overlap. Video GMV as a concept sits so close to broader GMV definitions, and to video-commerce attribution topics, that it rarely needed its own standalone page in the first place. Anyone searching for this term is usually also searching for, or would be better served by, content that already exists (or should exist) elsewhere on the site.
And the search volume just isn't there. "Video GMV" as an exact phrase doesn't pull enough monthly search volume to justify its own URL, its own crawl budget, or any internal link equity pointed its way. Low-volume definitional terms like this one belong as a subsection of something bigger, not as their own page competing for scraps.
The default move is folding the definition and any useful examples into the data dictionary index page itself, rather than creating or propping up another standalone glossary entry. One less URL, one stronger page.
If there's already a broader guide covering ecommerce metrics or video-commerce attribution living in guides and reports, that's actually the better home. A guide that already ranks for adjacent terms and gets real impressions is a much stronger host for this definition than the dictionary index would be.
Picking between the two comes down to three things:
Not everything on the old page deserves a new home. Here's what survives the merge:
The core definition sentence carries over, assuming it's accurate and doesn't just restate something the target page already says. No point duplicating language that's already live elsewhere.
Everything else gets a hard look. Most single-metric glossary pages pad themselves out with a generic "why this metric matters" section that says nothing specific to video GMV, the kind of boilerplate that could be copy-pasted onto any metric page on the internet. That gets cut. If it doesn't teach the reader something unique to this metric, it's not worth carrying forward.
If the original page had a real example calculation or formula, that's worth keeping, maybe tightened up. If it didn't, or if what's there is vague, the merged version gets a cleaner one-liner instead, something like: video GMV = total order value from purchases initiated through a video or live shopping session. Short, specific, done.
Once the merge target is locked in, the primary move is a 301 redirect from /resources/data-dictionary/video-gmv to that URL. That passes along whatever minimal equity the page has and sends both users and crawlers to the live, useful version of the content.
If there's genuinely no clean merge target (no existing page close enough topically to host the definition without it feeling bolted on), the fallback is a noindex tag instead. The page stays live for the rare case someone has it bookmarked or linked directly, but it comes out of the data dictionary's internal navigation and out of the sitemap. No reason to keep sending crawl budget toward it.
Before any of that goes live, it's worth running a quick internal link check. Anything site-wide that still points to the old URL, whether that's another dictionary entry, a guide, or an old blog post, should get repointed to the merge target first. Redirecting the page but leaving stale internal links behind just creates an extra hop for no reason.
Last step: update the XML sitemap so the pruned URL stops showing up for recrawl. Small thing, easy to forget, and it's the difference between Google dropping the page quickly versus it lingering in the index for months.
Pulling a thin, zero-engagement page out of circulation isn't about losing a page, it's about consolidating. Whatever thin authority /resources/data-dictionary/video-gmv had moves to a page that's actually positioned to rank for something.
The bigger win is structural. Every near-duplicate glossary entry you remove lowers the odds that Google looks at the data dictionary section as a whole and files it under "low-value content produced at scale." That's not a label you want attached to an entire section of the site, and it's not one bad page that creates it, it's a pattern of them.
This page is one data point in a larger audit. The same under-10-impressions, zero-click threshold should get applied across every other entry in the dictionary, and the ones that fail it should get the same treatment: merge where there's a real home, noindex where there isn't.
Before touching the redirect, confirm the merge target with whoever owns /resources/data-dictionary. Picking the wrong host page undoes the whole point of this exercise.
Set a 90-day reminder to check Search Console after the redirect goes live. Confirm the old URL has actually dropped out of the index, and just as important, confirm the merge target's impressions haven't taken a hit from absorbing content it wasn't built around.
Then move to the next batch. Run the same impressions and clicks check across the rest of the data dictionary, and apply this same merge-or-noindex framework to whatever else falls under the threshold.
If you're curious how we think about content audits and metric definitions more broadly, it's worth poking around our guides and reports or getting a sense of the basics over in getting started. Feel free to subscribe if you want future pruning writeups like this one landing in your inbox instead of your search results.
explore more insights
3 min read
3 min read
3 min read