Restaurant websites fail in ways that other small business websites don't, because restaurant customers behave differently. Nobody "researches" a restaurant for a week. They're hungry, they're on a phone, they have ninety seconds and three tabs open, and they're asking three questions:
- What's on the menu and what does it cost?
- Are you open right now (or at 7 PM Friday)?
- How do I get the food: directions, reservation, or order?
A restaurant website's entire job is to answer those three questions faster than the next tab. Everything else, the story, the chef's bio, the photos of the dining room, is supporting cast. Useful, but only after the big three are answered.
Here's the playbook, including the part most agencies won't say out loud about delivery apps.
The menu: kill the PDF
This is the single biggest fix on most restaurant sites, so let's deal with it first.
Stop publishing your menu only as a PDF.
PDF menus feel convenient on your end: the designer made it for print, you upload the same file to the website, done. But here's what's actually happening on the customer's end:
- On a phone, PDFs are misery. They open slowly, render at the wrong size, and force pinch-zoom-and-drag navigation. Your hungry visitor is two-finger-scrolling around a print layout designed for an 11 by 17 sheet. Many give up and check the next restaurant's tab instead.
- Search engines struggle with them. When your menu is real text on a real page, you can show up for searches like "shrimp and grits Wilmington" or "gluten free pizza near me." A scanned or image-based PDF takes that dish-level visibility and buries it. Google's own search documentation is consistent on this point: content as actual HTML text on a page is what gets indexed and ranked reliably.
- They're an accessibility problem. Screen readers handle a properly structured web page well and a designed PDF badly. Diners using assistive technology shouldn't be locked out of your menu, and in some cases that's a legal exposure, not just a courtesy.
- They go stale. Updating a PDF means reopening the design file, exporting, re-uploading. So nobody does, and the website menu drifts out of sync with reality. A web-page menu can be updated in two minutes when a price changes or a dish 86es permanently.
The fix: your menu lives on the website as a normal page. Sections, dish names, descriptions, prices, dietary flags. Real text. If you also want a printable PDF available as a download for people who ask, fine, but it's the backup, never the only option.
While you're at it, put prices on everything. A menu without prices reads as either "expensive" or "out of date," and both cost you covers.
Hours: the most boring thing on your website is also the most important
An outdated menu annoys people. Wrong hours create enemies.
When someone drives across town because your website said you were open, and you weren't, you didn't just lose that sale. You created a person with a story about you, and they tell it. Worse, they tell it in a Google review.
Treat hours as a maintenance discipline, not a set-and-forget field:
- Your website and your Google Business Profile must always agree. Most "are they open" checks happen on Google, not your site, so keep both current. Google's guide to managing your Business Profile covers setting regular hours, and crucially, special hours for holidays.
- Update holiday and special hours in advance. Closed for Thanksgiving, closing early Christmas Eve, closed for a private event Saturday. Set these on Google as special hours and reflect them on the site. The week before a major holiday is exactly when "open now" searches spike.
- Kitchen hours versus bar hours. If the kitchen closes at 9 but the doors close at 11, say so. "Open until 11" followed by "kitchen's closed" at 9:15 is the same betrayal as wrong hours.
- If you close unexpectedly, update Google first. Burst pipe, staffing crisis, whatever. Thirty seconds in the Business Profile app prevents a day of angry doorknob-rattlers.
Local SEO: how empty tables get found
Restaurants live and die on local search. "Best tacos near me," "seafood restaurant Wilmington NC," "brunch open now." Showing up for those searches isn't magic; it's a short list of fundamentals done consistently.
- A complete Google Business Profile. Categories set correctly (primary category matters most), menu link, ordering and reservation links, attributes (outdoor seating, kid-friendly, vegetarian options), and photos. Lots of photos. Food photos in a Business Profile do more for a restaurant than almost any other marketing asset, and the listing can be managed for free through Google for business.
- Reviews, and replies to reviews. A steady flow of recent reviews matters more than a big stale pile. Build the habit: train your team to mention it, put the direct review link on receipts or table cards. And reply to reviews, especially the bad ones, briefly and like a calm professional. Future customers read your replies as a preview of how you'd treat them.
- A fast website with real text. Your dishes, your neighborhood, your cuisine, written in actual sentences on actual pages. The dish-level searches mentioned above only find you if the words are on the page.
- Mobile speed. Restaurant traffic is the most mobile-heavy of any local business category. A site that loads slowly on a phone in a parking lot is a site that loses to the place next door. The guidance at web.dev covers the details, but in practice it comes down to a modern, lightweight build and properly compressed photos. Food photography is wonderful and also the number one cause of restaurant sites that take eight seconds to load.
Third-party delivery: the honest math
Now the part that deserves straight talk.
DoorDash, Uber Eats, and Grubhub commonly take a commission in the range of 15 to 30 percent of each order, depending on the plan and market. On restaurant margins, that frequently turns a profitable order into a break-even one, or worse. You already know this; you see the statements.
So should you quit the apps? For most restaurants, no, and anyone telling you to rage-quit them tomorrow is selling something. Here's the honest framing:
- The apps are a discovery channel you rent. They put you in front of people who have never heard of you, scrolling at 8 PM with a credit card already on file. That's real and it has value, especially for new restaurants. Think of app commissions partly as a marketing cost.
- The problem is when regulars order through the apps. Discovery commissions on a new customer can be defensible. Paying 25 percent on the customer who orders from you every Friday is a hole in the boat. The strategic goal isn't quitting the apps; it's moving your repeat customers to a direct channel.
- The website is how you do that. A clear "Order Direct" path on your own site, whether that's online ordering, call-in, or reservations, plus small nudges everywhere: a line on the box, a card in the bag, a note on the receipt. "Order direct from our website and skip the app fees." You don't need every customer to switch. Every regular who does is margin recovered every single week.
- Be honest about the tradeoffs in the other direction too. Direct online ordering has its own costs: software fees, payment processing, and you handle your own fulfillment or pickup logistics. For some operations, especially low-volume delivery, staying app-only for delivery while pushing direct pickup is the rational call. Run your own numbers instead of adopting anyone's slogan.
What your website should do, concretely: make the direct ordering or reservation path the most prominent button on the site, list the third-party app links below it for people who insist, and never bury direct ordering to look neutral. It's your website. It should favor your margins.
The complete restaurant site
You don't need much. You need it right and current:
- Home. Cuisine, vibe, location, hours, and three loud buttons: Menu, Order or Reserve, Directions.
- Menu. Real text, real prices, dietary flags, updated when reality updates.
- Order and reserve. Direct path first, apps second.
- About. Your story, your people, your photos. This is where personality lives, after the big three questions are answered.
- Contact and hours. Address, tap-to-call, parking notes, hours matching Google to the minute.
This is the structure we build restaurant sites on, and it's the same discipline behind every build in our website and SEO service: answer the visitor's real questions first, fast, on a phone. It's how we approach every local industry we serve across North Carolina and beyond.
Want it handled by next week?
We're Omnyra, a veteran-owned web shop in Wilmington, NC. We've built 1,500+ small business websites in the last 90 days, and we build done-with-you: your site is built live on a call with you, so the menu, hours, and ordering links are right because you're sitting there confirming them.
First draft in 24 hours. Live in 7 days, guaranteed. Tiers from a $500 Minimal build to Super Max from $6,000, with pay-in-4 and Klarna available.
Book a call and we'll build it together, or see pricing first.