Leonardo Ribeiro's blog

Google’s AI Search Guide, in Plain Language for Small Business Owners

Google’s May 2026 guide says AI answers still come from ordinary Search. Clarity beats a special AI trick.

6 min read

A web browser with Google search open with input field filled with the word “SEO”. This is a hand drawn drawing made with black pen on paper. Image is full black and white with full white background.

A new official page, not a new shortcut

A lot of owners now watch a customer type a question into Google and get an AI answer before anyone clicks a site. The worry is practical: if the answer already names a competitor, or skips you, did the rules of the web just change?

On May 15, 2026, Google published an official page, Optimizing your website for generative AI features on Google Search. Semrush’s write-up is a useful summary of what that page says, and of what it refuses to say. This post is for owners, not for people who live inside ranking debates.

The lesson is early and plain. Google says AI Overviews and AI Mode still draw from the same Search index and the same quality systems as ordinary results. They are not a second internet with a secret door.

The tradeoff is time. Chasing a special “AI SEO” trick costs hours you could spend making the offer and the page clearer. A clearer page helps a person decide. It also gives search systems something they can understand. A trick that only exists to impress a model usually does neither.

What “still SEO” actually means for a small site

Retrieval, in owner language, is simple. The AI answer can only highlight pages Google already finds, understands, and trusts enough to rank. If the page is missing, blocked, or so vague that a person cannot tell what you sell, the model has nothing solid to point at.

The guide points back to basics, not to a new stack of software. A page Google can crawl. A clear topic. Content that matches what the customer actually asked. That is the workflow: be findable, be specific, be useful.

This is also a customer-quality issue. A page that names who you serve and what done looks like is easier for people to use. It is easier for search systems too, because the meaning is on the page instead of implied. “We help local clinics” is weaker than “We set up appointment reminders for dental clinics in Belo Horizonte, and done means the front desk stops copying the same message by hand.”

There is a limit, and no honest number belongs here unless you measure your own site. Being indexed is not the same as being chosen. No tool can promise a mention in an AI answer. If a vendor offers that promise, treat it as a sales line, not as a lesson from Google.

Four things Google says you can stop doing

The myth-busting section is the part most small sites can use this week. Google is telling people to ignore four habits that look technical and mostly add maintenance.

llms.txt. Google may see the file. The guide says it gets no special path into AI answers. Other tools might use a file like that. That is a separate choice, not a Google requirement. Do not treat a text file in the root of the site as the work.

Content chunking. You do not need to slice one article into tiny pieces so an AI can “find” a sentence. Write a clear page. Google says its systems can pull the relevant passage from a page that covers more than one point. Breaking a good explanation into fragments often makes it worse for the owner who has to keep it updated.

Rewriting the same page for every long-tail wording. Synonyms and meaning are enough. Extra versions of the same service page add editing work without a clear quality gain. If two URLs say the same thing in slightly different words, you now have two pages to keep honest.

Special schema or a Markdown copy of every page. Not required for inclusion in Google’s generative features, according to the guide. Structured data can still help other jobs on a site. It is not the ticket into an AI Overview.

Mentions, spam, and the quality tradeoff

Google’s warning, in plain terms: buying or faking mentions so AI will talk about your business is unlikely to help. The same spam safeguards still apply. Generative features depend on ranking systems that look for quality and on systems that block spam.

The tradeoff for a local service owner is concrete. A real review, a clear service page, and a repeatable delivery process beat a pile of inauthentic name-drops. A mention that a customer would not recognize as true does not make the business more profitable. It makes the public story harder to defend.

Owners who tried these tactics were often responding to fear, not to laziness. Unclear offers invite shortcut thinking. When you cannot say who the work is for, a tactic that promises visibility without that sentence starts to look reasonable.

Software and AI can draft a page. They cannot invent trust. If the process is messy, the page will be messy too. A model will happily write “premium results” over a workflow you have not defined. The customer still has to live with the real delivery.

Agent-ready sites: optional, and only if it fits the workflow

Google’s forward-looking section is easy to overread. It points to agent-friendly practices and to standards such as Universal Commerce Protocol and WebMCP, so an agent could act for a user—book, buy, or complete a step—rather than only summarize a page.

The tradeoff is extra work. Google frames this as relevant only if the business has time and a real reason. A shop with a working checkout, or a clinic that can safely take a booking, might have that reason later. A protocol is not a growth plan.

For most Brazilian service owners, a working contact path matters more. So does a page that states price logic, service area, and what is included. An agent that cannot tell whether you cover their city, or what “done” costs, will not save the sale. A person reading the page on a phone will not either.

Technical founders can treat agent standards as a later build, not the first software project. Ship the page a buyer can understand. Then decide whether an agent completing a task is a real workflow or a demo.

This guide is Google only

Be explicit about the uncertainty. ChatGPT, Claude, and other tools do not have to follow Google’s documentation. Google does not claim to publish every ranking detail. Anyone who says this one page explains “how AI search works” everywhere is filling gaps the document leaves open.

A useful workflow is one checklist for Google—crawl, clarity, quality—and a separate, smaller check of how you show up when you ask those other tools about your own business. Ask the question a customer would ask. Read the answer. Note what is wrong. Fix the page or the offer. Do not build a second career out of the screenshot.

Avoid treating “GEO” or “AEO” as that second career. The Semrush piece notes that Google frames this as an extension of SEO, not a new channel with its own secret method. New labels are fine for conversation. They are a poor reason to abandon a page that still fails a basic reading.

Profitable attention still depends on an offer people want. Search visibility does not fix a confusing service. If the AI answer describes you accurately and the customer still does not buy, the bottleneck is the offer, the price logic, or the proof—not the absence of another acronym.

A small next step this week

Pick one money page: the service you most want new customers to understand.

Write, in one paragraph, who it is for, what done looks like, and what you will not do. Put that near the top. A boundary is part of clarity. “We do not take emergency calls” saves you and the buyer.

Then check three practical items. The page loads. Google can reach it. The heading matches the question a customer would type.

If you want a second pass, bring that page to a short review—a workshop, office hours, or a lightweight systems audit—and name the one repeated task the page should remove for the buyer. A useful page does not only rank. It shortens the next conversation.

Which page will you clarify first? Say it in one sentence.

Share this post

Get new posts by email

One email from Leonardo Ribeiro when a new post is published. Nothing else.

Comments