The short version
Restaurant websites get evaluated in 30 seconds on a phone, often in the parking lot of the competitor down the street. The diner already knows they want to eat — the question is whether you're open, whether the menu fits the night, and whether they can book a table now. Three answers, 30 seconds. Sites that can't deliver them lose the table to the restaurant that can.
Website Killer generates the full restaurant site from a prompt: hero with your food photography, menu organized by course with prices, hours and address with a Google Map embed, online reservation CTA routed to OpenTable / Resy / a direct form, click-to-call phone CTA prominent on mobile, and a press / reviews block. Restaurant + LocalBusiness JSON-LD is wired automatically with cuisine type, hours, address, phone, and menu URL — which is how Google reads your restaurant as a local entity, the prerequisite for showing up on Maps and the local 3-pack.
What you bring: real food photos, your actual menu with prices, your hours, your phone number. The AI fills in the rest. Five minutes to a publishable site, an hour including a real custom domain.
What restaurants sites must have
- Hero with real food photography (not stock)
- Menu section organized by course with prices
- Hours + location with Google Map embed
- Online reservation CTA (OpenTable / Resy / direct form)
- Click-to-call phone CTA prominent on mobile
- Press / reviews block with named publications
- LocalBusiness + Restaurant schema with cuisine type
- Private events / catering inquiry form (if relevant)
Why Website Killer for restaurants
- Food-photography-aware templates designed for taste — not the generic 'restaurant template' look
- LocalBusiness + Restaurant JSON-LD auto-generated from hours, address, cuisine, menu URL
- Click-to-call CTA prominent on mobile (60% of diner conversions are calls, not form fills)
- Sub-1.5s LCP on 4G — diners checking from a parking lot don't bounce
- Custom domain with SSL — yourrestaurant.com, not yourrestaurant.menupages.com
What great looks like
Restaurant sites that rank locally and convert in-person traffic share five traits.
- Real food photography in the hero — stock photos lose to a phone-shot photo of your actual food every time
- Open-now indicator above the fold — diners checking 'are they open' bounce in 3 seconds if it's hidden
- Menu with prices visible — hiding prices for 'ask the host' filters serious diners out, not in
- Reservations one tap away — every section should have a 'book a table' CTA on mobile
- Press / reviews quoted with names — Eater, NYT, local food blog mentions all earn trust
Ranking signals
Local SEO checklist
The technical floor is wired automatically. The ranking signals below depend on you — most of them sit outside the website.
- Verified Google Business Profile with the same name/address/phone as the site (NAP consistency)
- Cuisine type listed in schema and on the page (drives 'Italian restaurant near me' queries)
- Hours with day-by-day breakdown (not just '11am–10pm' — Google penalizes vague hours)
- Menu URL submitted in schema + the site (Google reads the menu for dish-level queries)
- Reviews surfaced from Google / Yelp / Resy on the site (review snippets supported via Review schema)
- Photos uploaded both to Google Business Profile AND on the site (consistency signal)
Worked examples
Prompts that work
Two prompts you can adapt. The more concrete the prompt, the less editing afterward.
Independent neighborhood restaurant
Website for Casa Lou, a family-run Italian restaurant in Boston's North End, three generations on Hanover Street. Open Tue–Sun 5pm–10pm, closed Monday. Hero: family photo + 'Tuscan cooking, three generations on Hanover Street.' Menu organized: appetizers, pastas (handmade daily), mains, dessert, wine list with prices. Reservations: Resy link. Phone (617) 555-0142 click-to-call. Address: 421 Hanover St, Boston MA. Press block placeholders for Eater Boston, Boston Globe. Style: warm, family-photography-led, restrained.
Why this works · Independent restaurant prompts should include cuisine type, hours, neighborhood, and named press outlets. The AI uses these for Restaurant schema fields and review hooks.
Multi-location restaurant group
Website for Tareq Kebab, a Persian kebab restaurant with 3 locations in NYC (East Village, Midtown, Williamsburg). Hero: hero kebab photo + 'Charcoal-grilled Persian kebab across three NYC kitchens.' Each location: own page (/locations/[slug]) with hours, address, phone, map, photos, location-specific specials. Menu: shared across locations, organized by appetizers / kebabs / sides / desserts / drinks. Catering inquiry form on a /catering page. Style: warm, photography-dominant, Persian-pattern accents.
Why this works · Multi-location prompts should ask for per-location pages — each gets its own LocalBusiness schema, the right pattern for Google's local index.
Avoid these
Common mistakes
- Stock photos of generic Italian food — diners recognize the inauthenticity and trust drops
- Hidden menu behind a PDF — Google can't crawl PDFs reliably; the menu should be HTML
- Hidden phone number — restaurant calls convert 4x more than form fills; the phone belongs in the nav
- Reservation CTA only in the footer — every section should route to the reservation
- Missing 'closed Monday' notice — diners who show up to a closed restaurant don't come back
LocalBusiness schema
Local SEO baked in
Restaurants sites generated with Website Killer include LocalBusiness JSON-LD with your hours, address, and phone — so Google understands your business as a local entity, not just a webpage. That's the prerequisite for showing up in the local 3-pack and on Google Maps.
FAQ
Frequently asked questions
Does Website Killer add LocalBusiness + Restaurant schema for Google?
Yes — restaurant sites include Restaurant + LocalBusiness JSON-LD with hours, address, phone, cuisine type, and menu URL. Combined with a verified Google Business Profile, that's the prerequisite for ranking on Maps and the local 3-pack for '[cuisine] restaurant near me' queries.
Can my restaurant site take reservations?
Yes — embed OpenTable, Resy, Yelp Reservations, or a direct form that posts to your inbox. Reservation CTAs are prominent in every restaurant template and the booking link is one tap away on mobile.
How do I handle multiple locations?
Describe each location in your prompt with hours, address, phone, and the AI generates /locations index + /locations/[city] for each. Per-location LocalBusiness schema is the pattern Google's local index expects.
Can the menu be updated easily without redeploying?
Yes — chat-edit the menu live. Say 'add a new pasta: cacio e pepe, $24' and the AI inserts it in the right section. Daily-specials boards and seasonal menus update the same way.
Will my restaurant site rank for '[cuisine] near me' searches?
Local ranking requires three things: LocalBusiness schema (we handle), Google Business Profile + photos + reviews (you handle), and time. Website Killer gives you a faster, more modern site than 80% of local competitors — which improves bounce rate and dwell time, two ranking signals. Most restaurants reach page-1 ranking for their primary cuisine + city inside 60 days.
Can I embed an online ordering link (DoorDash, ChowNow, ToastTab)?
Yes — paste your delivery / pickup ordering URL and the AI wires a prominent 'Order online' CTA. Most independent restaurants route to ChowNow or ToastTab for commission-free direct orders alongside the DoorDash/Uber Eats default.
Ship your restaurants website today.
Free forever plan. AI generation, hosting, and a custom domain — in one flow.