How Local Businesses Show Up in Google AI Overviews and AI Mode

Published 2026-09-14 · AlgoEthos

The direct answer, from Google's own documentation: to be eligible for AI Overviews and AI Mode, "a page must be indexed and eligible to be shown in Google Search with a snippet." That is the whole technical requirement. Google states plainly that "There are no additional technical requirements."

If you have been told you need a special schema, an AI-specific file, or a new markup format, the documentation contradicts it directly: "You don't need to create new machine readable files, AI text files, or markup to appear in these features. There's also no special schema.org structured data that you need to add."

That is good news and slightly deflating news at the same time. The good news is there is no secret to buy. The deflating news is that the work is ordinary SEO — done well, on a site that is genuinely useful — and ordinary work is harder to sell than a trick.

This guide separates four things that get mixed together constantly, and that mixing is where most bad advice comes from.

The four things people confuse

Almost every confused conversation about AI search collapses four separate questions into one. Keep them apart and the topic becomes manageable.

1. Eligibility — does your page meet Google's stated conditions for being able to appear? The conditions are documented, and they are the part you can configure. Meeting them is not a guarantee: Google still decides whether to crawl, index and serve any given page.
2. Inclusion — does it appear for a given question? This is not under your control, not guaranteed, and varies by query.
3. Measurement — can you tell whether it appeared? Partially, and with real limits worth knowing before you promise anyone a report.
4. Guarantees — can anyone promise placement? No. Anyone who does is selling you something they do not control.

The rest of this article takes them in that order.

1. Eligibility: the conditions you can configure

Eligibility is the part with a documented answer, so start here and finish it properly. Be clear about what "finishing it" means, though: you are removing obstacles and meeting stated conditions. Google decides whether to crawl a page, whether to index it, and whether to serve it. Nothing below buys you any of those three. What it does is stop you ruling yourself out.

Your page must be indexed. If Google has not indexed the page, nothing downstream matters. Check coverage in Search Console rather than assuming — and note that requesting indexing is a request, not an instruction.

Your page must be eligible for a snippet. This is the requirement people trip over without realising, because the controls that block snippets are the same ones some sites apply for unrelated reasons. Google names them directly: nosnippet, data-nosnippet, max-snippet, and of course noindex. These work the same way for AI features as for ordinary Search results.

These four do different jobs, and treating them as one switch is how sites rule themselves out by accident. Precisely:

• noindex — when Google processes it, the page is excluded from Google Search. That removes it from AI features too, because those require a page that is indexed and snippet-eligible. It is a Google Search directive, not a universal one; other systems have their own rules.
• nosnippet — prevents a snippet being shown for the page. The page can still be indexed. Because snippet eligibility is part of the stated requirement, this is the one most likely to exclude an otherwise healthy page.
• data-nosnippet — excludes only the selected content it wraps, not the page. Sometimes added to hide boilerplate, it can end up wrapping the part of the page that actually answers the question.
• max-snippet — sets the maximum number of characters Google may use as a text snippet. In its normal use it limits snippet length: it does not exclude the page or its content, and a restrictive value simply leaves less to work with. The exception is max-snippet:0, which Google documents as equivalent to nosnippet — a zero-character limit means no text snippet at all, which removes snippet eligibility and therefore has the same excluding effect as nosnippet rather than merely shortening the result. If you are auditing a page that will not appear, check for max-snippet:0 as carefully as you check for nosnippet; it is easy to read it as a harmless length cap. (max-snippet:-1 is the opposite: no limit.)

Worth checking on your own site today: a nosnippet applied site-wide years ago to deter scrapers, a data-nosnippet that has crept around real content, or a noindex left on a page you meant to be public.

None of those are exotic. They are ordinary directives that someone added for an ordinary reason, and their effect on AI features is rarely considered when they are set.

That is the whole of the stated technical requirement. There is no step five to add, and adding one does not improve your position. What remains after this is not more configuration — it is Google's decision to crawl, index and serve, which no setting on your site controls.

2. Inclusion: the part you influence but do not control

Meeting the eligibility conditions is something you can check. Inclusion is not. Being eligible does not mean appearing, and appearing for one question does not mean appearing for a similar one.

