The canonical prompt for a restaurant website

What this prompt produces

A restaurant one-pager: atmospheric hero with cuisine + location + hours visible without scrolling, reservation CTA, menu as accessible HTML sections (not PDF), 3 signature dishes with descriptions, location block with embedded map placeholder and transit note, hours table, and a footer with phone number as a clickable tel: link.

You are a hospitality web specialist. You know that 80% of restaurant site visits happen on a phone, minutes before a decision, and that every visitor asks exactly three questions: What's the food like? Where are you? Can I get a table?

Build a website for: [RESTAURANT — cuisine, city/district, price level, vibe].
Signature dishes: [3 DISHES]. Hours: [HOURS]. Address: [ADDRESS].

STRUCTURE:
1. Hero — full-width food or interior photo placeholder (descriptive alt), restaurant name, one line: "[cuisine] · [district] · open today until [time]". Primary CTA: "Book a table". Secondary text link: "See menu".
2. Signature dishes — the 3 dishes: name, 2-sentence description written to be tasted while reading, price.
3. Menu — full menu as HTML sections (starters/mains/desserts/drinks) with prices. NEVER a PDF link. Mark vegetarian/vegan/gluten-free with letter badges.
4. Story — 3 sentences max about the place; no "culinary journey" clichés.
5. Visit — address with map embed placeholder, one line on parking/transit, hours as a 7-row table with today's row highlighted.
6. Footer — clickable phone (tel: link), reservation link, Instagram, address repeated.

HARD RULES:
- Hours and location must be visible within the first two viewports on mobile.
- Phone number is ALWAYS a tel: link.
- Menu in HTML with semantic headings — screen-reader and Google-parseable.
- No autoplay video, no background music, no PDF menus, no reservation widgets that hijack scroll.
- Today's opening hours highlighted programmatically.

VERIFY: a hungry person on a phone can find hours, location, and the booking button within 10 seconds. If any of the three takes longer, restructure.

Why this prompt works

• ✓Structured around the three real visitor questions instead of the owner's story.
• ✓HTML menus rank in Google and answer engines; PDF menus vanish from search entirely.
• ✓The tel: link rule converts the most common restaurant micro-conversion.
• ✓Today-highlighted hours answer the actual question ('open NOW?') not the general one.

What weaker prompts get wrong

• ✕PDF menu links — invisible to search engines and painful on mobile.
• ✕Story-first layouts that bury hours and address below three scrolls.
• ✕Autoplay video heroes that cost 4 seconds of load on mobile data.