Can an AI agent read your prices and finish your forms? A site check for browser agents

Why browser agents are a different visitor

A browser agent visits your site for one person, in real time, to finish a task. A search crawler indexes pages and a training crawler collects text for future models; neither is trying to book a demo.

OpenAI's dots, announced on 29 September 2026, each run their own cloud computer and browser, connect to over 4,000 apps through plugins and can sign in to supported websites with saved passwords.¹ A buyer can ask one to compare suppliers and book a call, and the agent does the clicking.

Cloudflare draws the same line in its controls. Its July 2026 changelog splits AI traffic into Search, Agent and Training, where Agent means real-time activity on a person's behalf, including browser-use agents.² Training crawlers are the fastest-growing part of the rest: they made 52% of crawler requests on Cloudflare's network in June 2026, up from 22% in spring 2025.³

Search is moving the same way. Google said in May 2026 that AI Mode had passed 1 billion monthly users, a company statement, and described agentic features in Search.⁴ Our note on tasks in AI Mode covers what that means for brand visibility.

Three kinds of AI traffic, three decisions

Search

• Indexes pages for answers
• Allow: blocking removes you from answers

Agent

• Acts for one person, now
• Reads prices, fills forms
• Allow on pages buyers act on

Training

• Collects text for future models
• A business choice, page by page

Is agent traffic allowed at your CDN?

Check this first, because a block at the CDN hides every other fix. From 15 September 2026, new domains on Cloudflare block Training and Agent traffic by default on pages that display ads, while Search stays allowed.²

Most B2B pricing pages carry no ads, so the default may not reach them. A domain set up after mid-September, a blog with ads on the same domain or a security rule written for scrapers can still stop agents where it matters. Open your CDN's bot or AI traffic settings and read what each class is set to, page group by page group.

Decide by page, not by site. Pricing, product, plan comparison, contact and demo pages are where agents finish tasks, so allow Agent there. Training is a separate decision, covered in our guide to blocking training crawlers while keeping answer bots.

Can an agent read your prices from the page?

Only if the price, the plan limits and what is included are written on the page as text. A price behind "contact us", inside an image or loaded only after a click is a fact the agent cannot report.

Put the plan name, price, billing period, currency, main limits and minimum term in server-rendered HTML. Agents with a full browser can run scripts, but crawlers and answer engines often read the raw HTML, and every reader should get the same facts. View the page source and search for the price. If it is not there, it is not reliably anywhere.

If you do not publish prices, publish the structure: what drives the price, the minimum term and what every plan includes. Our view: "pricing on request" gives an agent nothing to compare, so it is likely to compare the suppliers who did publish.

Can an agent finish your quote or demo form?

It can if the first step asks for plain fields and saves the lead before any challenge appears. A CAPTCHA, a forced account or a booking widget from another domain on step one can stop an agent cold.

Run the form as an agent would. Give each field a visible label, use standard input types for email and phone, avoid controls that only work with a mouse, and confirm success with text on the page rather than only a pop-up. Accessibility work and agent readiness overlap heavily here, because both depend on labels and predictable controls.

Keep spam protection, but move it. Invisible checks, rate limits and a challenge on later steps protect the form without blocking the first submission. Then decide what an agent may do on a buyer's behalf. Requesting a demo is fine; accepting terms or paying should probably wait for the person.

Do your terms match what other sites say?

They need to, because an agent comparing suppliers reads your page and third-party listings side by side. When the two disagree, it may report either one, and the buyer rarely checks which.

Check review sites, marketplaces, partner pages and comparison listings for your prices, plan names, minimum terms and trial length. An old figure on a directory is the usual culprit. Our guide to fixing wrong AI pricing at the source sets out the order of fixes.

For B2B software, the pages agents lean on are the ones that already decide shortlists: pricing, comparisons, integrations and security. Our list of shortlist pages to fix covers each of them.

How to run the check in an afternoon

Give an agent a real buyer task, watch where it stops, fix the first blocker and run it again. Set the task in a market you sell to, so the agent meets your real pricing and forms.

Saudi Arabia is worth testing because AI use there is rising fast. Microsoft's diffusion report for June 2026 shows it climbing from 30th to 25th place, the largest rise in its ranking.⁵ We found no published data on how many buyers there use browser agents, so treat the test as a check, not a forecast.

The afternoon check

1. CDN settings

   Read the Search, Agent and Training rules for each page group.

2. Page source

   Find the price, limits and term in the raw HTML.

3. Agent task

   Ask an agent to compare suppliers and book a demo.

4. Form result

   Confirm the request arrived and what the agent entered.

5. Listings

   Compare your facts with directories and review sites.

This check covers what an agent can do on your site. Whether AI engines name you at all is a separate measurement. Sigzen AI's audit runs buyer prompts across four engines (ChatGPT, Gemini, Google AI Overviews and Google AI Mode) on three separate days, through a licensed AI-answer data provider. See what the audit covers.