Since there is no AI-specific lever, what is left is Google's general guidance on helpful, people-first content. Their published self-assessment questions are a genuinely useful editing tool, and worth reading as questions about your page rather than as ranking factors:

• "Does the content provide original information, reporting, research, or analysis?"
• "Does the content provide insightful analysis or interesting information that is beyond the obvious?"
• "Does your content clearly demonstrate first-hand expertise and a depth of knowledge?"
• "After reading your content, will someone leave feeling they've learned enough about a topic?"
• "Is this the sort of page you'd want to bookmark, share with a friend, or recommend?"
• "Does the content have any easily-verified factual errors?"

Google frames the underlying test as who, how, and why. Who authored the content — is that self-evident to a visitor? How was it produced — and specifically, "Is the use of automation, including AI-generation, self-evident to visitors?" And why does it exist, which Google calls "perhaps the most important question": content should exist "primarily to help people."

For a local service business, the practical translation is unglamorous:

• Answer the actual question near the top of the page. Not after four paragraphs of positioning. If someone asks what something costs, the page should say what it costs.
• Be specific in ways only you can be. Your service area, your hours, what you actually do when a job goes wrong, what you charge. Generic copy assembled from competitors is exactly the thing the guidance above is designed to filter.
• Put first-hand experience on the page. You do this work. Most pages in your category are written by people who do not.
• Structure it so a reader can scan it. Clear headings, short paragraphs, real lists. This is good for readers first; that it also helps machines parse the page is a side effect, not the reason.

Notice what is absent from that list: any instruction to add markup, files, or technical tricks for AI. There is nothing to add, because Google says there is nothing to add.

A note on llms.txt, stated honestly

You will see advice to publish an llms.txt file. Here is exactly what can be said about it from the source cited in this article, and no more: Google's documentation states that no additional AI-specific files or markup are required to appear in these features. That settles the requirement question — it is not required.

It does not settle whether publishing one helps. This article has not established any inclusion benefit, and does not claim to have surveyed the published evidence either way. So if you choose to publish one, treat it as an optional experiment whose effect this article makes no claim about. What it is definitely not is a substitute for anything in section 1, and it should not be sold to you as a requirement, because the documentation says it is not one.

3. Your business information: the local layer

For a local business, one more thing sits underneath everything above: whether Google can tell who and where you are, consistently.

Google's guidelines for representing a business are specific. Your name "should reflect your business's real-world name, as used consistently on your storefront, website, stationery" — and names may not include marketing taglines, store codes, phone numbers, or product information. Addresses must be "a precise, accurate address and/or service area", and P.O. boxes are not acceptable. You should "Provide a phone number that connects to your individual business location", preferring a local number over a call centre, and "Provide your regular customer-facing hours of operation."

The reason this matters here is not that a profile is an AI-features ranking factor — that is not a claim Google makes and not one I will make for them. It is simpler: if your name, address, phone and hours disagree across your website, your profile, and the directories that quote you, you have made yourself harder to identify. Being hard to identify is a bad position in any system that has to decide which business to cite.

Fixing it is dull, finite, and mostly free. Do it once, then keep it current when something changes.

4. Measurement: what you can honestly report

This is where a lot of marketing goes quietly wrong, so here is the limit stated plainly.

Google reports AI-feature traffic in Search Console's Performance report under the Web search type, and traffic from sites appearing in AI features "are included in the overall search traffic in Search Console."

Read that carefully, because it decides what you can promise. AI-feature traffic is folded into your ordinary Web numbers. It is not broken out as its own line. So:

• You can see total clicks, impressions, CTR and average position for a page or query.
• You can watch those numbers move over time and notice when something changes.
• You cannot open Search Console and read a number labelled "AI Overview appearances."
• You therefore cannot honestly attribute a change in clicks specifically to AI features using Search Console alone.

Anyone who shows you a confident "AI visibility score" derived from Search Console is showing you an inference, and it should be labelled as one. There are third-party tools that sample AI responses directly; a sample is useful evidence and is still a sample, not a coverage guarantee.

