Meridian Hospitality Group operates four upscale restaurant concepts in a major European city: a contemporary French bistro, a wood-fired Mediterranean concept, a cocktail-focused wine bar, and a private dining venue for corporate events. Each location had strong word-of-mouth reputation and consistent occupancy at peak hours. The challenge was filling shoulder-period seats and attracting first-time guests who were not arriving through referral networks.
The group's marketing manager discovered the AI visibility gap through a personal experiment: she asked Google's AI Overview, ChatGPT, and Perplexity to recommend upscale restaurants in the city for a business dinner. None of the four Meridian venues appeared in any response. Competitors that she knew to be inferior in terms of food quality and service appeared consistently. The recommendations were based on structured data signals and content architecture, not actual dining quality.
AISOS was engaged for a four-month project covering all four locations. The engagement focused on local AI visibility -- the specific signals that cause AI assistants to recommend local businesses in response to "near me" and city-specific queries. This case study documents the approach and outcomes, with reference to the broader restaurant industry AI visibility strategy and foundational concepts in Answer Engine Optimization.
The Challenge
Restaurant recommendations are among the most common queries AI assistants receive. "Where should I take a client for dinner in [city]," "best wine bar for a date night," "private dining rooms for corporate events" -- these are exactly the high-intent queries that translate directly into reservations. Meridian's locations were absent from all of them despite having the product quality and price positioning to compete at the top of every category they operated in.
The baseline audit identified three structural problems. First, the group's website used a custom CMS that had never implemented Restaurant schema or LocalBusiness schema beyond the most basic name and address fields. AI systems querying for restaurant recommendations look for machine-readable data on cuisine type, price range, ambience attributes, special features (private rooms, tasting menus, sommelier service), and current operational status. None of this was structured. Second, the group's Google Business Profile data was inconsistent across locations -- different opening hours, mismatched categories, and incomplete attribute sets. AI systems that draw on Google's local knowledge graph found conflicting data and deprioritized the venues. Third, there was no published content addressing the specific use cases (business dining, date night, private events) that were generating the competitor recommendations Meridian was missing.
The competitive loss was measurable. During the audit, AISOS tracked 40 local restaurant queries across the five major AI platforms. Meridian venues appeared in 3 of 40 (7.5%). The two leading local competitors appeared in 31 of 40 and 28 of 40 respectively. Understanding why this gap existed -- and that it could be closed -- required first grasping what AI visibility means for local businesses.
The AISOS Strategy
The strategy for Meridian was built around three parallel workstreams. The first was a complete structured data rebuild. AISOS deployed full Restaurant schema for each location, including cuisine type, price range (using both the schema priceRange attribute and explicit numerical average spend), accepted payment methods, has menu, serves cuisine, and a detailed amenities list. Menu schema was implemented for each venue's current seasonal menu, with dish-level structured data for signature items. For the private dining venue, EventVenue schema was layered on top of Restaurant schema to capture that dual-use nature.
The second workstream was Google Business Profile optimization across all four locations. This involved standardizing hours, correcting category assignments (the wine bar had been categorized as a "pub" rather than a "wine bar"), adding all available attribute fields, and implementing a systematic review response policy that demonstrated active management. AI systems that draw on real-time local data weight recency and management responsiveness as signals of venue quality. The AI SEO checklist includes a local business section that guided this audit.
The third workstream was use-case content: four dedicated landing pages, one per venue, structured around the specific dining scenarios each location serves best. The French bistro page was built around "business lunch in [city]" and "client entertainment." The Mediterranean concept around "wine dinner" and "group booking." The wine bar around "date night" and "post-theatre." The private dining venue around "corporate event catering" and "private dining room hire." Each page included the specific structured FAQ content that AI assistants use to generate location recommendations -- a direct application of AEO principles to local hospitality.
The Results
After four months, Meridian's mention rate across the 40 test queries increased from 7.5% to 62.5% (25 of 40). The private dining venue showed the strongest relative improvement, going from 0 mentions to appearing in 9 of 10 corporate event queries. The French bistro and Mediterranean concept each reached 7 of 10 for their primary use-case queries. The wine bar showed 5 of 10, with room for further improvement as Google's AI update cycles incorporated the new GBP data.
Reservation volume attributable to AI platforms increased by 52% over the four-month engagement period compared to the equivalent prior-year period. Perplexity referral traffic (directly trackable via UTM) increased from near-zero to an average of 340 monthly visits across the four venues. The private dining venue saw the most concentrated commercial impact: three new corporate event bookings in month four were sourced directly from AI assistant referrals, contributing approximately 18,000 euros in event revenue.
Google Business Profile views increased by 89% across the four locations as a secondary effect of the optimization work. The structured data improvements that benefited AI visibility also improved Google Maps recommendation placement -- an example of how AI-first optimization often lifts traditional search performance simultaneously.
Key Success Factors
The menu schema implementation was a differentiating factor. Most restaurants implement basic business information in structured data but stop there. Dish-level schema that includes ingredient information, dietary attributes (vegetarian, gluten-free, allergen statements), and price was extremely effective for AI visibility because it enables AI assistants to answer specific queries such as "fine dining restaurants with excellent vegetarian tasting menus in [city]." Meridian's chef team collaborated with AISOS to ensure the schema data was accurate and updated with each seasonal menu change.
The review response policy contributed more than initially expected. AI systems that incorporate real-time web data weight the recency and quality of business responses to reviews as a freshness and management quality signal. Implementing a structured review response policy -- 48-hour response time, personalized responses from named managers -- improved Meridian's freshness signals across all AI platforms that sample Google's local data. This is a zero-cost, ongoing practice that the group has continued beyond the AISOS engagement.
Seasonal content updates were built into the implementation plan from the start. Restaurant menus change quarterly. If the structured data does not reflect current offerings, AI systems begin generating responses that do not match reality -- and disappointed customers who arrive based on an inaccurate recommendation erode brand trust. AISOS built a quarterly schema update process into Meridian's CMS workflow so that menu data remains accurate without requiring a specialist to be engaged each season. Reach out to AISOS to discuss how ongoing maintenance is structured for hospitality clients.
Lessons Learned
The restaurant engagement demonstrated that local AI visibility is more achievable than most hospitality operators assume. The technical complexity is manageable, the content investment is modest compared to a typical marketing campaign, and the commercial return is direct and measurable through reservation tracking. The barrier is not difficulty -- it is awareness. Most restaurant operators are focused on traditional review platforms and Google Maps, unaware that AI assistants are now a significant and growing referral source for dining decisions.
The engagement also highlighted the value of use-case specificity. A restaurant that presents itself as "a great restaurant for any occasion" does not give AI assistants what they need to generate specific recommendations. An AI assistant answering "where should I take my team for a working lunch" needs to know that a specific venue is well-suited for business dining -- good acoustics, private tables available, business-friendly menu pacing. The venues that answer specific questions get specific recommendations. Generic positioning gets ignored. This is a core AEO principle that applies to local hospitality as much as to any other sector.
Finally, the Meridian engagement reinforced that AI visibility and traditional local SEO are complementary, not competing, strategies. Every structured data improvement made for AI visibility also improved Google Maps performance. Every use-case landing page built for AI citation also generated traditional organic traffic. Teams do not need to choose between optimizing for AI and optimizing for search -- done correctly, the same work serves both. Contact AISOS to see how this applies to your restaurant or hospitality business.