Diners now ask AI "where should we eat tonight" and pick from the two or three names it gives them. If AI can't read your menu, hours and location, you're not in the answer — and you'll never know.
When someone asks ChatGPT or Perplexity where to eat, the AI reads candidate websites and answers with names. No scrolling, no maps, no review-site rabbit hole — and no trace in your analytics when you're skipped.
The most common restaurant failure: the menu is a PDF or an image. To an AI crawler that's a dead end — no dishes, no prices, no cuisine signals. Add a JavaScript-only reservation widget and unclear hours, and AI simply has more to say about the restaurant down the street.
The scan is free forever. If you want the fixes written for your restaurant, it's $29 once. Want them installed for you — llms.txt, schema, meta, robots.txt — it's $199 once. No subscriptions, ever.
Make your restaurant readable to AI: allow AI crawlers in robots.txt and your firewall, publish your menu as real HTML text (not a PDF), add Restaurant schema markup with cuisine, price range and hours, publish an llms.txt file, and keep your name, address and hours identical across Google, Yelp and directories. Then test monthly: ask ChatGPT "best [your cuisine] in [your town]".
Mostly no. AI crawlers reading your website see a link to a file — not your dishes and prices. An HTML menu is readable, quotable and recommendable; a PDF or image menu is close to invisible. This is the single most common restaurant AI-visibility failure, and it's usually a one-afternoon fix.
Yes. The same factors — crawler access, structured data, JavaScript-free content, clear headings — drive visibility in Google's AI Overviews as well as ChatGPT, Gemini and Perplexity answers.
Completely — no signup, no card. The scan and PDF report cost nothing. Paid options exist only if you want the fixes written for you ($29 one-time) or installed for you ($199 one-time).