A restaurant website has two separate jobs, and confusing them causes most of the damage we see. One job is helping search engines understand what the restaurant is, where it is and what it offers. The other is removing friction between an interested guest and a confirmed booking.
A page can be excellent at one and poor at the other. Worth separating them when deciding what to fix first.
Most restaurant websites fail Google's mobile speed checks. Why slowness costs real bookings, what causes it, and what to fix first — in plain language.
How to structure a restaurant location page that ranks and converts: address and hours in text, directions, parking, menus, structured data and booking.