Hero with cuisine + neighborhood
Name the vibe (“wood-fired pizza in Midtown”) so searchers and walkers know they’re in the right place.
Page blueprint
Sections a restaurant one-pager should include
Unlike consultants or contractors, your page must sell appetite and logistics at once — what you serve, when you’re open, and how to reserve or order.
Menu highlights (not a 40-page PDF)
Feature signatures, price bands, and dietary flags. Link out to a full menu PDF only as a secondary action.
Hours, address, parking
Operational facts prevent no-shows and angry reviews better than another food carousel.
Reservations / walk-in policy
State whether you take bookings, waitlists, or first-come seating — reduce phone tag.
Private dining / events (if relevant)
Higher-ticket enquiries need a separate CTA from nightly tables.
Reviews & press
Social proof for first-time diners who can’t taste the food online.
Design example
See food-service demos
Browse the homepage industry gallery for hospitality-style one-pagers, then regenerate with your restaurant name and cuisine.
Open industry demo gallery →Lead capture
Lead capture that fits F&B
Most restaurant “leads” are reservations, catering requests, or private-event enquiries — not generic newsletter signups.
- Primary CTA: Book a Table (phone + short form with party size / date / time).
- Secondary: Order Takeout / Delivery (deep-link to your ordering app if you use one).
- Tertiary: Private dining enquiry with headcount and event date.
- Ask for allergies or occasion only when it changes kitchen prep — keep the default form short.
- HaWa’s guaranteed contact form covers name/email/phone/message; use the message field for party details until custom fields exist.
SEO
Restaurant SEO priorities
Local + menu intent dominates. Rankings follow NAP consistency and useful on-page answers more than clever brand slogans.
- Title/H1 pattern: {Restaurant} — {Cuisine} in {Neighborhood/City}.
- Put hours, address, and phone in visible HTML (not only images).
- Publish signature dishes as text for “near me” + dish queries.
- TODO aspirational: Menu schema (Schema.org Menu/MenuItem) — HaWa does not ship a menu-schema builder yet; plan as a future/expert enhancement.
- Keep Google Business Profile hours synced with the website to avoid mismatched SERP data.
Checklist
Restaurant website go-live checklist
- Tonight’s hours (and holiday exceptions) are correct on mobile.
- At least 6 signature dishes listed as text with price bands.
- Dietary callouts present where you market them (veg, gluten-free, etc.).
- Reservation policy is explicit (book / walk-in / OpenTable link).
- Parking / transit note for first-time guests.
- High-quality interior or plated photo — not only stock.
- Phone number is tappable on mobile.
- Private events CTA separated if you sell that revenue line.
Questions
Industry FAQ
Should my full menu live on the HaWa one-pager?+
Put highlights and must-know items on the page. Link a maintained PDF or ordering menu for the complete list so daily specials don’t force constant regenerations.
Can HaWa replace OpenTable?+
No. Use HaWa for the marketing page and proof, then deep-link to your reservation tool. The contact form can capture party requests when you don’t use a booking widget.
Do delivery apps hurt my SEO?+
Third-party apps often outrank thin restaurant sites. A clear menu + hours page you own still matters for brand searches and walk-ins.
What CTA should be primary?+
Book a Table for full-service; Order / Call Ahead for counter service. Don’t lead with “Contact Us.”