AI Summary
Amazon’s AI shopping assistant Rufus now handles 18 to 22% of all product discovery sessions on mobile, and it doesn’t care about keyword density. It runs on COSMO (Common Sense Model of Shopping), Amazon’s proprietary algorithm that replaced A9 for AI-assisted queries, evaluating semantic clarity, structured data completeness, and review quality instead of traditional keyword matching. If your listing optimization strategy was built for A9, you’re optimizing for an algorithm that no longer runs.
What is Amazon Rufus and how does COSMO work?
Rufus launched broadly in the US in July 2024 and became core to the mobile shopping experience in 2025. Built on Amazon Bedrock, it’s a multimodal AI that combines text, images, and structured product data to answer natural language questions like “What’s the best espresso machine for beginners under $200?”
The COSMO algorithm processes queries by extracting entities (product category, price range, use case, skill level), then scoring candidates using a semantic graph of the entire Amazon product catalog, including reviews, Q&As, and frequently bought together data. This is fundamentally different from A9:
- A9: Keyword matching + click/conversion signals
- COSMO/Rufus: Semantic entity understanding + contextual relevance + conversational intent
According to Tinuiti’s March 2026 research, products optimized for Rufus see an average 27% increase in visibility in conversational search results. The shift is real and measurable.
The 5 ranking factors that COSMO weights most heavily
Based on data from SellerMetrics, Amalytix, and SellerLabs, Rufus weights these five signals disproportionately:
- Backend attribute completeness. Listings with 100% of category-specific backend attributes filled see 34% higher Rufus ranking. Rufus trusts structured, machine-readable data more than unstructured text because it’s consistent across the catalog.
- Q&A library depth. Products with 15+ answered Q&As rank 2.1x higher. Rufus treats Q&As as verified product information, they’re signal-dense and directly answer shopper questions.
- Review use-case specificity. Products with 4.5+ star ratings and 20+ reviews mentioning specific use cases are 3.2x more likely to be recommended. Generic “great product!” reviews do nothing for Rufus.
- A+ Content structure. A+ Content with structured comparison tables increases Rufus recommendation rate by 41%. Rufus pulls these directly for the 73% of queries that are comparison-based.
- Lifestyle image count and context. Listings with 6+ lifestyle images showing the product in use get 29% more citations. Rufus analyzes images using computer vision.
The comparison query problem: 73% of Rufus queries
The most important insight from Amalytix’s analysis: 73% of Rufus queries are comparison-based (“best X for Y”) versus 41% in traditional Amazon search. This is the single biggest strategic shift sellers need to make.
We’re seeing 73% of Rufus queries are comparison-based. If your listing doesn’t explicitly state what makes you different from alternatives, Rufus won’t recommend you even if you have the best keywords.
Amalytix, March 2026
What this means practically: your A+ Content needs a competitor comparison table, your bullets need to state your differentiation explicitly, and your Q&A section should include “How does this compare to [main competitor]?” as an answered question.
This optimization approach connects directly to the broader ecommerce AI search product discovery playbook and the marketplace aggregator AI search optimization frameworks covered elsewhere on this blog.
10 actionable Rufus optimization steps
- Implement noun-phrase SEO in bullets. Structure bullets as “[Use Case]: [Benefit]”, e.g., “For Beginners: One-touch operation with automatic milk frother.” Not just “espresso machine.” (SellerMetrics)
- Fill 100% of backend attributes. Go to your Seller Central listing, expand every attribute section, and complete all category-specific fields, material, size, color, target audience, use case. Rufus heavily weights structured data. (SellerLabs)
- Build a comparison table in A+ Content. Create an explicit “vs. competitor features” module. Rufus pulls these for comparison queries, which represent the majority of AI-assisted searches.
- Research and answer question-based keywords. Use Amazon’s Search Query Performance report to find what questions shoppers ask about your category, then answer those questions in your bullets.
- Proactively populate the Q&A section. Seed 15-20 questions with detailed, accurate answers before customers ask. Common formats: “Who is this best for?”, “What’s the difference between X and Y model?”, “Does it work with [specific use case]?”
- Upload 6+ lifestyle images with visible context. Show the product being used by a person, in its real environment, with scale context. Rufus’s computer vision analyzes what’s in the frame. (SellerLabs)
- Run post-purchase review campaigns asking about use cases. Use follow-up emails to ask customers specifically to mention the problem they solved or use case they applied the product to. Generic review requests produce generic, Rufus-invisible reviews. (Velocity Sellers)
- Optimize your product title for entity recognition. Include the product category noun, primary use case, and one key differentiator in your title, not keyword strings. “Commercial-Grade Stainless Steel Espresso Machine for Home Baristas” not “espresso coffee machine maker brewer premium 2026.”
- Add an Enhanced Brand Content video. Create a 30-60 second demonstration video. Rufus can’t watch video, but it analyzes video metadata and thumbnails for context signals.
- Monitor Rufus-specific metrics in Brand Analytics. Track your “Rufus appearance rate”, which keywords trigger Rufus recommendations for your products. Prioritize those keyword categories for optimization.
The principles here closely mirror the content chunking for RAG retrieval framework and the schema markup AI search approach, structured, semantically clear data outperforms keyword-dense unstructured text in every AI retrieval context, whether it’s Amazon, Google, or ChatGPT.
Rufus vs. traditional Amazon SEO: what you stop doing
Several tactics that worked under A9 actively hurt Rufus performance:
- Keyword stuffing in titles and bullets. COSMO’s semantic model penalizes unnatural language. “Organic cotton yoga pants women stretchy leggings pilates workout” reads as spam to an LLM that understands context.
- Hiding target keywords in backend fields without semantic meaning. Backend terms should complete sentences about the product’s use, not be arbitrary keyword lists.
- Ignoring the Q&A section. Many sellers treat Q&As as a support channel. Under Rufus, it’s a ranking asset. Every unanswered question is a missed citation opportunity.
- Using generic review solicitation templates. “How did you like your purchase?” generates reviews Rufus can’t parse. “What problem did this solve for you?” generates use-case evidence Rufus rewards.
The ecommerce product schema for AI post covers the cross-channel structured data strategy that underpins this optimization approach, the same semantic clarity principles apply whether you’re optimizing for Amazon Rufus, Google Shopping, or ChatGPT’s shopping agent.
Frequently Asked Questions
Does Rufus replace traditional Amazon keyword research?
How quickly do Rufus optimizations take effect?
Does Rufus affect organic Amazon rankings (not just AI results)?
Should I optimize for Rufus if I only sell on Amazon, not through Google?
Want this implemented for your brand?
I help growth-stage companies own their category in AI search. Audit your AI search visibility.