Home / Resources / Restaurant website checklist

Restaurant website checklist

A restaurant website needs the same few things every time: a menu as a normal web page, correct hours and address in text, one page per location, and details that match your Google profile. Structured data is optional and must match what the page shows. A starter is at the end.

Print this checklist

For the reasoning behind each item, read what a restaurant website must have and restaurant structured data in plain English.

1. The menu

• Your menu is a web page with real text, not only a PDF or a photo. Google's structured-data documentation recommends giving the full URL of the menu for food establishments.
• The menu says which items are vegan, and if you are not fully vegan, how you handle shared kitchens or fryers. Wording that makes a claim should be checked with the claims pre-flight checklist.
• Allergen information is available in the form that applies where you operate. Ask your local authority or a lawyer what is required.
• The menu shows when it was last updated, and prices are current.

2. Basic details in plain text

• Name, full street address, phone number and email are in text on the page, not only in an image or map.
• Opening hours are in text, including holiday and seasonal changes. They match your Google Business Profile.
• There is a map link or directions, and a line on parking, transit and step-free access if you know them.
• How to book, order or reserve is one obvious button or link, and it works on a phone.

3. Pages

• If you have more than one location, each has its own page with its own address, hours and menu. Google's documentation asks for the URL of the specific location, and it must work.
• There is an about page that says who you are, where ingredients come from and what makes you different, written from first-hand knowledge.
• Each page has its own title and one H1.

4. Consistency with your listings

• Name, address, phone and hours match on your site, your Google profile and your directory listings. Use the listings checklist.
• Your website address is on your Google profile and on HappyCow, and goes to the right page.

5. Structured data (optional)

Structured data is extra code that describes a page to machines. Google's local business documentation (updated 2026-09-08) lists name and address as required, and lists menu, servesCuisine, openingHoursSpecification, telephone, priceRange, geo and url as recommended. Google says no special markup is needed for its AI features (see the SEO and AI-search checklist), so treat this as optional. Only mark up what is visible on the page.

• You replaced every capitalised placeholder and the example.com addresses in the starter below with your real details.
• The hours, address and menu in the markup match what a visitor sees on the page.
• You tested the page with Google's Rich Results Test and fixed critical errors, as Google's documentation advises.
• After publishing, you checked the page with the URL Inspection tool in Search Console. Google says to allow several days for crawling and indexing.

Starter markup to copy

Paste it into the head or body of your location page, or give it to whoever manages your site. The values below are placeholders, not real details. Google's page says the hour format in its property table is hh:mm:ss while its examples use hh:mm, so check against the current page. For days that are closed all day, or open 24 hours, or hours that run past midnight, follow Google's documentation.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "YOUR RESTAURANT NAME",
  "url": "https://www.example.com/",
  "menu": "https://www.example.com/menu/",
  "servesCuisine": "Vegan",
  "telephone": "+00-000-0000000",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "STREET AND NUMBER",
    "addressLocality": "CITY",
    "postalCode": "POSTCODE",
    "addressCountry": "COUNTRY CODE"
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "17:00"
    }
  ]
}
</script>

Not sure where the markup goes in your website builder? Put it in the brief you give your designer: web designer brief.