Vegan, gluten-free and allergen searches: how restaurants get found safely

For a guest choosing around a dietary requirement, the menu is not decoration. It is the first screening tool. If the only answer is inside a PDF, an old photograph or a vague sentence saying 'options available', the guest has to call, take a risk or choose somewhere clearer.

Google says attributes can appear on Search, Maps and other Google platforms, and that adding certain attributes may help a business appear in searches for places with those attributes. Availability varies by category, country and profile; some attributes can also be informed by customer input. Review what your own profile actually offers rather than copying another restaurant's setup.

Source: Google Business Profile Help — Manage your business attributes — Google's guidance on how attributes appear, how they may affect discovery and why availability varies.

A restaurant should have one canonical, readable menu source. HTML text is easier for guests to search, zoom and translate than a photograph. It also gives search engines a clear page to understand. If a PDF is operationally necessary, publish an equivalent accessible page and keep the date or menu period visible.

Use the words guests use only when they are accurate: vegan, vegetarian, gluten-free, dairy-free, halal, kosher, nut-free or other terms all carry different meanings and sometimes certification expectations. A symbol without a legend is not enough. A filter without a clear statement about cross-contact is not enough for an allergy decision.

The operational hard part is keeping that one source in sync. The guest-facing menu, the kitchen's allergen matrix and the staff briefing sheet all describe the same dishes, yet they are usually maintained separately — which is exactly how a website ends up promising something the kitchen changed last month.

In Ireland, the public page should never become an improvised substitute for the restaurant's regulated allergen information. The Food Safety Authority of Ireland says food businesses must declare the use of 14 specific allergens in non-prepacked food. That obligation belongs inside a documented food-safety process; an SEO editor should not infer allergens from a recipe name, photograph or old menu.

Source: Food Safety Authority of Ireland — Allergens — The Irish authority's guidance on allergen declarations for food businesses and the 14 regulated allergens.

The exact legal framework changes by market. A restaurant serving guests elsewhere should use the relevant national authority and have its operational wording reviewed locally. This guide explains how search visibility interacts with allergen information; it is not legal or food-safety advice. Confirm current obligations with the relevant authority or a qualified adviser before publishing allergen wording.

A useful dedicated page answers more than 'yes'. It states which service the options apply to, whether advance notice is needed, how to contact the restaurant, when information was checked, and that staff must confirm allergy requirements. It links to the real menu and booking route. It does not pad the page with generic health claims.

Restaurant structured data can help a search engine understand basic facts such as cuisine, address, opening hours, menu URL and reservation action. Schema.org also includes vocabulary related to menus and diets. Markup must describe visible, accurate page content; it is not a hidden keyword field, a certification, or a guarantee that Google will show a special result.

Source: Google Search Central — Local business structured data — Google's supported LocalBusiness properties and requirement that structured data represents the page accurately.

Source: Schema.org — suitableForDiet — The vocabulary available for describing dietary suitability; using it does not replace operational verification.

1. 01Lead with the direct answer: what options exist and during which service.
2. 02Show the current dishes or link immediately to the relevant menu section.
3. 03Explain whether advance notice is requested and how to provide it.
4. 04State that allergy requirements need direct confirmation with trained staff.
5. 05Name the location if menus differ between branches.
6. 06Add a visible reviewed date and an owner for keeping the information current.
7. 07Link directly to booking or contact — do not leave the guest to restart their search.

Useful wording gives the guest a next step without making the decision for them. A starting pattern is: 'Please tell our team about any food allergy or intolerance before ordering. We will check the current ingredients and preparation process for your visit.' The restaurant must adapt that sentence to its real procedure and local requirements; it should not publish it if the team cannot carry out the promised check.

Measure actions rather than promising rankings. In Search Console, watch the queries and landing page impressions around the dietary page. In analytics, measure menu views, contact taps and booking clicks from that page. In the booking system, use a non-sensitive operational field for dietary notes rather than sending health information into general marketing tools. Search demand may be small, but the page can still be valuable if it answers a high-stakes decision clearly.

Written by

Alex Opsenica

Founder, Moolah Media

Founder of Moolah Media, a founder-led restaurant marketing specialist based in Ireland, working with restaurants worldwide on websites, SEO and Google Maps, and Google Ads. Around 20 years in hospitality, including hands-on restaurant management.

More about how Moolah works.