Website audit
Restaurant Website Audit: Fix Menu, Reservation, and Order Friction
A restaurant website must help a diner confirm the location, opening hours, menu, dietary fit, and best way to reserve or order. If you are searching for a restaurant website audit or asking someone to ‘audit my website,’ this checklist follows the journey from local search and Google Business Profile to a table request, phone call, or online order. It focuses on observable website issues and does not promise rankings, reservations, orders, covers, or revenue.
What should a restaurant website audit prove?
The audit should prove that a diner can identify the genuine restaurant, choose the right location, see current hours and menus, understand important booking or ordering conditions, and complete the intended action without avoidable friction. It should also confirm that the name, address, phone number, hours, menu links, prices, reviews, reservation routes, and ordering options agree across the website, Google Business Profile, maps, directories, and third-party platforms.
1. Test the first mobile visit
Open the homepage from a phone and look for the restaurant name, cuisine or concept, correct location, current service status, and main action. Test the menu, call, directions, reserve, and order buttons without relying on desktop hover states. Make sure consent banners, pop-ups, large images, and sticky controls do not hide essential information or compete with the action a hungry visitor is trying to take.
2. Match Google Business Profile to the website
Compare each genuine profile’s business name, address, phone number, category, regular hours, special hours, website link, menu link, reservation link, and ordering links with the live website. Open every destination on mobile and confirm it reaches the intended location. Correct controlled inconsistencies and remove obsolete providers without adding promotional keywords, unsupported locations, or unavailable services to the profile.
3. Make the menu current, readable, and useful
Check dish names, descriptions, prices, portion or format choices, service periods, availability notes, and required supplements against the current offer. Use an accessible HTML menu where practical; if a PDF is also provided, label it clearly, keep it current, and test it on a small screen. Avoid image-only menus, unreadable scans, conflicting versions, and search results that continue exposing an obsolete menu.
4. Explain dietary and allergen information carefully
State how diners can obtain current allergen and dietary information, who can answer questions, and whether advance notice is required. Use labels such as vegetarian, vegan, gluten-free, or allergen-free only when the restaurant can support their meaning and preparation controls. Avoid guarantees about cross-contact unless they are accurate, and do not let a website label replace a direct conversation when individual safety depends on current ingredients and kitchen procedures.
5. Verify restaurant proof and reviews
Confirm that ratings, review quotations, counts, awards, press mentions, chef profiles, venue photos, and food images are authentic, current, and attributed correctly. Do not present stock photography or another location’s dining room as the visitor’s chosen venue. Keep useful context with older awards or reviews and never invent diner stories, endorsements, popularity claims, or typical wait times.
6. Clarify reservations, walk-ins, and deposits
Explain whether a booking is instant or a request, which party sizes and service times are available online, and how walk-ins, groups, children, accessibility needs, deposits, cancellations, and no-shows are handled. Display material terms before submission rather than only in a confirmation email. Make clear when a third-party booking provider controls availability and avoid showing a successful request as a confirmed table unless inventory has actually been reserved.
7. Follow booking and order journeys end to end
Test reservation widgets, order buttons, phone links, contact forms, gift card routes, and delivery or collection handoffs with controlled data. Check location selection, dates, party sizes, item customization, fees, minimum orders, validation, payment, error recovery, staff delivery, and confirmation messages. Confirm that a user can return to the restaurant website and that failures provide a monitored alternative without losing essential context.
8. Set accurate hours and service expectations
Distinguish opening hours from kitchen, bar, lunch, dinner, collection, delivery, and holiday hours. Explain last-order times or service gaps where they matter, and keep temporary closures consistent across the website and profile. Avoid promising immediate replies, guaranteed seating, exact delivery times, or continuous availability unless operations can reliably support the statement.
9. Strengthen genuine local relevance
Provide the real address, map, directions, parking or transit guidance, entrance and accessibility details, and location-specific menus or contact information where useful. For multiple restaurants, give each genuine venue a distinct page with its own facts and actions. Avoid thin city pages, duplicate location copy, or pages implying a staffed venue where none exists.
10. Prioritize failures by diner risk
Fix wrong locations, hours, menu prices, dietary statements, deposit terms, phone numbers, broken booking or payment routes, false confirmations, and orders sent to the wrong venue first. Then address slow galleries, stale reviews, weak internal links, unclear service periods, and minor profile inconsistencies. Record the page, device, observed issue, owner, and retest date for every correction.
Frequently asked questions
What should be checked first on a restaurant website?
Start with the mobile journey: correct location, current hours, readable menu, phone number, directions, and reservation or order route. Then verify prices, dietary guidance, reviews, deposit terms, confirmations, and Google Business Profile destinations.
Should a restaurant menu be a PDF?
A PDF can be useful as an additional downloadable format, but it should be current, clearly dated or versioned where appropriate, accessible, and readable on mobile. An HTML menu is generally easier to browse, maintain, link to, and understand on small screens.
Does submitting a restaurant booking form confirm a table?
Only when the booking system has actually reserved the requested inventory. If staff must review the request, label it as pending and explain how and when confirmation will arrive.
How should a restaurant website handle allergen information?
Publish accurate, maintainable guidance, explain how to contact the restaurant about individual needs, and avoid unsupported safety guarantees. Current ingredient, supplier, recipe, and kitchen information should guide the final conversation.
How often should a restaurant website be audited?
Retest after changes to menus, prices, hours, service periods, locations, dietary procedures, booking rules, deposits, ordering providers, payment tools, or Google Business Profile links. Frequently changing menus and holiday schedules merit more frequent checks.
Quick checklist
- Can a mobile visitor identify the restaurant, location, current service, and next step?
- Do Google Business Profile details and action links match the website?
- Are menus, prices, service periods, and availability notes current?
- Are dietary and allergen labels accurate and responsibly explained?
- Are reviews, ratings, awards, photos, and chef details authentic?
- Are reservation, walk-in, deposit, cancellation, and group terms clear?
- Do booking, ordering, payment, phone, and confirmation routes work end to end?
- Are hours, closures, last orders, and response expectations accurate?
- Does each genuine location have useful, distinct local information?
- Have high-risk failures been assigned, fixed, and retested?