How to Structure a Website So AI Agents Can Complete Bookings

What does a bookable site need?

What does agentic booking mean for local service businesses, and how is it different from AI booking?

"AI booking" usually means an assistant helps someone find a slot, then hands them a link to finish. "Agentic booking" means the assistant does more of the work itself: checking availability across platforms, filling in details and, where allowed, completing the booking.

Google's AI Mode sits between the two. Google says it searches across multiple reservation platforms and websites for real-time availability, shows a curated list, and links directly to a partner to finalise. Browser agents, such as ChatGPT's built-in browser or Gemini's auto browse in Chrome, go further, opening pages and operating forms on a user's behalf.

For a local business, the difference matters in two ways. First, if you are not on a platform the assistant queries, you are not in its list of options. Second, if an agent reaches your own site and cannot operate the booking form, the booking fails, and the customer may book a competitor instead.

Can Google AI Mode book restaurants, events, beauty, and wellness appointments?

Yes. It started in the US, and restaurant booking has since reached other markets, including the UK from April 2026 through partners such as TheFork, SevenRooms, ResDiary and OpenTable. Google added restaurant reservations to AI Mode in August 2025, and in November 2025 made them available to all US users without a Search Labs opt-in. Event tickets and beauty and wellness appointments followed for Labs users in the US. At its May 2026 I/O event, Google said agentic booking was expanding to local experiences and services.

Google names these partners for finishing bookings: OpenTable, Resy and Tock for restaurants; Ticketmaster, StubHub, SeatGeek and Vivid Seats for events; and Booksy, Fresha and Vagaro for beauty and wellness. In each case AI Mode finds options and links to the partner's page, where the booking is completed. Hotel booking in AI Mode is rolling out in US English with partners including Booking.com, Expedia and major chains.

Where agentic booking is not offered, or your business is not on a platform Google connects to, AI Mode can still recommend you, but it is unlikely to show your live availability.

Fresha vs direct salon booking pages for AI agent conversions

Being on Fresha, Booksy or Vagaro puts a salon's live availability in front of AI Mode, because Google names them as partners. A direct booking page on your own site keeps the customer relationship and avoids platform dependence, but it relies on the agent being able to use it.

For most salons, the practical answer is both. Use booking software that is a Google partner, connect it to your Business Profile's booking button, and keep a direct page that agents can operate. Check each platform's current fees, especially for new clients found through its marketplace, before deciding where to send AI traffic.

How should the direct booking page be built?

Google's web.dev guide, "Build agent-friendly websites", explains that agents read pages through screenshots, raw HTML and the browser's accessibility tree, and usually combine them. Its recommendations translate directly to booking flows:

• Use real buttons and links. <button> and <a> are recognised as interactive; a styled <div> may not be. If you must use one, give it a role and tabindex.
• Label every field. Link each <label> to its input with the for attribute, so "Preferred date" is attached to the date field.
• Keep controls visible. Google says elements needed to complete an action should be visible and larger than 8 square pixels, or visual analysis may discard them. Avoid actions that only appear on hover.
• Keep the layout stable. Put the "Book" button in the same place on every service page, and avoid content that jumps as it loads.
• Give each service its own URL, with price, duration, deposit and cancellation policy in text.
• Show a clear confirmation page with the booking details, so the agent can report success.

OpenAI's publisher guidance makes the same point for its own agent: accessibility helps, because the agent, first built for OpenAI's now-retired Atlas browser, uses ARIA labels and roles to understand pages. The overlap with accessibility is no accident. Google's guide notes that everything that makes a site agent-ready also makes it better for people. More on readability for agents is in how brands can make their websites readable to AI agents.

What gets in an agent's way?

• Booking widgets inside iframes from another domain, which some agents handle poorly.
• Forced account creation before showing availability.
• CAPTCHAs at the start of the flow. Some protection is necessary; place it where it stops abuse without blocking every automated visitor.
• Pop-ups and cookie walls that cover the form.
• Availability loaded only after scrolling or clicking hidden controls.
• Prices shown only in images.

Do you need MCP or WebMCP?

Not yet. WebMCP is a proposed web standard for defining explicit tools, such as "check availability" or "book appointment", that agents can call directly. Google's guide says its APIs are available for experimentation in Chrome through an origin trial. It is worth watching, but a well-built form works with today's agents. When a full MCP server is worth building is covered in whether websites need MCP to be ready for AI agents. Adding a well-known file for agents is a separate step, covered in what should go in a website's .well-known directory for AI agents.

How do you test whether agents can book?

1. Check the accessibility tree of your booking page in Chrome DevTools. Every step should appear with a clear role and name.
2. Try it without a mouse, using only the keyboard.
3. Ask an agent to book a test slot, such as ChatGPT's agent or a browser agent, and watch where it stops.
4. Search AI Mode for your service in your area, and see whether your availability appears through your booking platform.
5. Check your listings point to the right booking link.

We have not run booking tests with AI agents on client sites ourselves. This page is based on Google's and OpenAI's documentation and announcements. Related checks are in how to check whether AI can read your pages.

What might this look like in practice?

Consider an illustrative day spa, Ruddby Spa, that took bookings through a custom widget embedded from another domain. When the owner asked a browser agent to book a massage, it failed at the date picker, which only responded to mouse hover. The spa moved to booking software that was a Google partner and linked it to its Business Profile. It also rebuilt its own booking page with labelled fields, a standard date input, and a "Book now" button in the same place on every treatment page. On a retest, the agent completed a booking on the spa's site, and AI Mode began showing the spa's available slots for massage searches nearby.

What do people ask about AI agents and bookings?

Can AI Mode book appointments at my salon?

If your salon uses a Google partner such as Booksy, Fresha or Vagaro, AI Mode can show availability and link to the booking in the US.

Does ChatGPT book restaurant tables?

Yes, in the US and Canada, through Yelp, OpenTable and Resy, with changes handled on those platforms.

Do I need special code for AI agents?

No. Semantic HTML, labelled forms and a stable layout work with today's agents. WebMCP is still experimental.

Should I block bots from my booking page?

Protect it against abuse, but avoid blocking the step where people, or their agents, choose a slot.