FlashCrafterRestaurants playbook
What a restaurant site must show before someone decides to visit or book — and the checks that confirm it works, from the menu's HTML to the Google Business Profile button.
Most guests form their opinion of your restaurant before they ever call. Menus checked online, your own website visited before a decision, bookings made directly on your domain — the site is doing work a third-party listing will not do for you. This playbook turns that into ten checks and fixes you can complete yourself, each with the reasoning behind it and a source you can open.
Practical playbook
Publish every dish and every price as text on the homepage or one click from it — the complete menu, not a teaser or a 'see our menu' link to a PDF. Why it works: Menus with prices are among the elements diners look for before booking, and the menu is the content people came for. Keeping it on the homepage removes the step between landing and deciding.
Rebuild the menu as an HTML page. To test an existing one, open the site and try to select a dish name with your cursor — if you cannot select the text, it is an image or PDF and should be replaced. Why it works: Google indexes PDFs, but its SEO guidance recommends HTML for content you want people to find and read. A menu locked in a PDF or an image is content a search engine cannot easily match to a 'near me' query, and it is also harder for a guest to skim on a phone.
Log in to Google Business Profile and check where the website, menu, and order links go. If 'Order online' sends guests to a marketplace, change it to the ordering page on your own site. Why it works: This is the single highest-leverage check on the profile. When the button points at a marketplace, the direct order — the one without a commission and with the customer relationship attached — is handed away at the exact moment a guest is ready to buy.
Copy your name, address, and phone number character-for-character from your Google Business Profile into the site footer and every listing you control. Match punctuation, suite numbers, and abbreviations exactly. Why it works: Consistency in name, address, and phone (NAP) is one of the strongest local-pack signals reported in operator SEO guidance, and the underlying need is Google's own: local results rest on relevance, distance, and prominence, which accurate matching information supports.
Open your homepage in a browser and look at the tab label or view the source. Set a title that names the restaurant and what it is — for example, the name plus cuisine and city — and give each page its own title and descriptive link text. Why it works: Google uses the page title to decide whether a result is relevant to someone's search, so a generic title works against you at the exact moment relevance is judged. Descriptive titles and anchor text also tell a scanning diner what they are about to open.
Test the site at PageSpeed Insights using field data (real-user Chrome UX Report results, not just the lab score) and compare against Google's Core Web Vitals thresholds for LCP, INP, and CLS. Then make sure the phone version carries everything the desktop version does: full menu, hours, photos. Why it works: Google crawls and indexes the mobile version of every site by default. There is no separate mobile-friendly bonus — the risk is a slow or content-thin mobile page. Core Web Vitals are ranking signals, though relevant content still matters more.
Put a clickable phone number, the address with a map, current hours, a reservation path, real photos, and guest reviews on the homepage — the elements that appear on the standard homepage checklist. Why it works: These are the items diners reportedly check before choosing where to go, and most of them are the fields a mobile visitor acts on immediately: call, navigate, book. A phone number that is not tappable on mobile forces an extra step at the moment of intent.
Offer a reservation link on your own domain and keep it visible on the homepage and in the Google Business Profile — not only through third-party booking platforms. Why it works: A survey of 850 U.S. diners by Toast found 65% prefer to book directly on the restaurant's own website rather than a third-party platform, and 72% of diners in an Owner.com survey visit the restaurant's own site before deciding to go. Meeting that preference on your own domain keeps the guest where you control the experience.
Mark up the site with the Restaurant, LocalBusiness, and Menu schema types, including PostalAddress and OpeningHoursSpecification, then run the homepage through the Rich Results Test to confirm it is valid and free of errors. Why it works: Structured data can enable rich results in search, which is how a restaurant's hours, address, and menu can surface without a click. Validity is what matters — errors waste the markup, and Google does not guarantee a rich result even from correct markup. Pages can rank without it.
Complete name, address, phone, primary and secondary categories, regular hours, holiday hours, website, menu link, ordering link, business description, attributes, photos, and Q&A. Choose the most specific primary category available — 'Sushi Restaurant' rather than 'Japanese Restaurant' or 'Restaurant'. Why it works: Google says complete and accurate profiles are more likely to show in results, and that photos and menus help customers decide. Choosing the most specific category available sharpens relevance, one of the three factors Google names in local ranking. Operator field reports suggest most profiles are left 40–60% blank — unfilled fields are the cheapest gap to close.
Questions
Next step
Keep reading
Vendor pages change. Figures are as published on the capture date; confirm before deciding.