Pulling ST reports across 14 client accounts this week, the pattern is unmistakable: the long tail is getting longer and stranger.
Queries like “cordless drill for arthritic hands” or “kitchen shears for left-handed baker”, the kind of oddly-specific strings that used to show up twice a year, now represent 6-11% of impressions on most of the accounts we manage. They convert at 2-3x the category average. They’re almost entirely invisible to keyword tools.
That’s Rufus doing what it was designed to do: rewrite fuzzy shopper intent into shopper-specific queries. And the implication is uncomfortable for any agency still selling “keyword harvesting” as a core service. Helium 10’s database can’t see queries that were generated on the fly inside a Rufus session and never typed by anyone. Jungle Scout’s volume estimates are based on autocomplete scraping. MerchantWords aggregates surfaced search terms. None of these tools index the queries Rufus builds in the moment, against a specific shopper’s prior conversation, that lead to a converting click. The static keyword universe is shrinking as a share of the actual demand curve, and the brands optimizing against the static universe are spending against a smaller and smaller piece of the real opportunity every quarter.
The numbers across our 14-account sample: in Q4 2024, oddly-specific intent queries (use-case + condition + persona modifiers) were 2.1% of attributed impressions on average. In Q1 2026, that’s 8.4%. A 4x increase in 15 months. Conversion rate on those queries is averaging 12.8% against a category mean of 4.6%, which makes sense, because they’re high-intent: the shopper is describing exactly what they need.
The move isn’t to chase the long tail manually. The math doesn’t work, there are too many variations and they shift weekly. The move is to make sure your catalog (A+ Content, backend keywords, bullet structure) is answering in Rufus’s voice, not just matching strings. That’s the work, and it’s structural rather than tactical.
What that means in practice: the FAQ module on your detail page is now the highest-leverage real estate you have, because it’s the most natively Rufus-readable surface. Three FAQ items written in the actual phrasing of long-tail queries (pulled from the bottom 30% of your ST report by impression count, where the high-intent niche queries live) gets you cited in Rufus summaries on queries you’d never have bid on. The brands that have done this since Q3 2025 are gaining share against the brands that haven’t, on the same SKUs, against the same competitors. The change isn’t visible in ACoS, it’s visible in impression-share growth on queries the brand wasn’t bidding on.
The same logic applies to A+ body copy. If your A+ describes your product in marketing-friendly brand language (“designed for the modern home chef”), Rufus has nothing to match against a query like “knife for arthritic hands.” If your A+ describes the product in attribute-completeness language (“ergonomic grip designed for users with limited hand strength”), Rufus has a clear semantic match. Same product, same image, dramatically different visibility. The Cosmo-aware A+ rebuild we run on every account is structured to make these matches visible to Rufus rather than hidden behind brand-language abstraction.
The brands compounding right now are treating their catalog as a software product: versioned, instrumented, edited weekly against the actual queries showing up in their ST reports. The brands keeping the keyword-tool playbook alive are slowly losing visibility on the queries that didn’t exist three years ago and account for a growing share of conversions today. The dashboard doesn’t show the loss. The market share trajectory does.
This isn’t a future concern. It’s the work right now.
Subscribe to the Operator Brief, we cover Rufus and Cosmo behavior weekly.