Par secteur · Restaurants
Website audit for restaurants
Diners find restaurants on their phone, usually minutes before they choose a place. A menu trapped in a PDF, a gallery that loads forever or a phone number that is not tappable costs you covers every day it stays broken. Start with the free scan and fix what it finds.
The free scan checks one page in about 30 seconds. No account, no card.
What the audit adds
- Lighthouse on a mobile device: LCP, INP/TBT, CLS, page weight
- Technical SEO checks on every crawled page
- Site-wide crawl issues: duplicates, thin pages, orphan pages
- AI copy and conversion review with ready-to-paste rewrites
- A prioritized 30-day plan for your site
What usually goes wrong
Website problems that matter for restaurants
Each item lists the checks that detect it. When we do not check something automatically, it says so and tells you what to do by hand.
Menu only as a PDF
Google indexes PDFs, but a PDF menu loads slowly on mobile, adapts badly to a small screen and cannot carry structured data.
Not checked automatically — do this by hand.
We do not parse PDFs, so no automated check catches this. Open your homepage without images: if the menu is only a .pdf link, publish it as a normal HTML page and keep the PDF as a download.
Heavy food photos and carousels
Full-size camera photos in a hero carousel are the most common reason restaurant pages load slowly on phones.
Not checked automatically — do this by hand.
No technical check measures page weight, but every paid audit includes Lighthouse on a mobile device, which shows the LCP and page weight your photos cause. Export photos at the size they are displayed, in a modern format.
Broken or malformed tel: links
Malformed tel: links (or href="#" / javascript:void placeholders) look clickable but do not start a call.
- Dead tel:/mailto: links (Full Test)
The Full Test flags dead-anchor tel:/mailto: links. Plain-text or image phone numbers are not detected automatically — wrap real numbers in href="tel:" and tap them on a phone to confirm.
Hours and address only inside images
Text inside an image cannot be read by Google, maps or screen readers, and it cannot be checked automatically.
Not checked automatically — do this by hand.
Type your hours, address and neighborhood as real text in the footer or contact section. We cannot read text inside images.
No structured data (JSON-LD) at all
The structured-data check only reports whether any JSON-LD exists on the page — not whether it is Restaurant schema. Most small restaurant sites ship none.
- Structured data
After you have any JSON-LD, add Restaurant (or LocalBusiness) markup for name, address, cuisine and menu links as advice for richer results — that type is not what the automated check verifies.
FAQ
Restaurants questions, answered.
Is a PDF menu bad for SEO?
Google can index PDFs, but they are a weaker result: they load slowly on mobile, adapt badly to small screens and carry no structured data. Keep the PDF if diners use it, but also publish the menu as a normal page and link both.
Do you check my Google Business Profile or reviews?
No. The audit covers your public website only. Your Business Profile, photos and review replies are managed in Google, and we do not read or score them.
Will the audit tell me why my restaurant does not show up in local search?
It finds the website-side causes: thin pages, missing titles, slow mobile loading and missing structured data. Local ranking also depends on your Business Profile and reviews, which are outside the audit.
How much does a restaurant website audit cost?
The scan is free. Paid products and their current prices are listed on the pricing page; each audit is one payment for one URL, with no subscription.
How long does the free scan take?
About 30 seconds. It fetches one public URL, runs the technical checks and shows a score with the top issues. No account needed.
By platform
On these platforms?
Many restaurants sites run on one of these. The platform pages list the same problems from the platform side, with fixes written for it.
Other industries