Top 9 Signs Your Restaurant Website Needs Rebuilding

Not every bad restaurant website needs a rebuild. Sometimes the platform is fine and nobody's fed it properly in three years — that's a content problem, and it's a much cheaper fix.

A day of writing, a photographer for an afternoon, and you're most of the way there. But sometimes the platform itself won't let you build a genuinely professional website for your restaurant, no matter how much time or content you throw at it.

That's a different conversation, and it's the one most restaurateurs avoid having because "rebuild" sounds expensive and disruptive before anyone's even worked out whether it's actually necessary.

• We audited 40 London restaurant websites for our last piece on the £8,000 mistake most of them are making.
• Along the way we found nine patterns that reliably separate a platform problem from a content problem.
• None of these require a developer to diagnose — you can check every one of them yourself, on your phone, in the next ten minutes

Main Problem of Broken Restaurant Websites

Every website problem in our audit fell into one of two categories, and the distinction matters because the fix — and the cost — is completely different.

1. Content Problem

Is when the platform is technically capable of doing the right thing, but nobody has done it. Kiln in Soho is the clearest example in our audit: the site scores 96 out of 100 on Mobile Performance — the highest of any great restaurant website we tested — because there's nothing on the page to slow it down.

The platform isn't the issue. The site has simply been dormant since 2020. That's a content problem. It needs a writer, a photographer, and someone willing to log in and use the CMS that's already there.

-------------------------------------------------------

2. Platform Problem

Is when the CMS [website builder] itself won't let you do the right thing, no matter how much content you throw at it. Every one of the five Squarespace built restaurants in our audit shipped a PDF or off-platform menu — Frog by Adam Handling, Casse-Croûte, Bancone Covent Garden, 40 Maltby Street, and Elliot's Café.

Zero out of five had a proper HTML menu. That's not five separate content failures. That's the platform steering every single operator toward the same dead end.

9 Signs You Need a Restaurant Website Redesign

Read through the nine signs below with this distinction in mind. Each one is tagged so you know which kind of broken you're looking at — and, in the fix-it tip underneath, whether you can solve it yourself this afternoon or whether it's a conversation about migrating platforms.

-------------------------------------------------------

1. Menu Exists Only as a PDF, Image or Instagram Link

🔴 Usually a Platform Problem

Twenty-five of the 40 restaurants we audited published their menus as PDFs. Two published it as an image of a handwritten chalkboard. One routed the "View Menu" button straight to Instagram, sending diners off the restaurant's own site entirely.

• PDFs are technically indexable by Google, but they rank poorly and almost never appear in AI-generated answers
• Image menus (a photo of a chalkboard) exist nowhere as text — not for Google, not for a screen reader, not for a diner using Google Translate
• Instagram redirects hand your menu content to a platform you don't own and can't control

HTML SOLUTION:

A) If your platform supports a proper content page (most do, even if nobody's used it), rebuild the menu as an HTML page with real headings and prices.

B) Keep the PDF as a downloadable backup if you like — just stop treating it as the primary version. If your platform genuinely has no way to publish structured text content, that's sign #6 below, and it's a bigger conversation.

-------------------------------------------------------

2. Nobody Touched the Hospitality Website in Years

🟡 Usually a Content Problem

One site we audited had a newsletter pop-up announcing an opening that happened a decade ago. Another's most recent blog post was from September 2024. A third — 40 Maltby Street — was, in our assessment, "built once and never touched again," resulting in a subpar restaurant site.

• Stale content is the single most common issue in our audit — more common than any technical failure
• It's rarely about capability. It's about nobody being assigned the job
• The platforms underneath these sites (WordPress design, Squarespace, custom builds) were all perfectly capable of being updated

MAINTENANCE SOLUTION:

A) This one rarely needs a developer. Put a recurring calendar reminder — quarterly is enough — to add small regular improvements: seasonal menu note, a new photo, or a short update.

B) If logging into your own CMS requires finding a password nobody remembers, or the person who built the site is unreachable, that access problem is worth solving on its own before anything else.

