Quick answer: A WordPress restaurant website should make three jobs effortless on a phone: see today’s menu, book a table or join a waitlist, and place an order for pickup or delivery when you offer it. Keep hours, location and allergen notes easy to find. Choose plugins or simple custom fields you will actually update during a rush, not a fragile page-builder art piece nobody on staff can edit.
What diners need from the site right now
In April 2020 many dining rooms face sudden closures or limited service under stay-at-home orders. The website has to match the door. If you only offer curbside and delivery, say so on the homepage in plain language. If reservations are paused, remove or hide the old “book a table” path so people do not schedule disappointment.
Evergreen restaurant site jobs still apply when rooms reopen: menus, photos that look like the food, events and private dining details. Prioritise truth over aspiration.
Our earlier restaurant website design guide covers layout patterns. This article focuses on WordPress choices for menus, reservations and ordering.
Information architecture that works on mobile
Keep top navigation short:
- Menu
- Order (or Pickup)
- Reservations (if active)
- Location and hours
- Contact
Put a sticky call bar on mobile with Call and Order. Skip maze-like multi-location dropdowns unless you truly need them. One-location restaurants should show the address and Google Maps link in the footer of every page.
Menus staff can update
Ideal menu setup in WordPress:
- Structured items (title, price, description, dietary tags) rather than one giant PDF only
- PDF optional as a download for printers who want it
- Categories that match the pass (starters, mains, drinks)
- A “last updated” note when prices change often
Custom post types or a solid restaurant plugin beat pasting a flyer photo into the page. Photos of paper menus fail accessibility and SEO and go stale the night you change the soup.
If you run WordPress.com limits versus self-hosted needs, remember plugin freedom usually lives on self-hosted installs. See WordPress.com vs WordPress.org when choosing the hosting model.
Reservations and waitlists
Options that fit WordPress:
- Embed from an OpenTable-style provider
- Dedicated booking plugins
- WooCommerce Bookings for experiences and special seatings when productised
- Simple waitlist forms when tables are first-come
Whatever you pick, confirm:
- Timezone and party size rules
- Cancellation copy
- Whether deposits apply for large parties
- Who gets the notification SMS or email during service
Forms should be short. Patterns in WordPress forms apply: label clearly, show errors, do not reset the form on failure.
Ordering: pickup, delivery, third parties
Be explicit about channels:
- First-party order on your site (WooCommerce or specialty ordering plugin)
- Phone orders
- Third-party delivery marketplaces
Commission-heavy apps may still be necessary for discovery. If you also take first-party orders, promote them with clearer pricing or loyalty perks you can actually honour. Link the Order button to one primary path to avoid a choice paralysis screen.
For stores adapting checkout to pickup, many operational lessons overlap with wider ecommerce pickup flows even when the theme looks like a restaurant. Stock, prep times and ready notices matter as much as the food photography.
Local visibility
Restaurant searches are local. Keep Google My Business aligned with the site hours and temporary notices. On-site, include neighbourhood and city names naturally on the location page. Broader tactics sit in our local SEO checklist.
Schema for restaurants (name, address, hours, menu when appropriate) helps search engines understand the business. Do not mark up offers you cannot fulfil.
Performance and photos
Food photography is heavy. Compress images, lazy-load below the fold and avoid autoplay video heroes on the homepage. Diners on cellular outside your door will leave if the menu never arrives. WordPress speed optimization habits apply hard here.
Content blocks worth having
- Allergen and dietary note with a contact for questions
- Private dining / catering one-pager
- Gift cards if you sell them (helpful when dining rooms are limited)
- Hygiene and safety practices you actually follow, written without drama
- Employment page if hiring
Skip long brand novels above the menu link. Hungry users are impatient users.
Plugin discipline
Restaurants suffer when every manager installs a slider plugin. Keep a short approved list:
- Menu or custom fields
- Booking embed or plugin
- SEO plugin
- Security and backup
- Caching compatible with your host
Lock plugin installs to an admin who understands updates. A broken checkout on Friday night costs more than a fancy animation.
Accessibility and clarity
- Real text menus, not only images
- Colour contrast on dark “moody” themes
- Visible focus states on forms
- Alt text that describes the dish when the image carries meaning
Accessible pages help SEO and humans. They also reduce support calls from people who cannot read the grey-on-grey specials board.
Soft launch checklist
- Update hours and service mode on homepage and GMB together
- Place a test reservation or waitlist entry
- Place a test order for pickup
- Open the menu on a mid-range Android phone over cellular
- Call the number on the site and confirm it rings the right handset
Fix issues before boosting posts on social.
Photography and brand without slowing the kitchen
Hire or schedule a quick shoot for hero dishes, then compress aggressively. Serve responsive sizes. A beautiful 4MB photo of pasta that never loads outside the restaurant helps nobody.
Keep a shared drive of approved images with filenames that match menu items so managers can swap seasonal specials without opening a design tool.
Private dining and catering pages
Even when the main dining room is limited, catering and meal kits may keep revenue moving. Give each offer a simple page: what is included, lead time, order method and contact. Do not bury them under a generic “Events” label that still talks about packed banquet halls if that is not available.
Governance for franchise or multi-site groups
If brand marketing owns the theme but local managers own hours and menus, document who edits what. Child sites on Multisite or separate installs both work; confusion about who can publish a temporary closure notice does not.
FAQ
PDF menu or HTML menu?
HTML first for phones and search. PDF as a supplement if regulars ask for it.
Do we need WooCommerce for a restaurant?
Only if you sell products, gift cards or direct orders through the site. Many restaurants embed a specialist ordering tool instead.
How often should menus update in WordPress?
Whenever the pass changes prices or dishes. Train one FOH or manager on the edit flow so marketing is not a bottleneck for the soup of the day.
Should we list every delivery app?
List the ones you want volume through. Too many buttons scatter orders and confuse staff.
Feed the hungry visitor first
A WordPress restaurant website wins when menus, reservations and ordering tell the same story as the door. Build for thumbs, keep data editable and align temporary service modes everywhere. If you want help building or rebuilding a restaurant site that staff can run day to day, see Turn visitors into customers.
