Machine layer SEO: make your site readable for AI agents
Short answer Machine layer SEO means making the version of your site that software reads clear enough for AI agents to compare and book for customers. Agents read your page code and the list of buttons and fields browsers build for screen readers. Put prices and hours in plain text, name every button and field, and run Chrome's free Lighthouse agent check.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat is machine layer SEO?
"Machine layer" is an industry label, not a Google term. It means the part of your website that software reads: the page code, the text in it, and the list of buttons and fields your browser builds for screen readers. Two kinds of software read that layer, and they want different things.
| Search crawlers | AI agents | |
|---|---|---|
| Who sends it | Google, Bing or OpenAI, on their own schedule | A customer who asked for a task |
| What it does | Reads pages so search results and AI answers can use them | Reads, clicks and types: compares, books, requests a quote |
| Obeys your robots.txt | Yes | Not reliably (see FAQ) |
| What decides if you win | Indexing, useful pages, reputation | Whether it can read your facts and finish your form |
Chrome's developer team draws the same line: "agents searching the web and agents using the web." For searching, they say, SEO principles still apply, and Google calls optimizing for its AI answers "still SEO." An agent has to find you before it can use your site, so that work comes first.
This page covers the second column. Google's definition:
"AI agents are autonomous systems that can perform tasks on behalf of people, such as booking a reservation or comparing product specifications." (Google Search Central: Optimizing your website for generative AI features)
Which agents your customers have, and where they stop, is in AI browsers and what your website needs.
How do AI agents read a website?
Three ways, per Google's web.dev team: a screenshot, the raw HTML, and the accessibility tree.
"Agents don't look at your website on a monitor. They operate on a machine-readable representation of your site." (web.dev: Build agent-friendly websites)
- Accessibility tree: the browser's list of every button, link and field, with its name and state. It was built for screen readers. Chrome's team calls a well-formed one "the primary way AI agents understand your page."
- HTML: the page code, which shows what belongs together, such as which price goes with which service.
- Screenshot: a picture the agent reads with a vision model. web.dev calls this slow and costly, and better as a backup.
Two rules follow. Facts an agent needs should be text on the page, not only inside a photo of your price list. And every button and field needs a name. Chrome's Lighthouse docs say missing labels "can block users with visual disabilities and agents from completing a task." Most of the work that helps blind visitors helps agents too.
What should an agent find on my site?
Picture the task a customer hands over, then check the answer is on your page as text.
| The customer tells the agent | What your page needs, as text |
|---|---|
| "Find a cleaner who can come Friday and book it" | Service area, and a booking form that works without an account |
| "Which of these three roofers gives free estimates?" | Your estimate policy on the service page |
| "Does this dentist take my insurance?" | Accepted plans, listed by name |
| "Get me a price for a brake job" | A price or range, or a quote form with labeled fields |
If your price depends on the job, a starting price or a range still gives an agent something to compare.
How do I test my site for AI agents?
Use Chrome's free audit. Lighthouse, the checker built into Chrome, has an experimental Agentic Browsing category. It needs Chrome 150 or later (Help, About Google Chrome shows your version). Open your booking or quote page, right-click, choose Inspect, open the Lighthouse tab, tick Agentic Browsing (it's off by default), and click Analyze page load.
| What it checks | What it means | Act on it? |
|---|---|---|
| Accessibility for agents | Every button and field has a name; nothing clickable is hidden from the tree | Yes, first |
| Layout stability | Buttons don't jump while the page loads, so an agent doesn't click the wrong thing | Yes |
| llms.txt | Whether a summary file exists; a missing file counts as not applicable | Optional |
| WebMCP | Whether your forms describe themselves to agents | Only if your website or booking platform offers it |
It shows how many checks you pass, not a 0–100 score, because "the current focus is to gather data and provide actionable signals rather than a definitive ranking" (Chrome's docs). Passing doesn't promise an agent will book with you.
Then try a real one. Ask an AI agent you use to book a test appointment on your own site and watch where it gets stuck. It will stop before anything final: OpenAI says "we require human review before any consequential action."
Do I need llms.txt, WebMCP or other agent formats?
Not yet, for most service businesses.
| Format | What it is | Status, November 2026 | For a service business |
|---|---|---|---|
| llms.txt | A short text file summarizing your site, at yoursite.com/llms.txt, proposed in 2024 | Google Search ignores it; Lighthouse treats it as optional | Harmless; don't pay extra for it |
| WebMCP | Code that tells an agent what each form does and what it needs | Proposed standard; a trial in Chrome and Edge (Edge's runs to March 30, 2027) | Wait for your website or booking platform to support it |
| Universal Commerce Protocol | An open standard Google uses so agents can buy products in AI Mode and Gemini | Early access: checkout on product listings for select merchants; Google's help covers the US, Canada and Australia | Not for services |
| Product feeds to ChatGPT | Your product catalog sent to OpenAI | Not needed for ChatGPT's browser to use your site | Skip unless you sell products |
| Schema markup | Labels for your business details in the page code | Not required for Google's AI features | Keep it accurate: schema markup guide |
Google's position on special files:
"You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities), as Google Search itself doesn't use them." (Google Search Central)
OpenAI says the same about feeds: sites "do not need to have direct feeds set up with us" for ChatGPT's cloud browser to use them.
One catch with WebMCP: if your booking form loads inside a frame from your booking software's site, Chrome switches WebMCP off inside it by default. The software company has to build the tools, and your embed code has to allow them. Ask your booking provider before paying anyone to "add WebMCP."
Not every agent visits your website
Some phone you. When a customer asks Google to book with you or check a price, Google may place an automated call to your Business Profile number:
"When customers use Google Search or Maps to connect with your business for various requests, Google might contact your business on their behalf through an automated phone call to complete the request." (Google Business Profile Help: About automated calls and texts from Google to your business)
- It books appointments and confirms prices and availability of services. If you share a quote, the customer gets it by email or text.
- If you work with an online booking provider, Google "may book through the partner or by calling your business directly." A connected provider is the machine-readable route: see Reserve with Google.
- In the US it works in every state except Indiana, Louisiana, Minnesota, Montana and Nebraska. Google's page names no other country.
- To turn it off, a verified owner goes to Business Profile settings, Advanced settings, and switches off "Bookings and inquiries from customers."
Example
A house cleaner in Phoenix with prices in a photo
Her rates sit in a flyer image. She retypes them on the page: from $150 for a two-bedroom home. Lighthouse flags two quote-form fields with no name, and her web person adds labels in an afternoon.
A physiotherapy clinic in Vancouver offered "agent-ready" setup
A vendor quotes C$2,500 for llms.txt and WebMCP. Her booking runs in a widget from her clinic software, so WebMCP code on her own pages can't describe it. She asks the software company about its plans and spends the money on service pages.
An auto repair shop in Columbus, Ohio
Google's automated calls ask for brake-job prices a few times a week. The owner keeps the setting on: each call is a customer waiting for a quote, and Google sends them his answer.
FAQ
Is machine layer SEO the same as GEO?
No. GEO is about being named in AI answers. This is about agents using your site once they find it. Google calls both SEO: is GEO worth paying for?
Do AI agents follow robots.txt?
Not reliably when a customer sends them. OpenAI says for its user-requested visits "robots.txt rules may not apply," and Google says its user-triggered fetchers "generally ignore robots.txt rules." Your firewall is the real control: should you block AI crawlers?
Does schema markup help AI agents?
Agents don't need it to use your site: they read the page and its accessibility tree. Google says its AI features need no special markup either. Schema still helps with rich results in Google Search.
Different for you?
- You want to know which AI agents exist, how to let them through your firewall, or how to track them: AI browsers and what your website needs.
- AI answers don't name you at all: how to get ChatGPT to recommend your business.
- Your host or firewall blocks bots: should you block AI crawlers?
- Visitors arrive but don't book: website not getting leads.
- Your booking or quote page needs a rebuild: Website Agent.