What is Answer Engine Optimisation — and Why London Businesses Can't Ignore It

Let's start with a scenario you've probably lived

You're driving through Islington, hands on the wheel, and you need a coffee. You ask your phone: "Find me a good coffee shop near Angel." Your phone responds with a name. One name. You either go there, or you don't bother.

That business didn't get lucky. It didn't just have a nice Instagram. It earned that position through deliberate, structured optimisation for exactly this kind of moment. That's Answer Engine Optimisation — and most London businesses are leaving it entirely to chance, wondering why the phone isn't ringing.

To be clear: we're not saying voice search is going to replace Google. It's not. But "it won't replace Google" does a lot of work as a reason not to act. Voice doesn't need to replace anything — it just needs to be the channel where one customer found your competitor instead of you. That's happening now. Most businesses haven't noticed yet.

What AEO actually is (without the jargon)

Answer Engine Optimisation (AEO) is the practice of structuring your content, schema markup, and local citations so that voice assistants — Siri, Alexa, and Google Assistant — choose your business as the spoken answer to a relevant query.

SEO gets you onto a list. AEO makes you the answer. The gap between those two outcomes is wider than it sounds.

When someone types "electrician North London" into Google, they get options. They browse. They compare. When they ask Alexa the same thing with their fuse box sparking, Alexa reads out one name and they call it. There's no browsing. No comparison. The electrician who did their AEO gets the call. The others get nothing — and no way of knowing they were ever close.

(Why did the electrician win? Because they were a live wire on the digital front. We'll get our coats.)

How voice search is different from typing

The difference isn't just that your mouth moves. The queries themselves are structurally different — and that matters for how you write and optimise.

When people type, they abbreviate. "Italian restaurant EC1." When they speak, they don't. "What's a good Italian restaurant near Farringdon that's open on a Monday evening?" Voice queries are longer, more conversational, and far more specific. People also assume their assistant knows where they are — so they ask it like they'd ask a friend, not like they're feeding a search bar.

The content that wins voice answers looks different from content that ranks well in traditional search. It has to be direct, plainly written, and structured to answer an actual question — not to include the right keywords at the right density. A page stuffed with "Italian restaurant London" twenty times won't win anything. A clearly written paragraph that says "We're a family-run Italian restaurant in Farringdon, open every day including Monday evenings" might end up being exactly what Siri reads aloud.

Format matters here too. Voice assistants pull heavily from FAQ-structured content — a question, then a direct answer, nothing else. If your site doesn't have that structure, you're making it difficult for Siri or Alexa to select you. They're not being picky; they just need clear signals. Most websites don't give them any.

Why this matters specifically for London businesses

London is a particular beneficiary of AEO investment — and not just because there are more people here. A few factors make the London market unusually well-suited to voice search:

Commuters ask questions hands-free. London has one of the longest average commute times of any city in Europe. Whether you're on the Overground or stuck behind a lorry on the North Circular, voice queries happen during commutes at high rates. Your future customer is asking Siri about your category right now, probably from a vehicle or a packed Elizabeth line carriage.

Density makes "near me" queries intensely competitive. In most London boroughs, five or six businesses in your category are within walking distance. When a customer asks for a recommendation, they're not aware of all of them — they're aware of whichever one the voice assistant mentions. Being in that position requires AEO. Having a nice website doesn't.

The competition for voice is still thin. This is the striking thing. For all the competition in London's local search market, almost none of it has extended to AEO. Most businesses have done some SEO. Very few have done AEO. The gap between the two is your opportunity window — and it won't stay open indefinitely.

What AEO actually involves — in plain English

AEO isn't one thing you fix and move on from. It's a set of workstreams that build on each other, and they matter in roughly this order:

1. Conversational content structure. Your pages need to answer real questions in plain English. Not "We offer premium solutions for your drainage requirements." But "We're plumbers based in Hackney and we handle emergency call-outs the same day, seven days a week." Alexa doesn't speak marketing; neither do your customers.

2. FAQ sections built for extraction. Voice assistants actively look for FAQ-formatted content because it's the easiest thing to convert into a spoken answer. If your site doesn't have clearly formatted questions and direct answers, you're not in the running.

3. Speakable schema markup. Google's Speakable schema is a piece of structured data that tells voice platforms which sections of your page are suitable to be read aloud. Without it, even genuinely good content gets passed over — not because it isn't useful, but because nothing signalled that it was there. It's a small technical step most businesses skip entirely, and one of the clearer advantages still available right now.

4. Featured snippet capture. Google Assistant draws primarily from featured snippets — the highlighted box at the top of a search result page, above all the other links. Winning featured snippets for your key local queries is the single most reliable path to becoming the voice answer for those same queries. If you're in position zero on Google, you're probably the voice answer too.

5. Local signal strength. Voice searches for local businesses weigh Google Business Profile completeness and local citation consistency very heavily. A fully filled-out GBP, consistent NAP (name, address, phone) data across directories, and genuine reviews are the foundation that everything else sits on. If this isn't right, nothing above it works well.

6. Platform coverage. Siri and Alexa use Bing. Google Assistant uses Google. Different weighting signals, different optimisation priorities. A proper AEO strategy covers all three — because your customers use all three, and you don't get to choose which assistant they own.

How long before you see results?

We won't tell you AEO will fix everything by Tuesday. It won't. But for most London businesses targeting specific local queries, meaningful movement in featured snippets happens within 6–10 weeks of proper implementation. Voice citation frequency tends to follow in the same window.

Then it compounds. The business that wins the voice answer for "best accountant in Angel" in June is very likely still winning it in December — because the competitors who haven't done AEO still haven't done it, and anyone who starts later is climbing from zero while you're already sitting at the top.

My dad used to say: "The best time to plant a tree was twenty years ago. The second best time is now." He was talking about his garden. It applies here too. And unlike his garden, this doesn't involve standing in the rain on a Sunday afternoon with a spade you can't find.