Can AI read your menu? The restaurant visibility checklist

1. Test a dining decision, not your restaurant name

Choose requests that match your actual service: a relaxed weekday lunch, a birthday dinner for six, or a café with step-free access. Include the neighbourhood and one or two constraints. Look at several answers and the sources they cite rather than celebrating a single successful screenshot.

Record whether your restaurant appears, which location is named and whether the practical details are correct. A recommendation based on last year’s menu can disappoint a guest even when it looks like a marketing win. Keep branded accuracy questions separate from unbranded discovery questions.

2. Make the menu readable and maintainable

Publish dishes, descriptions and current prices as HTML text. A PDF can remain as a printable option, but it should not be the only place the menu exists. Add the menu to your main navigation and link it from each location page. Avoid requiring a login or app download to see it.

Give seasonal menus a visible date or validity period and remove stale versions from prominent links. Describe dietary options carefully. “Vegan option available” and “free from cross-contact” are different claims. Have your kitchen verify allergen statements and explain how a guest should confirm a specific requirement with staff.

3. Explain what a visit actually feels like

Publish the information that changes a dining decision: table service or counter service, approximate meal price, group capacity, outdoor seating, accessibility and reservation policy. Be specific about restrictions. A terrace open only in dry weather should not read like guaranteed outdoor dining.

Create a page for a real recurring occasion only when you have something useful to say. A group-dining page should explain set menus, deposits, capacity and how to enquire. Do not generate dozens of interchangeable “best date night in [district]” pages. One accurate venue page can answer many related questions.

4. Fix the local information trail

Check your business profile, website and reservation platforms together. Distinguish venue opening hours, kitchen service times and takeaway availability. Update holiday exceptions and temporary closures. For a restaurant group, make addresses, menus and booking destinations unambiguous for each venue.

Read reviews for repeated information gaps. If guests keep asking about parking or noise, add a factual answer on your site. Request honest feedback consistently; do not offer a reward for positive sentiment or script a review with keywords. Relevant local coverage can introduce the restaurant to new readers, but it should remain editorially independent.

5. Give the guest one reliable next step

Open the restaurant page on a phone and try to see the menu, reserve, call and find the entrance. Check that a reservation link opens the right location and party-size rules. A strong recommendation is wasted if the next screen is a broken widget or an unrelated venue.

Measure menu visits, reservation handoffs and completed bookings when available. If your reservation provider cannot return booking data, label handoffs as clicks, not covers. Revisit the same dining prompts each month and before major seasonal changes. The operational habit of keeping information accurate matters more than a one-off “AI optimisation” exercise.

Your 30-day action plan

Use the month to build a baseline and ship useful improvements. AI answers may take longer to change, and results can vary between runs.

• Week 1 · Test 10 dining questions and list wrong or missing facts.
• Week 2 · Publish the HTML menu and distinguish kitchen and venue hours.
• Week 3 · Fix reservation links and add a useful group or occasion page.
• Week 4 · Check answer accuracy, reservation handoffs and actual bookings where measurable.

Common questions