Global Mechanical Keyboard Brand
Consumer electronics / mechanical keyboards
- Website type
- DTC-style e-commerce / consumer electronics
- Buyer query language
- English buyer queries
- Audit type
- Anonymised public-brand AI visibility audit
Executive Summary
A global mechanical keyboard brand showed uneven AI visibility across platforms. ChatGPT surfaced the brand more often, while Gemini showed very low owned-domain citation visibility in this run. The audit identified opportunities to strengthen official-site citation signals and comparison-ready buying guidance.
Website crawl signals were limited for this sample, so this report focuses primarily on AI recommendation visibility and owned-domain citation patterns.
Want to see how AI understands your brand?
Check if AI recommends your brandCitation Metrics
This measures how often AI responses cited or surfaced the brand's own website. A brand may still be mentioned through third-party sources.
Prompt Themes Tested
- —Best mechanical keyboards for Mac users
- —Best wireless mechanical keyboards for productivity
- —Best budget mechanical keyboards under $100
- —Mechanical keyboard comparison prompts
- —Hot-swappable keyboard recommendations
- —Compact and travel keyboard prompts
- —Gaming keyboard alternatives
- —Mechanical keyboard buying guides by use case
- —Is this brand worth buying?
Platform Breakdown
“What is the best mechanical keyboard for Mac users who switch between work and gaming?”
Key Findings
ChatGPT cites this brand on around 43% of relevant queries — better than most — but Gemini cites it 0% of the time. Claude is inconsistent at 13%. The gap between platforms is a structural signal problem, not a brand recognition problem: the site has minimal schema markup and limited AI-readable content of the type that Gemini and Claude weight most heavily.
Minimal structured data and an incomplete set of AI-readable signals. The brand's web presence is crawlable, but there are few explicit structured signals to help models understand what it sells, who it is for, or what makes it different.
Competitor Citation Patterns
AI assistants default to editorial review sources when brand-owned content lacks clear comparison and recommendation structure. Creating on-domain buying guides and "best for" content can shift citations toward the official site.
Pages that directly answer "best for X" questions outperform product pages that lead with specs. Structuring key pages around use-case recommendations rather than feature lists is more likely to generate owned-domain citations.
Structured FAQ markup makes it easier for Gemini and Claude to extract clear answers about product suitability, pricing, and use cases — reducing reliance on third-party sources for that information.
Priority Fixes
Create "best for" buying guides by user type
- Why it matters
- AI assistants answer buying-intent queries by surfacing the most comparison-ready content available. Without explicit use-case guidance on the official domain, AI defaults to citing editorial review sites instead.
- Where to apply
- Dedicated buying guide pages, collection pages, key product pages
- Expected impact
- Higher owned-domain citation rate on Mac, productivity and gaming keyboard queries across ChatGPT, Gemini and Claude.
Add model-comparison FAQ content
- Why it matters
- Common decision questions — "Which model for a compact layout?", "Which keyboard is best for hot-swap switches?" — are currently unanswered on the official domain. AI assistants cite sources that answer these questions directly.
- Where to apply
- FAQ pages, product comparison pages, category landing pages
- Expected impact
- Broader query coverage and more consistent citations across model-selection and comparison prompts.
Add XML sitemap and reference in robots.txt
- Why it matters
- Without a sitemap, AI crawlers may miss key product, collection and guide pages — reducing the total surface area available for citation.
- Where to apply
- Domain root + robots.txt Sitemap directive
- Expected impact
- More complete AI crawler discovery of buying guide and product pages.
Implement Product and FAQ schema markup
- Why it matters
- Structured data helps Gemini and Claude extract specific product attributes, pricing ranges and FAQ answers — the types of information they need to confidently recommend a brand.
- Where to apply
- Key product pages, collection pages, FAQ sections
- Expected impact
- Improved citation consistency on Gemini and Claude, which weight structured data more heavily than ChatGPT.
Strengthen internal linking between use-case guides and product pages
- Why it matters
- AI crawlers follow link signals to understand content relationships. Linking "best for Mac users" guides to specific product pages helps models understand which products match which use cases.
- Where to apply
- Buying guide pages, collection pages, homepage
- Expected impact
- More coherent brand representation in AI-generated product recommendations.
Future-proofing (low-cost, uncertain impact)
These recommendations are low-cost to implement but the payoff is currently unverified. Major LLM providers have not publicly confirmed they use llms.txt. We include it because the cost-to-implement is near zero and being early to an emerging standard has historical value. We do not count llms.txt in your visibility score.
Create and publish /llms.txt
- Why it matters
- An llms.txt file tells AI crawlers exactly who the brand is, what it sells, and which pages matter most — without requiring the model to interpret the full site from scratch.
- Where to apply
- Domain root (yourdomain.com/llms.txt)
- Expected impact
- If LLM providers adopt llms.txt as a retrieval signal (currently unconfirmed), brands with the file may surface faster. Low-cost insurance, not a guaranteed lift.
Want to see how AI understands your brand?
Check if AI recommends your brandIssues Found
Low AI citation rate
The brand is cited by ChatGPT on some queries but largely absent from Gemini and inconsistent on Claude. Adding schema markup, FAQ content, and an llms.txt file creates structured signals that all three AI platforms can use to identify and recommend the brand consistently.
Missing llms.txt
Create a /llms.txt file at your domain root. This file helps AI crawlers quickly understand who your brand is, what you sell, and what pages matter most — reducing reliance on indirect signals.
Missing XML sitemap
Add an XML sitemap and reference it in robots.txt. This ensures AI crawlers can discover all your key pages, not just those linked from the homepage.
Rewrite Suggestions
“Our keyboard supports wireless and wired modes with multiple layout options.”
“Best for Mac and Windows users who want one mechanical keyboard for both productivity and desk setup flexibility. This model suits people who switch between devices, prefer hot-swappable switches and want a compact layout without losing essential shortcut keys.”
“Explore our range of mechanical keyboards.”
“Find the right mechanical keyboard for your setup — whether you work from a Mac, game on a PC, prefer compact travel-friendly layouts, or want hot-swappable switches for easy customisation. Browse by use case or switch type.”
“Which keyboard is right for me?”
“Which mechanical keyboard is best for Mac users? For Mac users who switch between work and creative tasks, we recommend keyboards with macOS-compatible layouts, USB-C connectivity and multi-device pairing. Models with dedicated Mac keycaps and Function-row shortcuts tend to perform best in productivity workflows.”
30-Day Action Roadmap
- ·Create and publish /llms.txt summarising brand, product range and key pages
- ·Generate and submit an XML sitemap; add Sitemap directive to robots.txt
- ·Verify GPTBot, ClaudeBot and GoogleOther are allowed in robots.txt
- ·Draft "best for" buying guide pages for: Mac users, productivity, gaming, compact layouts
- ·Add a model-comparison FAQ page answering the top 8–10 purchase-decision questions
- ·Add hot-swap and wireless use-case explanations to relevant product pages
- ·Implement FAQ schema markup on the new FAQ page and key product pages
- ·Add Product schema markup (name, description, category, price range) to top products
- ·Add Organization schema to homepage with brand description and sameAs links
- ·Add internal links from buying guides to relevant product pages
- ·Cross-link "best for" sections across collection and product pages
- ·Review and update page meta titles and descriptions for buying-intent alignment
Strengthen comparison-ready buying guides and model-selection content.
Create clearer "best for" content by use case, such as Mac users, productivity, compact layouts, hot-swappable switches and wireless desk setups.