Can diners view our menu on their phones without downloading a PDF?

Yes. Zeso builds menus using responsive semantic HTML blocks that load instantaneously on any smartphone without pinching or zooming. Every dish is indexed by Google, helping diners find your specific specialties.

How does Zeso help our restaurant be found when people search for food nearby?

Zeso embeds Schema.org Restaurant structured data detailing your exact street address, cuisine type, operating hours, and price range, served from 330+ edge locations so a machine reads the details without inferring them.

What does a restaurant website need before it takes orders?

The three things a hungry person looks for: what you serve, when you are open, and how to reach you. On Zeso that is the menu, the hours and the click-to-call, declared once and carried on every page. Everything else — the photography, the story, the awards — is what they read while they wait for you to answer.

Should each dish have its own page?

Not for its own sake. A page per dish is the doorway pattern unless each one is something people actually search for and you have real words to say about it. One menu, well written, with the dish and its price in the markup, covers most restaurants better than thirty thin pages.

Does the schema have to say "restaurant"?

The type you set — Restaurant carries the cuisine and the menu, which the generic LocalBusiness cannot. It is a field you set, and what it buys is legibility: a machine reads the facts you already publish instead of guessing them from the prose.

Restaurants, Cafes & Bistros

A restaurant website that drives direct orders without 30% delivery app commissions

Diners decide where to eat from their phone in seconds. A winning restaurant website needs mobile-friendly digital menus, real-time operating hours, and direct online ordering without middleman fees.

Schema.org Restaurant & Menu data

Built for: Independent restaurants, cafes, neighborhood bistros, food trucks, and craft bakeries

edge locations: 330+
median TTFB: <50ms
uptime on paid plans: 99.9%

Live Interactive Experience

Explore what your website feels like in the real world

Switch between personas, toggle desktop and mobile frames, and test real interactive micro-experiences powered by Zeso's modular Pods and sub-50ms edge network.

Edge Node: Anycast (330+ PoPs)Edge TTFB: 24ms

Domain: elenavance.design1.0× Lifetime Price-Lock

https://elenavance.designSSL · Anycast

HTTP/3

Digital Sovereignty

Elena Vance — AI Research & Systems Design

Partner at Vector Labs. Writing on deterministic state engines, memory models, and open web standards.

Custom Domain

elenavance.design

at wholesale registry cost

Monthly Hosting Fee

$0.00 / month

Free 1-page site on custom domain

Platform Lock-in

0% Lock-in

Clean static HTML/CSS/JS export

The problem

The problem this solves

Most restaurant websites upload clunky PDF menus that require downloading and pinch-zooming on mobile phones. Frustrated diners abandon your site and order through third-party delivery apps that take 20%–30% of your margin.

The payoff

What you get

Interactive Menu

Fast digital menus powered by CMS Pod without PDF downloads

Update menu items, seasonal specials, daily soups, and dietary tags (GF, Vegan) in seconds from your phone. Menus render as clean responsive HTML that search engines index.

Direct Orders

Commission-free pickup and table reservation routing

Forms Pod and Events Pod route takeout orders and party reservation requests directly to your kitchen printer, POS, or staff WhatsApp with zero platform fees.

Local Search Schema

Schema.org Restaurant with hours, price range and cuisine

The type, the address, the opening hours, the price band, the area you cover, the cuisine you serve, your food service permit and the seating you offer — reservations, takeaway and set menus in the catalogue — are declared in machine-readable JSON-LD, so a machine reads the restaurant instead of inferring it.

How-to guides

The guides behind this

Your markup

The block your own site should carry

The type is the field you set, so it is the specific one rather than the generic LocalBusiness. Zeso builds the entity from your business details — the type, the address, the coordinates, the hours, the price band, the area you cover, the services you sell, the licence you hold and the amenities of the place.

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "@id": "https://yourbusiness.com/#organization",
  "name": "Your Business Name",
  "url": "https://yourbusiness.com/",
  "telephone": "+1-555-0100",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "18 Example Street",
    "addressLocality": "Portland",
    "addressRegion": "OR",
    "postalCode": "97204",
    "addressCountry": "US"
  },
  "areaServed": [
    {
      "@type": "City",
      "name": "Portland"
    }
  ],
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": [
        "Monday",
        "Tuesday",
        "Wednesday",
        "Thursday",
        "Friday"
      ],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "priceRange": "$$",
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Services",
    "itemListElement": [
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Table reservations"
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Takeaway and delivery"
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Private dining hire"
        }
      },
      {
        "@type": "Offer",
        "itemOffered": {
          "@type": "Service",
          "name": "Seasonal and set menus"
        }
      }
    ]
  },
  "hasCredential": [
    {
      "@type": "EducationalOccupationalCredential",
      "credentialCategory": "license",
      "name": "Food service permit"
    }
  ],
  "amenityFeature": [
    {
      "@type": "LocationFeatureSpecification",
      "name": "Parking",
      "value": true
    },
    {
      "@type": "LocationFeatureSpecification",
      "name": "Outdoor seating",
      "value": true
    }
  ],
  "servesCuisine": "Pacific Northwest"
}

This is the block your own site should carry. On a site Zeso hosts, the platform emits it for you — fetch the page and check it. Anywhere else, replace every value with your own, including the opening hours, the four services and the credential's name, where a licence number belongs, and put it in a script tag of type application/ld+json. It is a declaration, not a request: it tells a machine what is true about the business, and it cannot make a ranking or a map result.

Data primitives

Pods that earn their place

CMSForm sheetAlbumsEvents

See every Pod

The alternative

Where this differs

Third-party delivery directories (DoorDash, UberEats) and unreadable PDF websites

What usually goes wrong

Losing 20%–30% of order totals to third-party delivery marketplace commissions
PDF menus that fail to load on mobile and cannot be searched by Google algorithms
Customer contact data trapped inside delivery apps with no ability to market directly

The Zeso approach

100% direct revenue and customer loyalty: mobile-optimized interactive digital menus, zero marketplace commissions, and Schema.org Restaurant structured data a machine can read.

Adjacent trades