.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiWe're pulling /resources/data-dictionary/tacos out of the sitemap and folding it into a bigger page. Here's the full audit trail: why it's getting pruned, what's worth saving, where it's going, and how we're handling the redirect so nothing breaks.
The numbers are the whole story here. Over the last three months, /resources/data-dictionary/tacos pulled under 10 impressions in Search Console and exactly zero clicks. Not low. Zero.
That's not a page that needs better meta copy or an internal link boost. That's a page nobody is searching for on its own. "TACoS definition" as a standalone query just doesn't have enough independent search demand to justify a dedicated URL. People who care about TACoS are almost always already reading about Amazon advertising metrics more broadly, ACoS, ROAS, TroAS, the whole set. They're not typing "what is tacos amazon" into Google and landing cold.
Here's the part people miss: a thin glossary page like this doesn't just sit there neutral, doing no harm. It actively drags on sitewide quality signals. Every page Google crawls that returns almost nothing to users eats into crawl budget and skews your content-depth ratios downward. A single-metric stub with 200 words of generic definition text is the kind of page that makes your whole /resources/data-dictionary/ section look thinner than it is.
Our decision framework is simple: any page under the minimum impression/click threshold with no backlinks pointing to it gets merged or noindexed. It doesn't get left alone just because it's "fine." This one cleared the threshold for pruning easily.
Not everything on the page is dead weight. A few things are worth carrying over intact:
What gets cut: the boilerplate "what is a metric and why does it matter" intro paragraph, the generic filler about data-driven decision making, and the thin "related terms" list at the bottom that just name-drops ACoS and ROAS without linking anywhere useful. None of that is unique content. It's the kind of padding that exists because glossary templates expect a certain word count, not because it adds anything.
The TACoS definition, formula, and ACoS comparison are getting folded into a consolidated section inside our broader Amazon ads metrics resource, something closer to an "Amazon Ads Metrics Explained" page than a standalone glossary entry.
The logic is straightforward: right now, TACoS, ACoS, ROAS, and TroAS each risk becoming isolated glossary stubs competing weakly for their own tiny slice of search intent. Combine them into one page and you get a single authoritative resource that can actually rank, instead of four thin pages that collectively rank for nothing. One strong page beats four weak ones, every time, on a topic this narrow.
Practically, that means the merged section needs to preserve the exact formula and any benchmark numbers, nothing gets softened or summarized away. If someone's citing that benchmark range in a client deck, the number shouldn't move just because the page did.
This pillar also becomes the natural anchor point for anyone researching Amazon ad performance more broadly, which is where Amazon advertising solutions and the general Amazon resources already live. A merged metrics page sitting next to those makes a lot more sense than a lone TACoS stub floating in the data dictionary with no context around it.
Once the pillar section is live with the merged content, the default move is a straight 301 redirect from /resources/data-dictionary/tacos to the relevant anchor on the pillar page. That preserves whatever residual link equity the old URL has, thin as it is, and sends anyone who did somehow bookmark it to the right place instead of a dead end.
If the pillar page isn't ready yet, the fallback is to apply noindex, follow to the existing page in the meantime. Leaving a near-zero-performing page indexed while we wait on content work isn't worth it. It just keeps contributing to the crawl budget and quality-signal problem described above.
Once the redirect is live and confirmed working, two cleanup steps follow immediately: pull the URL from the sitemap, and remove its entry from the internal data dictionary index listing. There's no reason for the data dictionary index to keep linking to a page that no longer exists as a destination.
The real fix here isn't just pruning one page, it's not creating the next five like it.
Going forward, we're not spinning up single-metric glossary pages for low-search-volume terms. If a metric doesn't have real standalone search demand, it gets bundled into the relevant pillar from day one instead of getting its own URL that sits there collecting zero clicks for a year before someone notices.
We're also adding a quarterly audit of every page under /resources/data-dictionary/*, measured against the same impression and click threshold used to flag this one. Catching this stuff every three months is a lot cheaper than catching it once a year after a dozen pages have quietly become dead weight.
And any new glossary entry that does get created needs to link back to, and be linked from, its relevant pillar immediately. No orphaned stubs. A metric definition with no path back to the broader resource it belongs to is exactly how pages like this one end up on a pruning list in the first place.
A few things to watch once the redirect goes live.
First, whether the merged pillar section starts picking up impressions for "TACoS" and "what is TACoS" queries within four to six weeks. If the consolidated page can't move the needle on those terms either, that tells us something different, maybe the search volume just isn't there at all, independent of how the content is structured.
Second, confirm the 301 is resolving cleanly. No 404s, no redirect chains stacking an old URL through two or three hops before landing on the final page. That's a quick technical check but an easy one to skip.
Third, keep an eye on the /resources/data-dictionary index page itself. If consolidating thin child pages like this one improves the overall quality profile of that section, we'd expect to see some ranking lift on the index page over the following months. That's as much a signal about whether this whole pruning exercise was worth it as the individual redirect is.
If you're digging into Amazon metrics beyond just TACoS, our guides and reports section has more detail on how these numbers connect to actual budget decisions. Worth a look if you're trying to figure out which metric should actually be driving your ad spend conversations, and subscribe if you want the next round of these audits and guides as we publish them.
explore more insights
3 min read
3 min read
3 min read