Most restaurant websites are not catastrophically broken. They look fine at a glance, the photos are nice, the brand voice is there. And they quietly cost the restaurant business anyway, through a handful of small issues that nobody notices because everyone who works on the site stopped looking at it months ago. A pre-engagement scan of a typical local restaurant site turns up the same five problems over and over. None require a rebuild. All of them are worth fixing.
Here they are, in rough order of impact.
1. The menu exists only as PDFs
This is the most common and the most expensive. The menu, the single most-visited thing on a restaurant site, lives as a stack of PDF files. Sometimes ten of them.
I want to correct a claim I have seen repeated on this exact point, because getting it right changes how you prioritize the fix. Google does not read PDFs poorly. Google converts PDF text to HTML internally and indexes it the same way it indexes a regular page (Google Search Central, on PDFs in search results), so your menu items are not invisible to search the way that claim implies. The real problems are more mundane and still worth fixing: a PDF re-crawls and re-indexes slower than an HTML page, so a menu change takes longer to show up in search. PDFs render badly on a phone, forcing the guest standing at your door to pinch and zoom instead of scroll. And there is no practical way to attach structured data, the machine-readable markup that describes a restaurant and its offerings, to a PDF, so even though the text gets indexed, none of the structure around it does.
The fix is to rebuild the menu as real HTML text with Restaurant and LocalBusiness schema markup added. To be clear about what that markup buys you: there is no supported Google rich result specifically for menus or individual dishes, so this is not a route to a flashier search listing. What it does is make your business machine-readable, cleanly and unambiguously, to search engines and to the growing number of AI tools that read structured data to answer questions about hours, cuisine, and price range. It is more work than uploading a PDF and it pays for itself in mobile experience and faster-to-update content alone.
If a guest at your door has to pinch-zoom a PDF on their phone to read your menu, you have already lost some of them to the place next door whose menu just loaded.
2. The neglect signals
A cluster of tiny details quietly tell every first-time visitor that nobody maintains this place:
- Raw code rendering as visible text. A stray markup declaration (something like an "xml version" string) showing through on the live page. It does not break anything, but every visitor sees it, and it reads as a back-of-house mess bleeding onto the front of the menu.
- A copyright year stuck in the past. It is a tiny detail that telegraphs "nobody has looked at this site in a year" to a first-time guest deciding whether you are still any good.
- Confusing navigation. Two menu items that both link to the homepage. Anchor links that point to nothing. Each one is a small frustration that adds up to "this is janky."
These are often five-minute fixes that punch far above their weight, because every single visitor forms a first impression from them.
3. There is no way to reach the visitor again
Most restaurant sites have a contact form and nothing else. Which means every visitor who is not ready to call right now leaves without giving you any way to reach them later. You paid, in rent, in food cost, in marketing, to get them to the site, and you let them walk with no follow-up possible.
The fix is real email capture: one tasteful modal or footer signup, and ideally a post-visit email trigger. Every visitor becomes a contact you own and can talk to again, about a new menu, an event, a slow Tuesday. A site without email capture is a leaky bucket by design.
Adjacent to this: group booking and catering inquiries usually fall into the same generic contact form, when catering is often the highest-value lead a restaurant gets. That lead deserves its own clear capture path, not a drop into the void.
4. The hours are wrong somewhere
Your hours live in at least three places: the website, the Google Business Profile, and whatever platform takes your orders. They drift apart, and the site is usually the one nobody updates. Holiday hours are the worst version of this, because they are wrong exactly when the most people are checking.
The cost is not abstract. A guest who drives over on a Monday you quietly stopped opening does not try again next week. They assume you closed, and they tell the person who suggested it. Pick one source of truth, make the site match the Google Business Profile exactly, set holiday hours a month ahead, and say plainly when the kitchen closes as opposed to when the doors do. Those are different times and guests find out the hard way.
5. Nobody has walked the ordering path
The "Order Online" button is usually the last thing anyone checks, and it is where the site quietly costs the most. It hands the guest to a third-party portal with different branding, a menu that does not match the one they were just reading, and prices that quietly went up to cover the commission. Reservation links have the same problem, often pointing at a platform you stopped using two seasons ago.
Open your own site on your own phone and order from yourself. Then book a table. Most owners have never done it end to end, and the handoff is where the drop-off is. While you are in there, find out what each of those orders actually costs you, because the commission is often the largest marketing expense a restaurant does not think of as marketing.
Two things are deliberately not on this list: schema beyond the menu, and Core Web Vitals. They matter, but they are small-site problems rather than restaurant problems, and Technical SEO for Small Sites covers both properly.
The honest priority order
If you own a restaurant site and have limited time, fix them in this sequence:
- Kill the neglect signals (code leaks, stale copyright, broken nav). Five-minute fixes, outsized first-impression impact.
- Rebuild the menu as HTML with schema. Biggest combined win for indexing speed, mobile experience, and machine-readability.
- Add real email capture, so the site stops leaking every visitor.
- Fix the hours everywhere they appear, starting with holidays.
- Walk your own ordering and reservation path on a phone.
A restaurant website does not need to be a work of art. It needs to load fast on a phone, show a menu Google can read cleanly, make a good first impression, and capture the people it attracts. Most sites miss at least three of those four, and each miss has a real, if hard to isolate, cost attached to it.
If you want a plain-language scan of what your site is doing well and what needs fixing first, a complimentary website audit will walk through it with you.
