Making your website machine-readable

For twenty years, website optimization meant one thing: rank higher on Google. You optimized keywords, built backlinks, and chased Core Web Vitals. That model is being remodeled.

People are no longer typing queries into a search box and clicking through results. They are asking ChatGPT, Gemini, and Claude to find products, compare services, and complete tasks. These AI models do not browse your site like humans do. They read it through screenshots, raw HTML, and the accessibility tree. If your site is not structured for machine consumption, the model cannot recommend it.

Google recognized this shift in May 2026 with Lighthouse 13.3, introducing the Agentic Browsing category. It is a new set of automated checks that evaluate whether your website is constructed for machine interaction. Not as a 0 to 100 score, but as a pass ratio: how many of the applicable AI-readiness checks does your site actually pass.

At Google I/O 2026, Google announced a fundamental restructuring of Search toward conversational, AI-driven experiences. This is not a side experiment or a beta feature. It is the direction of the product. When the company that built the traditional search model starts rebuilding it around AI conversations, the writing is clear.

The same practices that make your site readable to AI models also make it more accessible to humans. Semantic HTML, stable layouts, clean structure. The incentives finally align.

For the last few years, page speed was primarily a ranking signal and a human UX concern. With AI search, it becomes something else entirely: a resource constraint.

AI agents operate on a limited token budget per session. Every byte of HTML, every delayed server response, every unnecessary script consumes part of that budget. A page with a 200ms TTFB lets the agent start parsing immediately. A page with a 3-second TTFB forces the agent to wait before it can even begin reading your content. By the time it finishes, it may have burned through enough of its token budget that downstream pages never get evaluated.

Slow response times and bloated payloads do not just frustrate human visitors. They make your site economically unviable for an AI agent to process at scale. Fast TTFB, lean HTML, and minimal blocking resources are no longer just performance best practices. They are discoverability signals.

notiduck tracks TTFB from three geographic locations every 5 minutes. If your server response time regresses, you will know before an AI agent decides your site is too expensive to read.

Lighthouse has always been a website quality testing tool, covering performance, accessibility, SEO, and best practices. Version 13.3 added a fifth category: Agentic Browsing.

Unlike other Lighthouse categories, Agentic Browsing does not produce a weighted 0 to 100 score. Because the standards for the agentic web are still emerging, the current focus is on gathering data and providing actionable signals. The report displays a fractional pass ratio showing how many AI-readiness checks your site passes, along with specific pass or fail statuses for individual audits.

Source: Chrome for Developers, Lighthouse agentic browsing scoring

A growing community has formed around Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO). GEO focuses on making your content more likely to appear in AI-generated responses, while AEO targets the growing number of AI-powered answer engines and chatbots that pull information directly from websites to answer user questions. The idea is that you can optimize your content specifically for these systems. Some of the advice is solid. Some of it is not. As Ahrefs puts it, "GEO, LLMO, AEO... it's all just SEO."

One real difference from traditional SEO is speed. Search engine optimization takes months: you publish, wait for crawlers, build backlinks, and hope the algorithm notices. GEO and AEO can move much faster. AI models with real-time web search capabilities index and re-crawl independently of traditional ranking cycles, so structural changes to your site can start influencing AI-generated recommendations within weeks, not quarters. That speed is real. It is also why the snake oil spreads so quickly.

Another difference: there are currently no sponsored results in AI chat interfaces. The major AI assistants do not sell placement in their organic responses. You are competing on content quality and machine-readability alone, not against companies with larger ad budgets. This will likely change as AI companies figure out monetization, but for now the playing field is genuinely open.

Claims like "your TTFB must be under 500ms from every location on Earth" or "every page must follow the BLUF format (Bottom Line Up Front) or AI models will ignore it" are circulating widely. There is no hard evidence to back these specific thresholds. No AI company has published research showing that a 501ms TTFB causes your site to be excluded from model training data, or that a paragraph without a BLUF sentence gets silently deprioritized.

Even llms.txt falls into this gray area. Lighthouse 13.3 now audits for it, which gives it a veneer of importance. But server logs from large hosts show AI bots are not downloading these files yet. Google's John Mueller has compared it to the keywords meta tag: something you claim your site is about, but not something the crawlers necessarily trust or use. We track it because it is part of the Agentic Browsing score, and being ready costs nothing. But do not expect it to move the needle on its own.

That said, a fast TTFB will never hurt you. It helps human users, it helps agents, and it helps your Lighthouse scores. The 500ms bar is a reasonable target even if the "must be under 500ms globally or else" framing is overstated.

BLUF is similar. Writing your conclusion first is a well-established communication technique from military and business writing long before AI existed. If you write your BLUF naturally, it will not look strange to human readers. It might actually help them. The idea that it is a secret signal to AI models is probably overthinking it, but the practice itself is harmless and often beneficial.

Our take: focus on what Google actually measures. The Lighthouse Agentic Browsing audits are deterministic, reproducible, and based on real signals. Community trends are worth watching, but do not restructure your site around unverified claims. The practices that matter, semantic HTML, clean accessibility trees, stable layouts, and llms.txt, are the same ones Google is testing for.

Sources: Google web.dev, Build agent-friendly websites · Chrome for Developers, Lighthouse agentic browsing scoring · Google Blog, Search at I/O 2026 · Ahrefs, GEO, LLMO, AEO: It's All Just SEO · Ahrefs, What Is llms.txt, and Should You Care? · Search Engine Journal, Google Says llms.txt Comparable To Keywords Meta Tag