Describe the restaurant’s process for receiving and confirming dietary requests using kitchen-approved wording. Explain who guests should contact and when confirmation is needed. Keep ingredient descriptions separate from assurances about an individual diner’s requirements or the preparation environment.
Publish the confirmation process
State how advance requests reach the kitchen and whether some menus need prior arrangement. Review public symbols and menu notes when recipes or suppliers change. Avoid answering a personal dietary question with an automatic promise that the operational team has not reviewed.
Keep the sector facts verifiable
The restaurant team should own current menus, service hours and reservation conditions. Kitchen-reviewed dietary information must remain connected to the actual preparation process. Avoid treating a menu symbol as a personalized safety determination, and ensure photographs and price descriptions refer to the current offer.
What to check
- Have the kitchen approve public wording.
- Explain how requests are confirmed.
- Review menu notes when preparation changes.
A practical example
An illustrative tasting-menu page asks guests to discuss a dietary requirement before booking and explains that the team confirms whether the requested adaptation is available.
Sources and further reading
- Google Search Central: generative AI search guidance
- Google Business Profile: accurate business representation
These steps are Arrow AI's implementation guidance. The example is illustrative; it is not a measured customer result. Publication and source access do not guarantee an AI recommendation.
Apply this to your website
Identify the source gaps and decide what to improve with Arrow's free audit. Review what Arrow GEO measures before choosing a reporting scope.
