Pruning the /items-sold Data Dictionary Page: Merge and Redirect Plan
by Trivas.ai
|
5 min read
Oct 19, 2026
Current State: Why This Page Is Flagged for Pruning
/resources/data-dictionary/items-sold pulled under 10 impressions and zero clicks over the last three months. Zero. Not "low conversion," not "needs a CTA tweak." Nobody is finding this page, and when they do (rarely, by accident), nobody clicks through to it.
A page that thin isn't just sitting there harmlessly. It actively drags down the quality signals search engines use to evaluate the whole section. Google doesn't score pages in isolation anymore, not really, it looks at patterns across a directory. A handful of ghost pages next to your stronger glossary entries makes the whole section look thinner than it is.
/resources/data-dictionary
Here's the root problem: items-sold is a single-metric glossary entry with no unique angle beyond a bare definition. It tells you what items sold means and stops there. No context on how it's calculated across channels, no worked example, nothing that would make someone bookmark it or link to it. That's why it never earned demand in the first place, and why it's not going to start now if we leave it alone.
What 'Items Sold' Actually Covers (For Merge Purposes)
Before we kill the standalone URL, it's worth documenting what's actually on the page, since none of this should get lost in the merge.
The core definition: items sold is the count of units sold over a given period, distinct from both revenue and order count. One order can contain five items. Revenue can go up while items sold goes down if average selling price rises. These are three different numbers that get conflated constantly, which is actually the one thing this page did right.
A few confusion points worth preserving when this gets folded into a broader entry:
Items sold vs. orders: an order is a transaction; items sold is a unit count within that transaction.
Items sold vs. units per transaction: units per transaction is items sold divided by order count, a derived metric, not the same thing.
Items sold vs. revenue: revenue tracks dollars, items sold tracks volume. A discount-heavy period can inflate items sold while revenue stays flat.
The page also cross-links to AOV and conversion rate as related metrics. Those links need to carry over wherever this content lands, otherwise we're quietly bleeding the internal link equity those connections built up, small as it may be.
Consolidation Target: Which Pillar Absorbs This Content
The cleanest home for this is a consolidated glossary section on the data dictionary index itself, where items-sold sits alongside related volume and revenue metrics instead of floating on its own orphaned URL. If a broader ecommerce metrics guide already exists under guides and reports at a glossary level, that works too, but only if it's actually built for definitional content, not a listicle that happens to mention the term in passing.
Either way, the merged version needs to do something the standalone page never did: add context from what Trivas dashboards actually show. How items-sold rolls up differently in Shopify reporting versus Amazon's unit session data, for instance, where the two platforms don't always agree on what counts as a "sold" unit (returns handling differs, bundle reporting differs). That's the kind of detail that turns a dictionary entry into something someone actually bookmarks.
One more thing before we move forward: we confirmed no other data-dictionary child page already covers items-sold under a different name. No duplicate target, no risk of merging into something that creates its own overlap problem.
301 Redirect vs Noindex: Decision Criteria
Default move here is a 301 redirect, straight to the consolidated pillar section, not the bare index page. That matters. If the merged content lives in a specific sub-section of /resources/data-dictionary, redirecting to the top of the index with no anchor just dumps the visitor somewhere they have to search again. That's a soft 404 wearing a 301's clothes. Technically resolved, practically useless.
Redirecting to the specific section preserves whatever residual link equity /resources/data-dictionary/items-sold has built up, plus it catches the handful of stray impressions still coming in. Small numbers, but there's no reason to throw them away for free.
If the merge target section doesn't exist yet, meaning the consolidated glossary entry hasn't actually been built and published, don't redirect to a placeholder. Noindex the page temporarily instead. Redirecting to an unrelated or half-finished URL is worse than leaving the thin page up a little longer. Get the merge content live first, then redirect.
Implementation Checklist
This isn't complicated, but skipping a step here is how you end up with broken link chains six months from now.
Audit inbound internal links. Find every page currently linking to /resources/data-dictionary/items-sold and update the anchor to point at the new consolidated location directly. Don't rely on the redirect to carry the weight forever, update the source.
Set up the 301 at the server or CDN level. Then verify it with a crawler, not just a manual click-through. It needs to resolve in a single hop. A redirect chain (301 to 301 to final URL) bleeds equity and slows crawl efficiency.
Submit the updated pillar URL for re-indexing through Search Console. Watch for the old URL to drop out of the index, which should happen within 2 to 4 weeks if the redirect is clean.
Re-check sitewide performance on the data-dictionary section 60 to 90 days post-merge. Impressions, CTR, the works. The whole point of this prune is to confirm the section performs better consolidated than it did scattered across thin pages. If it doesn't, that's a signal the merge target itself needs work, not that pruning was the wrong call.
Next Step
Treat this as a template, not a one-off. There are almost certainly other entries in the data dictionary sitting at single-digit impressions with zero clicks, the exact same profile as items-sold. Flag them now, before they pile up into a dozen separate prune-and-merge projects instead of one coordinated pass.
Once this particular merge goes live, the data dictionary index is the place to see the consolidated structure in practice, glossary entries grouped by what they actually measure instead of scattered one metric per orphaned URL.
If you want a closer look at how we think about metrics definitions and reporting structure in general, the guides and reports library is worth a browse, and it's probably worth subscribing to updates if you'd rather not keep checking back manually.
Content author and contributor at Trivas.ai, sharing insights on e-commerce analytics, business intelligence, and data-driven strategies to help businesses grow.
Continue Reading
explore more insights
The Ecommerce Analytics Setup Guide for Shopify Brands (Step by Step)
3 min read
Ecommerce Analytics With Margin-Aware ROAS: Stop Optimizing Toward Unprofitable Growth
3 min read
Ecommerce Analytics for Beauty Brand Shopify: 7 Use Cases
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
