How an agentic browser works
An ordinary browser waits for you to click. An agentic browser adds a model that can act on the page itself: it reads the rendered content, decides what the next step should be, then clicks links, fills fields and moves between tabs until the task you described in a sentence is finished. Perplexity’s Comet and OpenAI’s Atlas are built around this idea, and the mainstream browsers have added assistant modes beside their normal windows.
Two things separate it from a search engine crawler. It is triggered by a person inside a session rather than running on a schedule, so it arrives at the moment someone actually wants something. And it sees the page after the scripts have run, the way a human does, which means the only things it can act on are the things your interface genuinely renders.
Why agentic browsers matter
They change who reads your site. A page written to be skimmed by a person and collected by a training crawler such as GPTBot now also has to be operable by software trying to complete a job — compare three suppliers, confirm opening hours, start a booking. If the agent cannot get through, the visit ends quietly and nothing reaches your enquiry inbox.
They also blur your reporting. Agent sessions can arrive with no referrer, an unfamiliar user agent, or an address that belongs to a data centre, so they land in analytics as direct traffic or get stripped out as bots. The sessions look short and strange, because an agent skips everything a human lingers over.
Where agentic browsers go wrong
The usual failure is not ranking, it is friction. Bot protection, hard rate limits and interaction puzzles exist to stop automation, and they will just as happily stop a legitimate agent working for your customer. So will a form that depends on hover states, a phone number rendered as an image, or a price that only appears once a pop-up has been dismissed.
The second failure is trusting the name in the request. Any piece of software can claim to be an agentic browser, and plenty of scrapers do. Judge the traffic by its behaviour in your server logs, not by the label it gives itself.
What to do about it
Make the site work without cleverness. Put the facts an agent needs — price, availability, location, the route to contact you — in the HTML as text, describe them with structured data, give every control a real label, and keep at least one path to your form that needs no dragging, hovering or dismissing.
Then decide deliberately what you allow. Read your firewall and bot rules against your own logs rather than against a vendor’s defaults, separate agent sessions from human ones in reporting where you can, and treat a blocked agent as a lost customer rather than a blocked robot. My view is that almost all of this is ordinary quality work — clean markup, honest facts stated on the page, no dark patterns — and it pays off whether or not agent traffic keeps growing.