Voice Search: What Google’s Documentation Says

Voice search is queries asked by voice and answers an assistant reads aloud. The popular advice “optimize for voice separately” is not confirmed by Google’s documentation: there are no separate rules for voice, and the only voice feature described, in the help page on speakable markup, is in beta and works for news content in English for users in the U.S. Below: what is known from the documentation, what belongs to practice, and why advice about “FAQPage” and “snippets are the voice answer” cannot be treated as facts.

What the documentation says

Google’s documentation has no section on “how to optimize for voice search”. The ordinary principles apply: pages must be crawlable, content helpful, data accurate. The starter guide (SEO starter guide) notes that Google’s language matching systems can understand how a page relates to many queries even if it does not contain the exact terms. That removes the need to “guess” every wording, including conversational ones (keywords on a page).

Snippets: you cannot “mark” a page

The popular claim “voice answers come from featured snippets” is not confirmed by the documentation. What the help page on featured snippets says: they are special boxes where the descriptive snippet is shown first; you cannot mark your page as a featured snippet — Google’s systems decide whether a page would make a good one and, if so, elevate it. You can opt out with the nosnippet and max-snippet rules. Clicking a featured snippet takes the user directly to the section of the page that was shown, without additional markup. The help page does not describe any link to voice answers. The practical conclusion does not change: a short, clear answer under a heading is good practice for readers, but not a “technology for getting into voice” (headings and structure).

Speakable: the only voice markup

The schema.org speakable property identifies sections of an article or page best suited for audio playback using text-to-speech. Per the help page, it lets search engines and other applications identify content to read aloud on Google Assistant-enabled devices; the Assistant uses it to answer topical news queries on smart speakers: it returns up to three articles and reads the marked sections aloud, attributing the source and sending the full article URL to the user’s mobile device.

• Beta: requirements may change.
• Availability: for users in the U.S. with Google Home devices set to English, and for publishers who publish content in English.
• What it is for: news queries; for news content to be eligible as answers, you need the markup and to follow the guidelines.
• What to mark up: key points rather than the whole article; around 20–30 seconds of audio per section, roughly two to three sentences, is recommended.
• What not to mark up: datelines, photo captions, source attributions — they sound confusing in voice-only situations.
• How to specify: via cssSelector or xPath (one or the other).

For other languages and regions the help page promises nothing. More on markup is in the lesson on structured data, and on the news format in the lesson on News SEO.

About FAQPage

Advice like “add FAQPage to get into voice answers” is not confirmed by the documentation: the help page on the FAQ rich result restricted its display in September 2023 and announced its deprecation on 7 May 2026. A question-and-answer block on a page remains useful to readers, but not as markup for voice.

What remains practice

• Conversational wording. People speak longer than they type; phrases like “how…”, “where…”, “when…” are common, but that is an observation of authors, not Google data.
• Brief, direct answers at the start of a section are useful both to readers and to anyone who will quote the page.
• Local queries (“near me”): the answer is local results, which are based on relevance, distance and prominence (help page, local SEO basics, Google Business Profile).
• The mobile version: most voice queries are asked from a phone, but that is an assumption; in any case indexing uses the mobile version (mobile-first).

How to measure

We did not find a separate “voice queries” indicator in the Search Console documentation, so the effect of “voice optimization” cannot be assessed from Google’s data. You can watch question-form queries in the Performance report and the pages that get impressions for them, but that is not voice, only a similar wording.

Checklist

1. Pages are crawlable, fast and clear on mobile devices.
2. Important questions are handled under separate headings, with the answer given at once and to the point.
3. For a local business, the profile is filled in and current.
4. For English-language news in the U.S., speakable markup is added if needed: two to three sentences, without datelines and captions.
5. Decisions do not rest on the claims “voice takes answers from featured snippets” and “FAQPage gives a voice answer”.

Mistakes

• Assuming voice search has its own documented ranking rules.
• Adding FAQPage for the sake of “voice”.
• Marking up a whole article or photo captions as speakable.
• Expecting speakable to be used outside the U.S. and English.
• Believing a page can be “marked” as a featured snippet.

What next

Next comes News SEO and Google News: how to get into news features and how that relates to markup and publisher requirements.