The honest method is the one in section 6: observe deliberately, write down what you actually saw and when, and let the log accumulate. That is slower than a dashboard and considerably more truthful.

5. The checklist

Work top to bottom. Everything here is either documented by Google or a plain-language editing decision. Nothing here requires a purchase.

Eligibility conditions — clear these first. Clearing them does not guarantee crawling, indexing or serving; it stops you excluding yourself.

1. Is the page indexed? Confirm in Search Console, do not assume — and remember indexing is Google's decision, not a setting you hold.
2. Does the page allow snippets? Check for nosnippet (blocks the snippet), a restrictive max-snippet (shortens it), and any data-nosnippet wrapping your real content (excludes that content).
3. Is noindex absent from pages you intend to be public? It excludes the page from Google Search once processed.
4. Is the page reachable by ordinary crawling — linked from your site, present in your sitemap, not blocked in robots.txt?

Content — the part that takes actual work

1. Does the page answer its core question in the first screen, in plain words?
2. Is there something on this page that only you could have written — your process, your service area, a real constraint you have hit?
3. Is it obvious who published it and why the page exists?
4. If you used automation to help write it, is that self-evident to a visitor?
5. Are there any easily-verified factual errors? Check every number and every price.
6. Would you send this page to a customer who asked the question by phone? If not, fix it before worrying about anything else.

Business information

1. Does your business name match your real-world name, with no taglines or extras appended?
2. Do name, address, phone and hours match across your site and your business profile?
3. Is the phone number one that reaches your location?

Measurement

1. Is Search Console connected and collecting data for the right property?
2. Have you recorded a baseline before you make changes, so you have something to compare to?

6. The observation log

Because measurement has the limits described in section 4, the practical alternative is a log. This is deliberately low-tech. A spreadsheet is fine. The value is in doing it on a schedule and writing down what you actually saw, including the times you saw nothing.

Record one row per check:

Three rules that keep the log honest:

• Use the same questions every time. Changing the wording changes the result, and then you are measuring your own inconsistency.
• Record absence. A month where you were not cited is a real observation, not a failed check.
• Never convert the log into a percentage or a score. It is a sample of a system that varies by user, location and time. Treat it as a narrative record, not a metric.

Over six months this log will tell you more that is true than any dashboard will, precisely because it does not pretend to more precision than the underlying reality has.

7. What nobody can promise you

Four things deserve saying directly, because they are the substance of most bad pitches:

• No one can guarantee you appear in an AI Overview. Not an agency, not a tool, not us. Eligibility is documented; inclusion is not promised anywhere by Google.
• No one can sell you special AI markup, because Google states none is needed.
• No one can show you a clean AI-attributed traffic number from Search Console, because that traffic is folded into Web.
• Anyone quoting you a ranking guarantee for AI answers is describing something they do not control. That is true for us too, which is why we do not offer one.

What can honestly be promised is the work in sections 1, 2, 3 and 5, done properly, and an honest record of what happened afterwards.

Where AlgoEthos fits

Our AI Visibility service is this work, done monthly by people, with plain-English reporting on what actually changed. If you would rather run the checklist yourself, run it — everything above is public, and nothing in it requires buying anything from us. If you want the ongoing version, with someone watching it as your business and the surfaces change, that is what the service is.

If you want to understand what your current numbers actually say before changing anything, our AI Research & Analytics lane starts there instead.

Next step: book a free walkthrough and we will run the eligibility half of the checklist against your site with you on the call. It takes a few minutes and it either finds something or it does not — and if it does not, we will tell you that.

Related reading on this site

• AI Visibility — the ongoing service
• AI Research & Analytics — understanding your numbers
• AI for Local Business — the practical overview
• Contact — book the walkthrough

Sources

All checked 12 September 2026. Google updates this documentation; re-check before relying on it.

• Google Search Central — AI features and your website — eligibility requirement, "no additional technical requirements", no special schema or AI files, snippet controls, Search Console reporting under the Web search type.
• Google Search Central — Creating helpful, reliable, people-first content — self-assessment questions, the who/how/why framework, disclosure of automation.
• Google Business Profile — Guidelines for representing your business on Google — business name, address, phone and hours requirements.