Is Your Website Blocking AI Agents and Their Customers?

Should your website let AI agents in? If you sell anything online, take bookings, or capture leads through a form, the answer is increasingly yes, and many businesses are saying no without knowing it. This week TechCrunch reported that personal agents such as Meta's Muse and ChatGPT's Dots are running into walls across the web. Amazon has blocked Muse from shopping on its store. United's terms forbid booking with an "automatic device". eBay restricts unauthorised agents. Yelp wants a paid data licence. Meanwhile Walmart, which actually partnered with Meta, still found its own human-verification buttons turning Muse away. Meta's line was blunt: turning away a personal agent means turning away the customer behind it.

Amazon and United can afford to block agents on purpose. They have the brand pull to make customers come to them directly. A mid-sized retailer, a hotel group, or a B2B supplier mostly can't. If a customer asks their agent to reorder supplies, book a room, or request three quotes, and your site is the one the agent can't get through, the order goes to a competitor whose site it can.

The Problem: Most Blocks Are Accidents

Very few small and mid-sized businesses have decided to block AI agents. The blocking happens anyway, through defaults nobody revisited. Three sources cause most of it.

• CDN and firewall defaults. Since September 15, Cloudflare's defaults for new domains, newly added sites, and Free-tier accounts that never changed their settings allow search crawlers but block both AI training and AI agent traffic on pages that show ads. Cloudflare sorts AI bots into three buckets: search, training, and agent. The agent bucket is the one acting for a real customer in real time.
• Bot challenges on the pages that make money. CAPTCHAs and "press and hold" checks on checkout, booking, and contact forms stop scripted abuse, but they also stop a legitimate agent at exactly the step where the customer was ready to buy.
• Interfaces that only work for eyes. Prices that load only after a pop-up is closed, availability hidden behind a date picker with no underlying link, forms that rely on hover menus. An agent can sometimes push through these, but it is slow and fragile, and agents tend to choose the path of least resistance.

None of these are bad decisions on their own. Together they mean a growing class of buyer gets a worse experience on your site than anywhere else, and you will never see it in your analytics. A blocked agent doesn't fill in a complaint form. It just leaves.

Block, Allow, or Charge: Make It a Decision

The fix is not to throw the doors open. It is to treat AI agent access as a business decision per type of traffic and per part of the site, the same way you already decide what search engines may index.

1. 1Separate training from agents. Blocking crawlers that harvest your content to train models is a reasonable default for many publishers. Blocking an agent that is trying to buy from you is usually not. Most bot tools now let you set these separately; check that yours does.
2. 2Open the money paths, protect the rest. Product pages, availability, pricing, booking, and quote requests are where agent access earns revenue. Account settings, admin areas, and anything that changes stored customer data are where strict limits belong.
3. 3Rate-limit instead of hard-blocking. A per-agent request ceiling stops abuse without stopping a customer. Verified agents can get a higher limit than anonymous traffic.
4. 4Give agents a front door. A clean product feed, a structured booking or quote endpoint, or an MCP server gives agents a reliable way in that you control, instead of having them drive your website like a confused human. We covered why this matters for your internal systems at wizeb.com/blog/ai-agent-ready-business-systems-headless-2026.
5. 5Charge where it makes sense. If what an agent wants is your data rather than your product, pricing it per request is now practical. We put a paid tool on our own MCP server to test exactly this: wizeb.com/blog/mcp-server-x402-agent-payments-2026.

Standards Are Arriving, Slowly

The industry knows this is messy. According to TechCrunch, Meta, Walmart, Stripe, Sierra, Genesys and others have been working on an open standard for how agents talk to businesses for commerce. Separately, the Universal Commerce Protocol, backed by Google, Shopify, Amazon, Microsoft and Stripe among others, covers discovery through checkout, and Stripe and OpenAI publish the Agentic Commerce Protocol. These will make agent shopping smoother over the next year or two.

But standards help businesses that are already reachable. If your firewall drops agent traffic before it reaches your site, no protocol fixes that. The groundwork, deciding what agents may do and making sure they can actually do it, is yours either way.

A Realistic Example

Consider an online office-furniture retailer doing about $4 million a year, around a third of it from repeat business buyers. Its site runs on Cloudflare's Free plan and shows a small ad banner for a financing partner, so after September 15 the agent-blocking default applied without anyone noticing. Its checkout also carries a bot challenge added after a card-testing attack two years earlier.

The first sign of trouble was anecdotal: two account customers mentioned that their assistants reported they "couldn't complete the order" and they had gone elsewhere. A review found agent traffic being rejected at the edge and the checkout challenge failing every agent that did get through. The fix took a week. Agent traffic was allowed on product, stock, and checkout pages with a rate limit; training crawlers stayed blocked; the checkout challenge was replaced with risk scoring that only escalates on suspicious payment patterns; and a simple reorder endpoint was published for account customers. Within six weeks, orders placed through agents went from effectively zero to about 3% of repeat orders, card-testing attempts stayed blocked, and the team finally had a log showing which agents visited and what they tried to do.

Three percent is small. It is also the start of a channel that will keep growing, and the retailer is now on the right side of it while competitors are still invisible to it.

Where This Fits in Your AI Agent Plan

Most AI agent planning looks inward: which jobs your own agents should take on, what they cost, how to govern them. Customer agents arriving at your site is the outward half of the same shift, and it belongs in the same plan. If you are mapping out where to start, our full guide is at wizeb.com/blog/how-to-implement-ai-agents-in-business.

How Wizeb Helps

Wizeb audits how AI agents experience your business today: what your CDN and firewall let through, where bot challenges block buying journeys, and which pages agents can't parse. Then we fix it. That means setting agent access rules by section, adding rate limits and logging, and building the structured front doors, product feeds, booking and quote endpoints, or an MCP server, that let customer agents buy from you reliably. The same team builds your own internal agents, so both halves of the plan line up. See how we work at wizeb.com/services/ai-agents.

Three Questions to Ask Your Team This Week

1. 1What do our CDN and bot-protection settings currently do with AI agent traffic, and did anyone choose that on purpose?
2. 2Can an AI agent get from a product or service page to a completed order, booking, or quote request on our site without a human stepping in?
3. 3Do we have any log that tells us how many agents tried to buy from us last month, and how many failed?