{"slug":"restaurant-website-prompt","niche":"website","lang":"en","title":"The canonical prompt for a restaurant website","description":"A prompt for a restaurant site that answers the only three questions visitors have — what's the food like, where are you, can I book — before anything else, with the menu as real HTML instead of a PDF.","spec":"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.","prompt":"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?\n\nBuild a website for: [RESTAURANT — cuisine, city/district, price level, vibe].\nSignature dishes: [3 DISHES]. Hours: [HOURS]. Address: [ADDRESS].\n\nSTRUCTURE:\n1. 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\".\n2. Signature dishes — the 3 dishes: name, 2-sentence description written to be tasted while reading, price.\n3. Menu — full menu as HTML sections (starters/mains/desserts/drinks) with prices. NEVER a PDF link. Mark vegetarian/vegan/gluten-free with letter badges.\n4. Story — 3 sentences max about the place; no \"culinary journey\" clichés.\n5. Visit — address with map embed placeholder, one line on parking/transit, hours as a 7-row table with today's row highlighted.\n6. Footer — clickable phone (tel: link), reservation link, Instagram, address repeated.\n\nHARD RULES:\n- Hours and location must be visible within the first two viewports on mobile.\n- Phone number is ALWAYS a tel: link.\n- Menu in HTML with semantic headings — screen-reader and Google-parseable.\n- No autoplay video, no background music, no PDF menus, no reservation widgets that hijack scroll.\n- Today's opening hours highlighted programmatically.\n\nVERIFY: 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.","whyItWorks":["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."],"commonMistakes":["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."],"keywords":["restaurant website prompt","restaurant ai prompt","cafe website prompt","menu website prompt"],"updated":"2026-07-18"}