An AI browser landing on your contact form or WooCommerce checkout is a different problem from an AI browser reading your blog post. Reading is passive; filling out a form and completing a purchase means the agent is acting on your site. Here’s what’s actually working today, narrowed specifically to forms and checkout.
The Agents Actually Doing This
Several AI browsing agents can now navigate a site, identify form fields, and fill them: OpenAI’s agent mode inside ChatGPT (built on its earlier Operator research), Anthropic’s Computer Use capability, Google’s agentic browsing work in Gemini, and Perplexity’s Comet browser. Each takes a slightly different approach — some drive an actual browser via screenshots and clicks, others work through a page’s accessibility tree or DOM directly — but the practical result for a site owner is similar: something other than a human is now filling in your forms.
Also Read: How to Prep Your WordPress Site for AI Browsers (ChatGPT Atlas, Perplexity Comet & Beyond) — the broader site-readiness guide this post narrows down to forms and checkout specifically.
Forms: Mostly Working, With Caveats
Standard, well-labeled form fields (clear label elements, sensible name/type attributes) are the easiest case for these agents. What breaks it: CAPTCHAs (by design), unusual custom widgets without proper accessibility markup, and multi-step forms that rely on JavaScript state an agent’s simplified page model doesn’t always track correctly. Nexter Blocks’ Form Builder outputs standard, semantic form markup, which is exactly the kind of structure these agents parse most reliably — a practical side benefit of building forms natively rather than through heavily customized third-party embeds.
The Specific Markup That Makes the Difference
The same accessibility fundamentals that help a screen reader also help an AI browsing agent, because both are working from the same underlying signal — the accessibility tree, not the visual layout. Concretely: every field needs an explicitly associated label (via for/id, not just placeholder text, which many agents and all screen readers treat as unreliable), a correct type attribute (email, tel, date rather than a generic text for everything), and a clear, programmatically associated error message when validation fails rather than a color change alone. A form that already passes a basic accessibility audit is, in practice, close to already being AI-agent-ready; the two checklists overlap far more than site owners usually expect.
Checkout: There’s Now a Named Protocol, With a Cautionary Adoption Story
Completing an actual purchase is a bigger ask than filling a contact form, because it involves payment credentials and real money, and this is no longer purely hypothetical — there’s a specific, named standard now. OpenAI and Stripe co-developed the Agentic Commerce Protocol (ACP), released as an open standard on September 29, 2025. It works by having the buyer select their payment method inside the AI agent’s interface, then Stripe issues a narrowly-scoped Shared Payment Token the merchant can charge through any compliant payment provider, without the buyer’s actual card details ever passing through or being exposed to the merchant’s own systems. PayPal joined as a supported payment provider on October 28, 2025, and Stripe shipped a fuller Agentic Commerce Suite in December 2025, with an April 2026 protocol update adding cart, product-feed, order-status, authentication, and MCP-compatibility support.
The adoption story is a useful reality check, though. ChatGPT’s own consumer-facing Instant Checkout feature, the most visible thing built on top of ACP, launched with Etsy and roughly a dozen Shopify brands (Glossier, Vuori, Spanx, SKIMS among them) — and was retired in March 2026 after that handful of merchants was essentially all that ever shipped against it. The underlying protocol kept developing regardless, but the specific consumer product built on it didn’t reach meaningful adoption. The practical lesson for a WordPress/WooCommerce store owner: the protocol layer is real infrastructure worth knowing about, but a specific AI-checkout product built on it can still fail commercially even while the standard underneath survives. Watch the protocol’s adoption by payment processors your store already uses, rather than chasing whichever consumer-facing AI shopping feature is getting attention this month.
Also Read: How to Get Your WooCommerce Store Ready for Agentic Commerce and AI Checkout — the dedicated deep-dive on store-side readiness for this.
What to Actually Do About This
- Use semantic, standard form markup (Nexter Blocks Form Builder or equivalent) rather than heavily customized JS widgets for fields you want AI agents to reliably complete.
- Don’t assume a CAPTCHA blocking these agents is a bug — for checkout specifically, that friction is often intentional risk management, not something to remove for the sake of AI compatibility.
- If you sell physical or digital goods, check whether your existing payment provider (Stripe, PayPal, and others) has adopted the Agentic Commerce Protocol rather than trying to reverse-engineer compatibility with every individual AI browser yourself.
- Treat any specific AI-shopping feature (like Instant Checkout was) as potentially short-lived even if the underlying protocol persists — avoid over-investing engineering time in one consumer-facing product’s specific integration.
- Run an accessibility check on your key forms even if accessibility itself isn’t your current priority — it’s a genuine two-for-one, since the same fixes benefit AI-agent compatibility.
FAQ
Should I try to block AI browsers from my forms?
That depends on your goals: blocking cuts off a growing channel of real interest (someone using an AI assistant to research or contact you), while allowing it means accepting less predictable traffic patterns. There’s no universally correct answer; decide based on what your forms are actually for.
Can an AI agent complete a WooCommerce purchase on its own right now?
Not reliably as a generic, unsupervised capability across arbitrary stores. A named standard exists (the Agentic Commerce Protocol, from OpenAI and Stripe), but the most visible consumer product built on it, ChatGPT’s Instant Checkout, was retired in March 2026 after limited merchant adoption. Most current agents still stop at or before the payment step for a typical, unintegrated store.
Does a CAPTCHA on my form block legitimate AI-assisted visitors too?
Yes, by design — that’s the tradeoff a CAPTCHA makes. If bot abuse isn’t currently a problem for a specific low-risk form, it’s worth weighing whether the friction is necessary there.
Does making my forms accessible also make them AI-agent-friendly?
Largely yes — explicit labels, correct input types, and programmatically associated error messages help both screen readers and AI browsing agents, since both rely on the same underlying accessibility-tree signal rather than the visual layout.
What is the Agentic Commerce Protocol (ACP)?
An open standard co-developed by OpenAI and Stripe, released September 29, 2025, defining how an AI agent collects a buyer’s payment method and hands the merchant a narrowly-scoped payment token to charge, without exposing the buyer’s actual card details. It has continued developing (an April 2026 update added cart, feed, and MCP-compatibility support) even after the specific consumer product built on top of it, ChatGPT Instant Checkout, was retired.
Conclusion
Forms are largely solved for these agents already, provided your markup is standard and semantic; checkout has real underlying infrastructure now (the Agentic Commerce Protocol) but the consumer-facing products built on it are still shaking out, with Instant Checkout’s own retirement in March 2026 as a concrete cautionary example. Build with standard, accessible markup for the former, and track your existing payment provider’s ACP support for the latter, rather than trying to force compatibility with every browser or chase every AI-shopping feature individually.
Suggested Reading
- How to Prep Your WordPress Site for AI Browsers (ChatGPT Atlas, Perplexity Comet & Beyond)
- How to Get Your WooCommerce Store Ready for Agentic Commerce and AI Checkout
- AI Agents and Your WordPress Site: What They Can Actually Do in 2026
