What belongs on the page versus your main menu
The everyday menu page is for guests choosing what to eat on the evening. The group page is for someone planning several weeks ahead. Tasting menus, canapés, family-style platters, celebration set menus and standing-reception packages belong on the group page, while à la carte dishes, daily specials and standard drinks stay on the main menu.
If a tasting menu is also offered to individual tables, it can appear in both places with a short cross-reference. Avoid duplicating hours, location and contact details; link to the page that holds the current contact details. The point of the split is to give a planner a focused reference rather than a second homepage to scroll through.
Information to gather from your restaurant
Before writing any copy, sit down with the kitchen and front-of-house leads and capture the operational facts.
- Typical group sizes and the largest party each private room can seat.
- Layout in each room, plus any AV or accessibility notes.
- Lead time needed and whether provisional holds are accepted.
- Minimum-spend or deposit terms the venue applies.
- Set-menu or family-style options, including vegetarian, vegan and common allergen handling.
- Standing receptions, canapés or wine pairings if offered.
Example content blocks to adapt
Two patterns commonly sit on a group page. The figures and names below are placeholders only; replace them with your own details.
Private-room block to adapt:
Set-menu block for around 8 to 20 guests:
A short lead-time block can state how far ahead the room needs to be booked and when the deposit is due. An enquiry block can name the channels the restaurant accepts for groups and the information the planner should send: date, approximate guest count, preferred menu and any allergies.
- Room name: [e.g., The Garden Room]
- Capacity seated: [e.g., 12 to 22]
- Layout: [e.g., one long table, rounds of 8, or standing reception]
- Notes: [music curfew, accessibility, AV options]
- Three courses, two or three options per course
- Price per person: [starting from EUR X] or confirm by enquiry
- Dietary requirements: confirmed in the final booking
- Optional add-on: [wine pairing, canapés on arrival]
Phrasing the enquiry step clearly
Phoning the restaurant, sending an email or messaging on WhatsApp are direct ways to start a group enquiry. State on the page that a direct enquiry is not itself a confirmed reservation; confirmation, deposits and cancellation terms come from the restaurant itself.
An external booking link is a separate channel: where the external booking provider confirms reservations under its own rules, that confirmation, deposit and cancellation terms come from that provider, while direct contact remains the right route for fully bespoke arrangements.
Avoid promising a specific reply window unless that is genuinely how the team works. If the reply time varies with the season, say so and invite earlier contact for events inside the next two weeks.
Setting up and sharing the page
The restaurant-premium template ships with sample content and fictional businesses that need to be replaced with your own room, menu and enquiry details before publishing. This premium template requires a Lite SME or Business plan to publish, so make the upgrade decision before printing or sharing the page link, since the template cannot be published on a Free plan. Restaurants that only need a single menu page can use the free Simple restaurant template instead.
Once published, the page lives at a hosted address that can be shared as a link or pointed to by a QR code. A new static URL QR is created in the public URL generator: enter the page address, generate the code, then print or download it.
Keeping the page current
Set menus, prices, room photos, lead times and minimum-spend figures drift through the year. A simple review rhythm, such as a quick check at the start of each season and after any menu change, keeps the page useful.
A printed QR code that points to the page's hosted address keeps working as the content behind it is revised; only changing the encoded URL would require a new code. When something larger changes, such as a new private room or a different deposit policy, add a short paragraph that explains the change, so the page does not feel out of date before a planner reads it.
