How Cycling and Carbon Wheel Stores Get Recommended by ChatGPT and AI Search (2026)
The hardest vertical we measured: a carbon-wheel maker cited 0 of 8. Gear reviewers own 'best wheelset' — the winnable ground is specification and compatibility queries.

Short answer: Cycling is the hardest vertical we've measured. We tested a carbon wheel manufacturer across two buying queries on four AI engines — eight engine-query pairs — and it was cited in zero. Every answer went to a small group of gear-review publishers and a fixed set of established brands. If you sell cycling components, you should plan around that reality rather than against it: the winnable ground is specification-level and long-tail, not "best wheelset."
We tested 2 buying queries across 4 engines. The manufacturer scored 0 of 8.
Run in June 2026 against a carbon wheel manufacturer with its own product blog.
| Query | ChatGPT | Gemini | Google AI | Perplexity |
|---|---|---|---|---|
| best carbon wheelset for climbing and racing | ✗ | ✗ | ⚠️ appeared as a Shopping card, absent from AI Overview text | ✗ |
| best carbon wheelset for triathlon racing | ✗ | ✗ | ✗ | ✗ |
Honest denominator: 0 of 8. The one near-miss is instructive — on Google, a product appeared in the Shopping panel while the AI Overview named Roval, Zipp and Bontrager instead. Being in the shopping results is not being in the answer.
Who won instead:
| Source type | Domains |
|---|---|
| Gear-review editorial | In The Know Cycling (4 of 8), CyclingNews (4), CyclingWeekly (3), 220Triathlon (3), GranFondo (2), BikeRumor, Slowtwitch |
| Established brands | Zipp, Specialized/Roval, DT Swiss, ENVE, Shimano, HED, FFWD, Bontrager, Hunt, Elitewheels |
| Forums | Reddit, Slowtwitch forum |
Notably, the manufacturer had published its own guides targeting these exact queries. They were not cited by any engine.
Why cycling is this hard
A handful of reviewers own the recommendation layer. In The Know Cycling appeared in half of all engine-query pairs. These sites do instrumented, repeated testing over years, and engines treat them as the authority for "best X" questions. A manufacturer's own guide recommending its own wheels is, structurally, a worse source — and engines behave as if they know that.
The named brands are named because they're benchmarks. Zipp 353, Roval Alpinist, ENVE SES are the reference points reviewers compare against. They get cited as a by-product of being the comparison set, not because their product pages are better structured.
Self-recommendation is a weak signal. This is the uncomfortable part. Content that says "our wheels are the best climbing wheels" competes against independent testing, and loses. That's not a structured-data problem and no amount of schema fixes it.
Compare with gemstones, where we measured stores winning 8 of 8 queries. The difference isn't merchant effort — it's whether an independent review establishment exists in the category. In cycling it does; in gemstones it doesn't.
What is actually winnable here
Given the above, three realistic plays:
Specification questions, not recommendation questions. "What rim depth for crosswinds," "carbon spoke vs steel spoke," "internal rim width for 32mm tyres." These have factual answers a manufacturer genuinely holds, and no reviewer owns them.
OEM and B2B queries. If you manufacture for other brands, "carbon rim OEM manufacturer," "custom wheel builder minimum order" are queries with almost no editorial competition.
Getting into the reviewers' comparison set. Long, unglamorous, and the highest-leverage move available. Being tested by In The Know Cycling matters more to your AI visibility than anything on your own site — because that's the domain the engines actually cite.
The product data cycling stores are missing
| Field | Why it matters |
|---|---|
| Rim depth, internal and external width | The three numbers every wheel comparison turns on. |
| Weight — rim, wheelset, and whether it includes tape/valves | Weight claims are compared obsessively and inconsistently stated. |
| Carbon grade (T700/T800/T1000) and layup | Differentiates price tiers; usually marketing prose. |
| Brake type (disc/rim), hub standard, freehub compatibility | Hard compatibility filters — get these wrong and the sale fails. |
| Max tyre width and tubeless readiness | Frequent buyer question. |
| Rider weight limit | Safety-relevant and frequently absent. |
| Spoke count and type | Relevant to durability and repairability. |
| Frame size ↔ rider height for complete bikes | The primary fit question. |
Compatibility fields are the most valuable here. "Will this fit my bike" is the highest-frequency pre-purchase question in the category, and it's answerable entirely from structured data.
What a well-structured wheelset product page looks like
{
"materials": ["T800 carbon fibre"],
"dimensions": { "rim_depth": 40, "internal_width": 21, "external_width": 28, "unit": "mm" },
"weight": { "value": 1420, "unit": "g" },
"compatibility": ["disc brake", "centerlock", "shimano HG freehub", "tubeless ready"],
"use_cases": ["climbing", "all-round road racing"],
"max_tyre_width": { "value": 32, "unit": "mm" },
"rider_weight_limit": { "value": 110, "unit": "kg" }
}
An engine answering "tubeless-ready 40mm disc wheelset under 1500g for a Shimano drivetrain" can satisfy every clause from this record — and crucially, that's a query no reviewer article answers precisely.
Note: illustrative target structure for the category, not a capture from a live store. We hold citation data for this vertical but not structured attribute data.
Schema and structured data that matters for cycling
Product with additionalProperty for every dimension and compatibility field. This category is pure specification; each spec should be an explicit PropertyValue with a unit.
isCompatibleWith / compatibility as structured values. Freehub standard, brake type and axle spec are hard filters. Publishing them as text in a table is better than nothing; publishing them as data is better still.
Weight stated with what's included. "1420g" meaning different things across brands is a known category problem. State the inclusion basis.
Organization schema with sameAs — especially for OEM manufacturers, where brand recognition is low and entity confusion is high.
Don't bury the spec table in a tab. Collapsed spec panels are common in this category and frequently invisible to crawlers.
How to check whether AI mentions your cycling store
- Ask ChatGPT, Gemini, Google AI Mode and Perplexity your category's "best X" queries — and expect to lose them.
- Then ask five specification questions only you can answer precisely. That's where the realistic opening is.
- Record which review publishers recur. Those are your actual competitors for the citation, and potentially your outreach list.
- Repeat after a week.
FoundGPT runs this across four engines and tracks drift. The free tier includes visibility checks and a readiness audit.
FAQ
We publish detailed guides. Why aren't we cited?
We tested a manufacturer that had published guides targeting these exact queries and it scored zero across eight engine-query pairs. On recommendation questions, engines prefer independent testing over manufacturer content — a structural preference, not a quality judgement.
Does appearing in Google Shopping help?
Not directly for AI citation. We observed a product in the Shopping panel while the AI Overview cited three other brands. They're separate surfaces with separate selection logic.
What's the highest-leverage thing we can do?
Get reviewed by the publications that keep appearing. In our test, In The Know Cycling was cited in half of all engine-query pairs. Their assessment of your product reaches engines more reliably than your own page does.
Is structured data pointless here, then?
No — it's just aimed at a different query class. Compatibility and specification queries are winnable and common. "Best wheelset" isn't.
Method and date
Engines tested: ChatGPT, Gemini (2.5 Flash), Google AI Mode, Perplexity. Date: June 2026. Queries: 2 non-brand buying queries. A separate brand-recognition query is excluded as it doesn't reflect discovery. Runs: one run per query per engine. Denominator: 2 queries × 4 engines = 8 engine-query pairs; manufacturer cited in 0. Known limitations: two queries is a small sample and single-run results drift. The zero result is consistent across all four engines, which raises confidence, but this remains directional. Product data: none held for this vertical; structure shown is an illustrative target, labelled as such. Note: different engine set and date to our July tests; not directly comparable across pages.
About the author
Rahul — Founder, FoundGPT
Rahul built FoundGPT and personally ran the multi-engine visibility tests behind this page. Across 111 Shopify stores he has run 23,000+ real AI-search checks on ChatGPT, Gemini, Google AI Mode and Perplexity, and applied ~99,000 structured-data fixes.