Home/ Blog/ SEO

Voice Search and AI Answers: Optimising for the Spoken Web

Voice queries and AI-generated answers have different structural needs than traditional typed search. Here's what actually changes about how you should write and structure your content.

Article Cover Image

Most SEO advice about voice search is either five years out of date or written by someone treating it as a minor technical tweak rather than a structural shift in how people access information. The reality is that voice search and AI-generated answers share an underlying logic that, once understood, changes how you should approach content for any channel.

The key insight is this: voice queries and AI answer engines both favour content that is written to be understood rather than to be found. Traditional SEO optimised for crawlers first and humans second. What's changed is that the models now powering search — whether Google's AI Overviews, Perplexity, or the voice responses on any modern assistant — are effectively running a comprehension test on your content before they'll use it.

How Voice Queries Actually Differ

When someone types a search query, they tend to abbreviate. "best web designer London" is a typed query. The spoken equivalent is "who's the best web designer in London for a small business" — longer, more specific, phrased as a natural question. This difference in phrasing has real implications for the content that gets surfaced.

Voice results strongly favour direct answers. When a voice assistant reads out a response, it almost always reads a single paragraph or two — a featured snippet equivalent — rather than a list of links. Your content needs to be structured so that a direct, complete answer to a likely question exists somewhere on the page, ideally within the first few sentences of a section.

A useful test: read your service pages out loud. If any sentence sounds like something a person would never say in conversation, it's probably too keyword-optimised for voice or AI comprehension. Rewrite it as you'd actually say it to a client.

What AI Answer Engines Actually Look For

AI search tools like Perplexity and Google's AI Overviews surface content differently from classic search. They're not looking for a page that has the most keyword density — they're looking for content that gives a clear, citable answer to a specific question, comes from a source that looks authoritative and consistent, and is structured in a way that makes it easy to extract discrete facts.

This has a few practical implications. First, your page headings matter more than they ever did for traditional SEO. An H2 that says "Our Services" tells an AI model very little. An H2 that says "What's included in a web design project" is answering a question — and that's exactly what AI models are trained to surface.

Second, your introductory sentences for each section need to lead with the answer, not the context. A section that starts "There are many factors to consider when choosing a web designer..." is burying the answer. A section that starts "The most important factor when choosing a web designer is whether they've worked with businesses of your size and in your industry" is giving the model something it can use.

"AI search engines are doing something closer to comprehension than matching. They're asking: does this page actually answer the question, or does it talk around it?"

Structured Data Is No Longer Optional

For voice search and AI answer engines, schema markup has moved from a nice-to-have to something that meaningfully affects whether your content gets used. The reason is straightforward: structured data gives AI models explicit, machine-readable facts about your business that they don't have to infer from prose.

For a service business, the minimum worth implementing is:

  • LocalBusiness schema — your business name, address, phone, hours, and geographic area served
  • Service schema — each of your services described explicitly, with a name, description, and price range if you publish one
  • FAQPage schema — if you have an FAQ section, marking it up properly makes it far more likely to be surfaced in AI-generated answers
  • Review or AggregateRating schema — if you have client testimonials, structured markup makes them available for AI answer snippets

None of this is technically complex. All major no-code platforms support schema injection through custom code blocks, and it takes under an hour to implement the basics for a service business site.

Writing for Conversational Queries

The practical writing change that makes the biggest difference is building question-and-answer structures into your pages. This doesn't mean a formal FAQ section on every page — it means writing content so that the headings are the questions and the paragraphs immediately following them are the answers.

A services page that has the heading "Web Design" and then three paragraphs of general description is not optimised for voice or AI. The same content rewritten as "What does a web design project with Desyn involve?" followed by a direct, specific answer — covering timeline, deliverables, and process — is much more likely to be surfaced when someone asks a voice assistant "what does it cost to get a website made" or asks Perplexity "how does a web design agency work."

The key is that the question you're answering doesn't have to be literally in the heading. The heading can be a natural title ("How we work") as long as the first sentence of the section answers the implicit question ("We run a three-stage process: discovery, build, and launch — with most projects completing in four to six weeks").

If your business serves a specific geographic area, local voice search is where the optimisation effort has the highest return. "Web designer near me," "web design agency in [city]," and "who builds Webflow sites in [city]" are all queries that are increasingly handled by voice — either through a phone assistant or a smart speaker — and they almost always surface a single result or a very short list.

To compete here, you need your Google Business Profile fully completed and actively maintained, your website to explicitly name the geographic areas you serve (in prose, not just in the page title), and consistent NAP (name, address, phone) data across every directory listing. Inconsistency between your website, your Google Business Profile, and third-party listings is the most common reason local voice results return the wrong information — or none at all.

Check what a voice assistant actually says when you ask it about your business by name. This is the fastest way to identify inconsistencies in your structured data or Business Profile. Most businesses are surprised by what they find.

The Underlying Principle

All of the changes described here flow from one principle: the shift from search engines as indexes to search engines as answer machines. When the goal was to get someone to click through to your page, having a lot of keyword-relevant content was valuable. When the goal is to be the source that an AI or voice assistant cites in its answer, clarity and structure matter far more than volume.

This doesn't mean producing less content — it means every piece of content needs a reason to exist and needs to answer a specific question clearly. A 400-word page that answers three common client questions precisely is worth more in the current landscape than a 1,500-word page that covers everything in general terms.

The web is becoming spoken as well as read. The sites that are ready for that are the ones that were already written clearly enough to be read aloud.