The alphabet · GEO

Get named in the answer.

The layer nobody else shows you: whether AI can read your site at all — and whether it says your name when your customers ask who to call.

GEO pillar four of four · 25% of your score

Generative engine optimization — being named in AI answers. It starts with access (can GPTBot and ClaudeBot even fetch your pages?), runs through entity clarity (does AI know exactly who you are?), and ends in citations: how often ChatGPT, Perplexity, and Gemini recommend you when your market asks.

See also: Local SEO · SEO · AEO · AIO

Why it matters

Three truths about GEO.

01

The answer is the new page one

Assistants return one or two names, not ten links. Being in that shortlist is a winner-take-most game — and today almost nobody knows whether they’re in it.

02

Most blocks are accidents

Firewalls, bot protection, and CDN rules silently drop AI crawlers every day. The business owner never sees it — AI simply has nothing to read, and recommends someone it can.

03

Answers shift weekly

AI answers are re-generated constantly. A citation you hold today can vanish next week — monitoring is the difference between finding out now and finding out from your sales numbers.

In your scan

What Speak Local checks.

Every scan measures these — scored, prioritized, and re-checked on schedule. See the full platform for how the pillars combine.

Crawler access — robots.txt, firewalls & CDNs actually letting AI bots in
Rendering — content in raw HTML, not locked behind JavaScript AI never runs
llms.txt & entity clarity — present, accurate, worth reading
Citation share of voice — how often AI answers name you vs. your rivals
LOCAL SEO AEO GEO AIO
GEO questions

Asked and answered.

What’s the difference between GEO and AEO?
AEO makes you quotable; GEO gets you cited. AEO is on-site craft — schema, FAQs, answer-shaped content. GEO extends off-site: whether AI crawlers can access you, whether your entity is unambiguous, and whether generative engines actually name you in answers. You need both, which is why they’re separate pillars in the same score.
How do I know if AI can read my site?
You can’t tell from a browser — you have to fetch your pages the way the bots do. Speak Local requests your site as GPTBot, ClaudeBot, and PerplexityBot from the outside and reports exactly what each one gets back, because robots.txt saying “allowed” means nothing if a firewall drops the request.
What is llms.txt?
A plain-text file at yourdomain.com/llms.txt that describes your site for language models — who you are, what you do, and which pages matter. It’s a young standard, but it’s cheap to publish, engines are starting to read it, and it’s one of the fastest fixes on most audit lists.