-------------------------------------------------------

3. No Schema Markup: Cafe, Restaurant, Menu

🔴🟡 Can be Either

Nineteen of the 40 sites we audited had no schema markup at all. Zero had Menu schema — the structured data that tells Google, and increasingly AI assistants, what's actually on the menu, what it costs, and what dietary options exist.

• Schema is the language search engines use to understand your page beyond just the words on it
• Some platforms (WordPress with a plugin like Yoast or RankMath) make this a five-minute job
• Others need custom code every time you want to add or change something

MARKUP SOLUTION:

A) If you're on WordPress, install Yoast SEO or RankMath and fill in the Organization and LocalBusiness fields — this genuinely takes under an hour.

B) If you're on Webflow, schema can be added via a simple code embed in your site settings.

C) If your developer tells you it's "not really possible" on your current platform, that's a platform ceiling, not a content gap you can write your way past.

-------------------------------------------------------

4. SEO - Meta Descriptions Are Missing or Generic

🟡 Content Problem

Twenty-three of the 40 restaurants we audited had meta descriptions that were missing, empty, keyword-stuffed, or — in one case — the CMS's own instructions to the operator, never replaced with real text.

• Your meta description is the sentence Google shows underneath your restaurant's name in search results
• It's also what AI assistants read when deciding whether your restaurant answers a diner's question
• Pages with a written meta description get nearly 6% more clicks than pages without one, according to Backlinko's analysis of 4 million Google search results

SEO SOLUTION:

A) Search your restaurant's name or brand on Google. The line underneath the title is your meta description. If it's wrong, empty, or generic, that's a two-minute fix in your CMS settings.

B) Write 120–155 characters describing what you serve, where you are, and what makes you distinct. "Modern British bistro in Soho, seasonal menu, natural wine, open Tuesday to Saturday."

C) Do this for every page, not just the homepage. Each menu page, each location.

-------------------------------------------------------

5. Every Food Photo is Invisible to Search

🟡 Content Problem

Across the audit, professional food photography sat behind empty alt text more often than not — sometimes literally the placeholder syntax <>, sometimes the camera's own file name, sometimes the auto-generated filename your phone gives an AirDropped photo.

• Alt text is the written description that tells search engines and screen readers what's in an image
• Paying for great photography and then leaving the alt text blank means multimodal AI search can't "see" any of it
• This is one of the cheapest fixes on this entire list

IMAGE SOLUTION:

A) Every time you upload a photo, write one sentence describing what's in it — "Rabbit and snail pie, Monday special" rather than nothing at all.

B) If you use a photographer, ask them to caption the files before delivery. Most CMS platforms prompt for alt text on upload; the discipline is remembering to fill it in, not a technical barrier

-------------------------------------------------------

6. Site Builders Not Built for Restaurants

🔴 Platform Problem

We found sites on Cargo (a CMS built for artist portfolios), on Tilda (a visual builder popular with agencies but light on SEO tooling), and five different sites on Squarespace — every single one of which shipped a PDF or off-platform menu.

• Platforms built for other purposes don't have restaurant-specific content types — no structured menus, no online ordering widget, no booking integrations built in
• They push operators toward the path of least resistance: upload a file, done
• This is the clearest example in our whole audit of a platform limiting the outcome regardless of effort

MIGRATION SOLUTION:

A) There isn't a content fix for this one.

B) If your platform has no menu content type and no realistic path to add one, the conversation is about migrating to a CMS built with hospitality in mind

C) Webflow web design, a properly themed WordPress build, or a hospitality-specific platform like BentoBox that actually supports structured menus.

-------------------------------------------------------

7. Mobile Performance is Capped, not Get Found

🔴 Platform Problem

Our audit's average mobile Performance score was 53 out of 100. Seventeen of 40 sites scored below 50. Some of the worst offenders had almost no content on the page — meaning the platform itself, not the content sitting on it, was the bottleneck.

