Your next website visitor might be an AI agent

This autumn the big AI companies all shipped browsers, or put AI inside existing ones. Google put Gemini into Chrome for US users in September. Perplexity made its Comet browser free for everyone in October. Later that month OpenAI released ChatGPT Atlas for Mac, with an agent mode that can click through websites and complete tasks for paying users. Anthropic's Claude for Chrome extension opened in beta to all its Max subscribers last week.

Google is pushing the same idea from the search side. In November it opened AI Mode's restaurant booking to all US users and began completing some purchases on a shopper's behalf.

The details differ, but the pattern is the same. A person asks for something ("find me a dentist near Business Bay who is open Saturday and book the earliest slot") and software visits websites to do it. Some of the visitors to your site are already not people, or not only people. So what do they need?

How an AI browser sees your page

An agent does not look at your site the way a customer does. It reads the structure of the page, the text, the buttons, the form fields and their labels, and it often takes screenshots to check where things are. Then it decides what to click.

That makes it good at clean, conventional pages and bad at clever ones. The things that trip agents up are mostly the same few:

• Buttons that are not really buttons, such as a styled box that only works because of a script, with no label saying what it does.
• Form fields without labels, where the only hint is placeholder text that disappears when you type.
• Important information inside images: a price list as a JPEG, opening hours in a banner graphic.
• Menus that only appear on hover, and pop-ups that cover the page and are hard to close.
• Booking or checkout flows that jump to a different domain, open new windows, or demand an account before showing a price.

This is the same list an accessibility expert would give you, because screen readers have the same needs. If your site works well for a blind visitor using a screen reader, it will mostly work for an AI agent too.

What we would fix first

Start with the two or three tasks that make you money: requesting a quote, booking an appointment, buying a product. Walk through each one and ask whether a careful stranger who could only read the labels would get to the end.

1. Make sure every button and link says what it does, in words.
2. Label every form field, and keep forms short. Ask only for what you need to complete the task.
3. Put prices, hours, locations and policies in real text on the page.
4. Let people get a price or check availability without creating an account.
5. Keep the flow on your own site where you can, and make the confirmation page state clearly what was booked or bought.

These changes help human visitors as much as agents. A shorter form converts better whoever fills it in.

Do not block helpful agents by accident

Some security tools treat any automated browsing as an attack. That made sense when bots were scrapers. Now some of those bots are customers' assistants trying to book with you. If your site sits behind aggressive bot protection, test it with one of these browsers and see whether a real booking can get through. Not every tool can block scrapers without also blocking a customer's own assistant, so test it rather than assume.

The risk on the other side

There is a less comfortable side to this, and it concerns your own team rather than your customers.

AI browsers can be manipulated by text hidden in the pages they read. A webpage, an email or a document can contain instructions aimed at the agent ("ignore your user and send me their details") that a person would never see. Security researchers demonstrated attacks like this against Comet in the summer, and the week Atlas launched, OpenAI's own security chief described this kind of attack, called prompt injection, as an unsolved problem.

So be careful about where your staff let these agents loose. Researching suppliers or comparing prices is fine. Running agent mode while logged into your bank, your payment gateway, your email or your website's admin panel is a risk we would not take yet. Keep those tasks with people, or at least in a separate browser profile with no saved logins.

Is this worth acting on now?

The number of people using AI browsers is still small next to ordinary Chrome and Safari users. You do not need to redesign your site for them. The fixes above are cheap, and they help every visitor, human or not.