Voice Commerce Is Back. And It Is About Your Q&A Schema, Not Your Skill.
Voice commerce is back in 2026, and the surface that wins is your Q&A schema. Nobody downloads the voice app. Here is what to ship.
A shopper at the hob asks her phone whether your pan works on induction. The assistant answers out loud from whatever Q&A markup it finds. If your page has none, it names another brand. The voice app you shipped in 2018 never comes up.
Voice commerce had its first wave around 2017-2019. Alexa skills, Google Actions, every DTC brand shipping a "voice app" that almost nobody opened twice. The wave broke on one wrong assumption. Shoppers were never going to install a brand-specific voice app. They just wanted the assistant they already use to know about your products.
In this article
In 2026 voice is back, on different rails. Spoken questions about your catalogue now go to ChatGPT Voice, Claude Voice, Gemini Live or upgraded Siri. None needs a brand-specific app. The winning surface is your Q&A schema.
Why will this wave not break like 2018 did?
Three differences from the 2018 wave.
- Voice now runs through general LLM assistants. No brand-specific app to install, so zero adoption friction.
- Latency dropped below the conversational threshold. 2026 voice interaction is sub-300ms end-to-end; 2018 was 1.5-2 seconds.
- Multimodal context. The assistant knows the user is looking at their phone, can see what is on screen, and can blend visual + voice in the same query.
Put together, that opens a kind of interaction that simply did not exist in 2018. A shopper stands in front of a wardrobe, asks their phone "what should I wear for a 12-degree run later", gets a recommendation, and orders the missing layer, all spoken, in about 40 seconds. No app, no wake-word they had to learn, no friction. The same retrieval machinery sits behind typed AI shopping, which we map in the answer engine optimisation playbook.
Voice commerce, first wave and second
2017-2019
- Brand-specific voice apps and skills
- Shoppers had to install them
- 1.5-2 seconds per interaction
- Voice only
2026
- General LLM assistants: ChatGPT Voice, Gemini Live, Siri
- Nothing to install
- Sub-300ms end-to-end
- Voice blended with what is on screen
Where does the assistant read your product data?
Voice assistants do not "have" your product catalogue. They retrieve it on demand from the web, the same way text-based AI agents do. The retrieval favours:
- 1Q&A schema (QAPage), read aloud almost verbatim.
- 2FAQ schema (FAQPage), read aloud with light paraphrasing.
- 3Product attribute tables, referenced for specific spec questions.
- 4AI-summarised review blocks, quoted to convey "what shoppers say".
- 5Aggregate ratings, read with the count and average.
Notice what is missing from that list: long-form descriptions, marketing copy, video captions, hero imagery. Voice strips everything visual and reads back the structured, machine-readable text. A PDP that is 80% beautiful imagery and 20% structured data has, to a voice assistant, almost nothing to say. Verified reviews carry extra weight here, for the reason we set out in how engines weight verified reviews.
| Surface | Voice treatment |
|---|---|
| QAPage (Q&A schema) | Read aloud almost verbatim. Highest-fidelity surface. |
| FAQPage schema | Read aloud with light paraphrasing. |
| Product attribute table | Referenced for spec questions (size, material, weight). |
| AggregateRating | Read with the count and average score. |
| Long-form description / marketing copy | Largely skipped. Not structured enough to quote. |
| Hero imagery / video captions | Ignored. Voice strips the visual layer entirely. |
How do I optimise a PDP for voice?
Make every answer voice-friendly
Read each FAQ answer aloud. If it sounds like a marketing brochure when spoken, rewrite. If it contains acronyms a voice assistant would mispronounce ("EPDM", "GSM"), expand them. If it is longer than 30 spoken seconds, split it.
Front-load the answer
Voice assistants quote the first 1-2 sentences and skip the rest. Get the answer in the first sentence. Reserve elaboration for sentences 2-3.
Use numerals, not spelled-out numbers
"14 days" reads better aloud than "fourteen days", most voice TTS engines render numerals correctly while spelled-out numbers occasionally trip them up.
Pronunciation overrides
If your brand name or any key product name has an unusual pronunciation, ship a pronunciation hint via the speech-to-text x-pronunciation header. Idukki, for example, would emit a hint that the second syllable is stressed.
What not to build
Three things teams get tempted to build that they should skip:
- A brand-specific voice app. Same reason it failed in 2018; nobody installs it.
- A custom wake-word. Adoption is a non-starter; users say "Hey ChatGPT" or "Hey Siri", not "Hey BrandName".
- An on-device voice assistant. Heavy engineering for a feature the OS-level assistants do better.
Measurable impact
Voice referrals sit at 1-3% of AI-engine referrals on mid-market stores today. Small, but compounding 30-40% quarter-on-quarter through 2026. Brands that did the voice-friendly Q&A work early are seeing those sessions convert at 1.5-2x the rate of typed-AI sessions, probably because a shopper who has spoken the question out loud has already half-committed by the time they reach the PDP.
Closing
Voice commerce in 2026 is not a team to hire against. It is a property of well-structured Q&A and FAQ content. If you have already done the AEO work on schema, you are most of the way to a voice-friendly catalogue. What remains is half a week of editorial polish: read your answers aloud and fix the ones that sound like a brochure.
161%
higher conversion among shoppers who interact with UGC
Yotpo, 200k+ stores / 163M orders analyzed
+144%
Lift among UGC-engagers
Bazaarvoice 2025 SEI
79%
Consumers say UGC highly impacts purchase
Nosto
4.1x
video reviews convert vs text-only
PowerReviews, 2023 baseline
Sources & notes
- 1Bazaarvoice, 2025 Shopper Experience Index · +144% conversion / +162% RPV among UGC-engagers; +354% conversion on PDPs with reviews vs without.
- 2PowerReviews, How UGC Impacts Conversion (2023) · Video reviews convert 4.1x better than text-only; photo reviews 2.6x; +103.9% lift among photo + video UGC interactors.
- 3Nosto, Consumer UGC research · 79% of consumers say UGC highly influences purchase decisions; UGC rated 2.4x more trustworthy than brand-produced content.
- 4Schema.org, QAPage + FAQPage · Structured-data vocabulary for question-and-answer and FAQ content that voice assistants retrieve and read aloud.
- 5BrightLocal, Consumer Review Survey 2024 · 88% of consumers look at reviews before purchase; 49% trust online reviews as much as personal recommendations.
Continue reading
2 pieces in this clusterThese long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.
- Agentic commerce
The 12 JSON-LD Shapes Agents Actually Quote (And the 4 You Can Skip)
AI agents quote about twelve schema.org shapes: Product + Offer, Review/Rating, and FAQ/QA do most of the work. Here is what to ship, what to skip, and the order.
- Conversational commerce
From FAQ Page to Chat Thread: The Migration Playbook with Timings
The static FAQ page is quietly dying. This is the week-by-week playbook for moving it to a conversational thread without bleeding the SEO equity it spent years earning.
More from Rohin Aggarwal
- Conversational commerce
Why we built the Conversational PDP
A Conversational PDP answers the silent question behind most product-page exits. Curated Q&A covers the common doubts, and an AI concierge the long tail.
- Conversational commerce
Anatomy of a Conversational PDP: The 9 Components Every Shop Needs by Q3
A conversational PDP needs nine parts: evidence-first hero, quick answers, attribute table, CTA, UGC rail, AI review summary, Q&A, sizing and policy block.
- Conversational commerce
The Future Trends of Conversational Commerce
Ten conversational-commerce forecasts through 2028: branded agent personalities, multimodal storefronts, disappearing checkout buttons, discovery moving off-site.