Example AI search audit
What eLLMo AI Search finds on
Higround in an AI search audit.
Higround BLACKICE keyboard. An AI search audit of what ChatGPT, Perplexity, and Gemini can read on the live product page.
higround.co
In the source audit, Higround scored 3.9 out of 10. Branded visibility was strong at about 73 percent, but unbranded visibility for the same buyer questions was only about 10 percent, because the product page gives an AI engine almost nothing to read.
Structured data
What an AI engine can confirm about this page without guessing.
No Product or AggregateRating schema on the product page
In the source audit, the BLACKICE listing carried 970 verified five-star reviews but no structured data an AI engine could read to confirm price, availability, or rating.
No FAQPage schema despite real buyer questions
Hot-swap support, switch type, and layout are common buyer questions with no structured answer block for an engine to cite.
Crawl infrastructure is in place
agents.md and UCP or MCP support already exist on the site. The gap is not access, it is what the page gives an agent to read once it arrives.
Verify it yourself
A live, unauthenticated fetch of higround.co, checked against the schema types an AI engine looks for first.
Live JSON-LD check
higround.co
- Missing
Organization
- Missing
WebSite
- Missing
Product / Offer
- Missing
AggregateRating / Review
- Missing
FAQPage
- Missing
BreadcrumbList
A direct, unauthenticated fetch of higround.co found no ld+json script tags anywhere in the returned HTML. Zero structured data of any kind at the domain root.
Can an AI crawler read this page
What the page body actually says, not what it implies with an image.
Product description is two sentences
In the source audit, the product page copy did not name the switch type, polling rate, weight, layout, plate material, or keycap profile in readable text, the exact specs a buyer or an agent needs to compare it to Keychron or Wooting.
Image alt text says only "BLACKICE"
Alt text carries no descriptive detail an engine could use to understand what the image shows.
IP collaboration context is not readable
Licensed collaborations like the Halo and Naruto keyboards are not connected to their source property in a way a language model can confirm.
Fix these
Ranked by how much each one changes whether an AI engine can cite this page.
Add Product, Offer, and AggregateRating schema
Structured price, availability, and the 970-review rating give an engine a citable, current answer instead of a guess.
Write out switch, polling, weight, layout, and keycap specs in readable copy
The same specs Keychron and Wooting already publish let an engine compare Higround directly instead of skipping it for lack of evidence.
Add FAQPage schema for hot-swap, switch type, and layout questions
These are the exact questions a buyer or an agent asks before recommending a 65 percent keyboard.
What every AI search audit ships
A scored audit, structured data fixes, and copy you can ship today.
Every audit ships a scored report, ranked schema fixes, and page copy designed to land in your engineering ticket and your content brief.
Scored visibility report
A branded and unbranded visibility score across ChatGPT, Claude, Gemini, and Perplexity, with the exact questions tested.
Ranked schema fixes
Structured data gaps ranked by how many buyer questions they unblock. Each one traces to a specific page element.
Readable page copy
Plain-text specs and answers an AI engine can quote directly. Paste into your product page or CMS.
Questions & answers
Common questions about this audit
This is a summary independent analysis by eLLMo AI, built from public data and our synthetic digital twins.
Book a demo
Same method. Your homepage. See exactly where AI engines can and cannot recommend your brand.