AI Agent Readiness for Restaurants
When someone asks an assistant about restaurants instead of opening a search results page, this is what it is trying to do — and what usually stops it.
The short answer
An AI assistant answering a question about your restaurant can only use facts your site publishes as text a machine can read. Below are the three questions it is most often asked about restaurants, the facts that decide each one, and the failures that keep those facts hidden.
What people are actually asking
Typed the way people type them. Each one is a question your site either answers or does not.
- restaurant near me open now with gluten free options
- where can i get a table for 6 tonight around 7
- is this place kid friendly and do they have parking
Check whether this place is open, whether it can seat or host the party, whether it can handle the dietary or accessibility constraint, and hold it.
Why it matters for Restaurants
Nowhere is the gap between how good a business is and how legible it is wider than here. Menus are the worst-formatted documents on the internet — a PDF, a Flash-era viewer, a photograph of a chalkboard, an Instagram embed. A restaurant with a great kitchen and a menu as a JPEG is invisible to every "where can I eat that is gluten free near here" query, and those queries have almost entirely moved to assistants.
What usually stops it
In rough order of how much damage each one does. The first is the one specific to restaurants.
-
Specific to Restaurants
The menu is a PDF
This one failure removes a restaurant from the majority of the queries it could win. Everything a diner filters on — dish, price, dietary suitability — is inside that file and readable by nobody.
-
The menu is a PDF, an image, or an embed
This is the defining failure of the category. If the menu is not HTML text, no assistant can tell anyone what you serve, what it costs, or whether it suits a dietary restriction — which is the question being asked.
-
Hours change and the site does not
Holiday hours, seasonal closures, kitchen-closes-before-bar — the cases where being wrong actually costs a customer are exactly the cases most sites never encode. Special-hours structured data exists for this and is almost never used.
-
Reservations happen entirely on a platform
If availability lives only inside a booking platform's widget, your own domain contributes nothing to the answer, and the platform gets cited instead of you — then charges you for the cover.
-
Dietary and accessibility facts are nowhere
Gluten free, vegan, halal, nut-free, step-free access, high chairs. Each of these is a filter someone is applying right now, and each one you have not written down is a query you cannot appear in.
-
Social media is doing the site's job
"Check our Instagram for today's specials" moves your most current, most useful information onto a platform that assistants cannot reliably read and that you do not own.
What to publish
None of this is new information about your business. It is information you already have, written down where something other than a person can read it.
Particular to Restaurants
- The menu as HTML with prices and dietary markers
- Holiday and seasonal hours as structured exceptions
True of this whole category
- The full menu as HTML text, with prices and dietary markers
- Real hours including holiday and seasonal exceptions, as structured data
- Reservation URL, party-size limits, and whether walk-ins are taken
- Dietary accommodations stated explicitly, not implied
- Accessibility facts — step-free access, accessible bathroom, parking
- Location detail a stranger needs: parking, entrance, nearest transit
What you get for it
Appearing in constrained searches. Most competitors cannot answer "open now, near here, has something my daughter can eat" — the one that can is the one that gets the booking.
How to fix it
Most of this is publishing what you already know, plus a discovery layer that tells an agent where to look: an MCP server, Markdown content negotiation, llms.txt, and the .well-known documents that let an assistant find all of it without crawling you page by page.
That layer is packaged as the AI Indexing Pack — a one-time $599 download you install on the site you already have, in about thirty minutes, on any Apache or LiteSpeed host running PHP 7.4 or newer. No subscription, and you can install it on every site you own.
This site runs the same pack. It scores 100/100 on isitagentready.com and 98/100 on Smithery, and you can check both yourself rather than take our word for it.
Or have us build the whole site. Custom builds are quoted per project, flat fee, and you own the code.
Questions
Someone asks an assistant: “restaurant near me open now with gluten free options” — can it answer for my restaurant?
Is this the same thing as SEO for restaurants?
What is the single biggest problem on most restaurant websites?
Do I need to rebuild my website to fix this?
How far behind is everyone else?
We scan real sites with our own engine and publish the distribution. The short version is that the gap between what buyers now expect an assistant to answer and what the average site can support is very wide — and it is widest in the industries that depend most on being found.
Other industries
The failures differ by trade. These are the closest to restaurants.