Squarespace vs Custom Restaurant Websites: The Commission & Menu Balance.

1. The Mobile Menu Experience

More than 80% of dining website traffic happens on mobile devices. Guests are checking menus while commuting, standing outside, or deciding where to meet friends.

When a venue uploads a print PDF menu to a website builder, mobile users are forced to download a large document and pinch-zoom to read tiny text. A responsive HTML menu renders instantly, adapts to any screen size, and can be crawled directly by search engines for dietary keywords like “gluten-free pasta” or “vegan tasting menu”.

2. The Direct Booking vs Aggregator Dilemma

When a guest visits your website, the primary goal is capturing a direct reservation. If the booking widget is hidden behind multiple clicks or redirects to an external portal, many diners fall back to third-party aggregator apps (OpenTable, Resy, Deliveroo).

While aggregators are valuable for initial discovery, paying £1.50 to £2.50 per cover on guests who already intended to visit your venue represents significant margin erosion:

• Just 30 covers per week diverted = £45–£75 weekly fee
• Annual cost: £2,300 to £3,900+ per year in unnecessary third-party fees

A clean, bespoke website with an embedded direct booking workflow ensures that guests book on your terms, with 100% of guest data captured for your venue.

3. Structured Schema for Local Search

Google Maps and local search engines rely on Restaurant and Menu Schema.org metadata to understand opening hours, price bands, cuisine categories, and current menus. Custom code allows full, granular schema implementation that feeds search engines clean, structured data.