Restaurants and hospitality groups

In hospitality almost everything is decided on the Google map, two hundred metres from the door and fifteen minutes before lunch.

The map matters more than the website

The typical search is "restaurant near me" or "where to eat in [neighbourhood]" from a phone, and what appears is the map pack. Distance, recent reviews and how complete the profile is decide it. An excellent restaurant with a neglected listing loses to a mediocre one that maintains theirs, and this is fixable in weeks, not months.

Reviews: volume, freshness and replies

It isn't just about having many. It's that they keep arriving and that you reply to all of them, including the bad ones. We set up a simple way to ask without being irritating (a QR code on the bill beats any campaign) and give you reply templates in three languages so the team isn't improvising.

Your menu has to be text, not a picture

Half the sector uploads the menu as a PDF or an image, and Google can't read it. That means you don't appear when someone searches "squid ink rice [neighbourhood]" or "vegan restaurant [neighbourhood]". A menu in HTML, with dishes as real text and marked up with structured data, is one of the highest-return things you can do in this sector.

Common questions

I have three venues. Do I need three websites?

No. One site with a page per venue, each with its own Google listing, address and hours. Three separate domains split your authority and triple the work for nothing.

Can you get my reviews up?

We can build the system for asking and replying, and that nearly always multiplies the rate they arrive at. What we don't do is buy them: Google detects it and the penalty is worse than the problem.

Is SEO worth it for a seasonal venue?

Yes, but with the calendar in hand. The work happens in winter so you arrive at May already ranking, not in July when half the season is gone.