• If a nearly empty page still scores badly, the template or builder is the cause
• Heavy page builders (some WordPress themes, some Squarespace templates) load unnecessary code on every single page regardless of what you publish‍
• Slow load times aren't a content problem — they're baked into the template, and Google has confirmed that page speed factors into search ranking

PAGE SPEED SOLUTION:

A) Ask your developer to run your homepage through Google's PageSpeed Insights and identify what's loading.

B) If it's genuinely just unoptimised images, that's fixable in a day.

C) If the report shows the template itself is heavy — excessive JavaScript, render-blocking scripts baked into the theme — no amount of content trimming will move the number, and that's your platform ceiling.

-------------------------------------------------------

8. Take Booking Button not Visible or Available

🔴 Platform Problem

We found booking links buried inside hamburger menu navigation, phone numbers hidden three scrolls down in the footer, reservation buttons that only appeared on the homepage and nowhere else, and one Michelin-starred site where getting to "Book" took four separate page loads.

• A persistent, sticky booking button — visible on every page, on scroll — is a basic feature most modern builders offer out of the box
• If yours doesn't have this option, or adding one means a full redesign, that's a platform limitation
• Every extra click between "hungry" and "booked" loses diners

UX DEVELOPMENT SOLUTION:

A) Check your platform's site-wide settings first — many builders have a "sticky element" or "persistent header" toggle that takes minutes to switch on.

B) If your builder has no such option and a developer has to hard-code it every time, that's worth weighing against the cost of the platform itself.

-------------------------------------------------------

9. Your Website Doesn't Tell a Story or Who You Are

🔴🟡 Can be Either

Very few of the 40 restaurants we audited told visitors anything meaningful about themselves. Two-sentence About pages. No photographs of the room. No named chef. No history — including at Rules, which has been open since 1798.

• AI assistants now answer "where should I take my parents for their anniversary?" by reading your website
• A minimalist business card doesn't answer that question — it just sits there
• Of 40 restaurants with Michelin stars, Bib Gourmands, and National Restaurant Awards between them, only Cora Pearl had an About page that read like a magazine profile

CONTENT SOLUTION:

A) Write 500 words about who runs the kitchen, when you opened, and what you're trying to do.

B) Photograph the room at service. Name your chef. If your platform has no way to add a real content page — only templated blocks — that's a platform problem, and it's sign #6.

-------------------------------------------------------

Quick Test List for Developers or Restaurant Owners

Go through the nine signs below and tick the ones that are true for your website. This takes about five minutes if you're checking on your phone as you go — which is exactly how most diners will judge whether your site is mobile-friendly in the first place.

• Your menu is a PDF, an image, or a link to another platform
• Nobody has updated the site in the last 6+ months
• There's no schema markup, or you don't know what that is on your site
• You've found something broken (a wrong title, a placeholder, a strange filename) that's been live for a while
• Your food photos have no real descriptions attached to them
• Your platform is a general-purpose builder, not one built for hospitality
• Your mobile PageSpeed score is under 50, even with a mostly empty page
• There's no booking button visible on every page as you scroll
• No story, history or description about you

Score Explanation

• 0 - 2: You're in reasonable shape. Fix these individually — none require a rebuild.
• 3 - 5: Worth a proper look. Some of these are platform-level and won't resolve with content work alone.
• +6: This is a rebuild conversation, not a content refresh. The platform is actively working against you.

-------------------------------------------------------

Conclusion: Restaurant Website Redesign

Most restaurant websites in London aren't broken because anyone made a bad decision. They're broken because a decision was made once — a platform chosen, a menu uploaded as a PDF because it was the fastest option that week — and nobody has revisited it since.

The nine signs above aren't a verdict on how much you care about your restaurant. Some of the best-reviewed places in our 40-restaurant audit had some of the weakest websites. The two things aren't related until a diner tries to find your menu on their phone and can't.

Run the quick test. Be honest about the score. If it's a content problem on your restaurant site, you can likely fix most of it yourself this month. If it's a platform problem, that's a bigger conversation — but it's one worth having before another year goes by with the same PDF sitting on the same subdomain, invisible to the diners searching for you right now.