A browser with no eyes
On August 7, 2026, Cloudflare announced Kitesurf, a cloud browser designed for AI agents rather than people. As TechCrunch reports, Kitesurf simply does not care about the visual layer of browsing: themes, tabs, extensions, all the things human browsers compete on are irrelevant to it. Its user reads the page as structure, not as pixels.
That is a telling product decision. Agents still have to use the web the way humans do, clicking through pages, filling forms, following links. But an infrastructure company the size of Cloudflare building a dedicated browser for them means the audience is no longer hypothetical. Your website now serves two kinds of visitors: people and software acting on behalf of people.
The traffic is already measurable
This is not a future scenario. In the first quarter of 2026, AI-referred traffic to US retail sites grew 393 percent year over year, and Fast Company's reporting on agentic commerce describes how Google, OpenAI, and retailers are racing to serve it. Notably, those AI-referred visitors outperform traditional traffic on conversion and revenue per visit. They arrive after an assistant has already qualified their intent.
The same logic shows up in search. With zero-click searches at 68 percent in early 2026, being quotable matters as much as ranking, a shift Search Engine Journal has covered in depth. Whether the machine reading your site is an answer engine or a shopping agent, the requirement converges: the site must be legible to software.
What an agent actually sees
An agent parsing your site does not see your brand gradient or your hover states. It sees:
- Document structure. Semantic HTML with real headings, lists, and labels, instead of a soup of styled divs.
- Structured data. Schema markup that states plainly what a page is: a product, a price, an opening hour, an article.
- Content that exists without JavaScript. If your critical content only appears after heavy client-side rendering, some agents will read an empty page.
- Followable flows. Forms and checkout steps that a machine can traverse: clear field names, predictable states, no dead ends that only a human would notice.
- A stated policy. Your robots and agent rules should say explicitly what automated visitors may do, rather than leaving it ambiguous.
None of this conflicts with good human-facing design. In our own web work at Clodron, the sites that read best to machines are usually the fastest and most accessible for people too. The disciplines overlap almost entirely.
How to prepare this quarter
You do not need an agent strategy document. You need a short audit:
- Load your key pages with JavaScript disabled. Is the substance still there?
- Run your product and service pages through a structured data validator. Fix what fails.
- Walk your contact or checkout flow and note every step that relies on visual context alone. Add labels and states a parser can follow.
- Write down your agent policy in robots rules, even a simple one, so access is a decision instead of an accident.
The web is getting a second audience. The sites that win with it are the ones that were built honestly for the first one: fast, structured, and clear about what they offer.