Mongolie Grill has been operating in Whistler Village since 1996 and has the foundations of an SEO programme in place. The site is reachable, indexable, returns valid HTTP 200 responses, has HTTPS, a published sitemap, and is hosted on Flywheel with Fastly CDN. Tripadvisor, Yelp, OpenTable, Facebook and Instagram profiles all exist and are linked from the site footer.
The layer of structured data, on-page signals, and analytics that Google and AI engines now use to identify and rank a local restaurant is incomplete or out of date. The homepage H1 reads "Happy Hour" rather than identifying the restaurant. The menu is delivered as image files. The analytics tag is a Universal Analytics property that Google retired in July 2023. There is no Restaurant or Menu schema markup anywhere on the site.
The majority of issues identified can be resolved in under a day. A two-week implementation effort would lift the overall score from 42 to approximately 70.
Original photographs of food and the dining room appear on the homepage. The site contains no first-person content, no kitchen narrative, and no founding history. The thirty-year independent ownership angle is the strongest underused trust signal available to the brand.
No named individuals appear anywhere across the twelve indexed pages. The head chef, owner, and front-of-house team are not introduced or credited. Google's Quality Rater Guidelines (September 2025) require demonstrated expertise to be attached to identifiable people. AI engines decline to attribute claims to an unnamed entity.
The phrase "Voted Whistler's best!" appears in the meta description without an on-page source. No press citations, awards with dates, Tourism Whistler directory listing, or Wikidata entry currently exist. Five social profiles are linked from the site footer but none are declared in the schema sameAs property.
Name, address and phone information is present but appears in three different formats across the site. The /safety/ page references the April 2022 vaccine card mandate that has not been in effect for four years. No privacy policy is published, which is a PIPEDA requirement in Canada. Per-weight pricing on the homepage ($6.80 per 100g) does not match the menu page ($6.40 per 100g).
The website loads correctly, returns valid HTTP 200 responses, ranks for the brand name in Google, and has a working OpenTable reservations link. Hosting is on Flywheel with Fastly CDN. Tripadvisor, Yelp, OpenTable, Facebook and Instagram profiles all exist and are linked from the site footer. The basic technical foundations are in place: HTTPS is active, a sitemap is published, all sitemap URLs are indexable, and there are no manual Google penalties.
Three changes in restaurant search since this site was last meaningfully updated affect the recommended work below.
First, Google leads almost every "restaurants in [city]" query with a Map Pack. The Google Business Profile, not the website, is the primary surface that potential customers see. Second, AI assistants (ChatGPT, Perplexity, Google AI Overviews, Apple Intelligence) now answer queries such as "best stir fry in Whistler" or "vegan restaurants Whistler" inline, and they require structured data (Restaurant and Menu schema) before they will reliably recommend a specific restaurant. Third, the majority of restaurant searches now happen on mobile, with tourist queries weighted heavily toward fast, scannable answers.
The recommended work falls into two tracks:
• AI Search Readiness: Restaurant, Menu, and LocalBusiness schema markup; an llms.txt file; a Wikidata entity record; an AggregateRating block populated from live Google or Tripadvisor data; named individuals for E-E-A-T compliance.
• Google Search Improvements: heading hierarchy fixes; consistent NAP across the site; new pages covering catering, vegan menu, private events, gift cards, and a privacy policy; Core Web Vitals improvements; internal links pointing to the menu page.
The two tracks share most of their underlying work. Schema markup contributes to both Google rich results and AI citation. NAP consistency is read by Google Maps, Apple Intelligence and Bing Places. Adding Restaurant and Menu schema is the single highest-impact item in either column.
Mongolie Grill | World Famous Stir-Fry in Whistler Village, Since 1996. Demote "Happy Hour" to an H2 or H3 inside its own promotional section.
WebPage and Organization schema stub on every page. The site has no Restaurant, LocalBusiness, Menu, MenuSection, MenuItem, AggregateRating, ReserveAction, openingHoursSpecification, or PostalAddress markup.["Restaurant","LocalBusiness","Organization"] entity. Populate address, geo (50.1153798, -122.9546316), telephone, openingHoursSpecification, priceRange, servesCuisine, acceptsReservations, areaServed, foundingDate, sameAs (the five social profiles), and hasMenu. Ready-to-paste JSON-LD blocks are included in the schema sub-report.
/safety/ page has a last-modified date of 22 February 2022 and continues to reference Whistler's vaccine card mandate. That mandate ended in April 2022. Four years of stale content on a public page acts as a trust-signal failure. It implies the site is no longer actively maintained, raises the question of whether other content is also out of date, and confuses tourist visitors making same-day dining decisions.
/find-us/. Alternative: rewrite the page as a current "Food Safety and Allergens" page covering kitchen practices, allergen handling, and dietary accommodations.
UA-127048562-1 is still in the page source, sending data to a property that has been deprecated for nearly three years. There is no GA4 replacement firing. The business has no usable analytics data and cannot measure the impact of any of the work in this report until this is fixed.
gtag snippet via Elementor's custom code. Remove the UA-127048562-1 snippet from header.php, theme code, and any Elementor settings. Verify with the GA4 Realtime view.
/food-bar-menu/ page contains six images with empty alt="" attributes. The actual menu (40+ ingredients, 12 sauces, by-weight pricing) is rendered inside those PNG screenshots and is not present in the page text. Search engines, screen readers, and AI engines therefore cannot read the menu. The most valuable page for restaurant SEO is, from a crawler's perspective, blank.
Menu, MenuSection, and MenuItem JSON-LD with name, description, offers.price, suitableForDiet (vegan, gluten-free), and allergen tags./food-bar-menu/ appears in the sitemap but has zero internal links pointing to it from any other page on the site. The most important URL for restaurant search has no internal authority flowing to it. Google sees an isolated page; users have to find it through navigation alone.
/reservations/ and /find-us/.
<title> tag, which appears in the SERP and the browser tab) on the reservations page is "Reservations - Follow up on social media". The page itself contains an OpenTable redirect surrounded by social media icons. There is no embedded reservations widget, no party-size guidance, no walk-in policy, no cancellation information, and no phone fallback.Reservations | Mongolie Grill Whistler.ReserveAction schema linking to the OpenTable URL.
201 – 4295 Blackcomb way – Whistler (lowercase "way", no postal code)201 - 4295 Blackcomb Way, Whistler BC (no postal code)4295 Blackcomb Way #201, Whistler, BC V0N 1B4, Canadatel: URI. Google, AI engines, and citation directories use NAP consistency as a primary local trust signal. This kind of fragmentation actively suppresses local rankings.
#201, 4295 Blackcomb Way, Whistler, BC V0N 1B4, with phone +1 604 938 9416 and the matching tel:+16049389416 link. Update the site footer, contact card, schema (once added), Google Business Profile, Yelp, Tripadvisor, OpenTable, Apple Maps, and Bing Places.
/llms.txt returns 404. There is no curated entity summary for AI systems. Combined with the missing Restaurant schema and empty sameAs, AI engines have to reverse-engineer the business from raw crawl data, and most do not. There is also no Wikidata entry for "Mongolie Grill" (verified absent via the Wikidata API), which is a low-cost, high-leverage AI grounding signal./llms.txt at the site root containing an entity summary, the founding year (1996), address, phone, hours, OpenTable link, walk-in policy, dietary options, pricing, and links to the menu and other key pages. A draft is included in the GEO sub-report.Allow rules in robots.txt for ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Applebot-Extended, CCBot, and Google-Extended.https://mongoliegrill.com/Find-Us/ (uppercase F and U) responds with HTTP 200 and serves the same content as /find-us/. This creates a duplicate-content variant. Google has to choose a canonical and may split link equity. Combined with missing security headers (no HSTS, CSP, Permissions-Policy or X-Frame-Options), this points to legacy WordPress URL handling that has not been hardened.
.htaccess or a PHP filter. Add HSTS, Permissions-Policy and X-Frame-Options headers in the same change. Verify with curl -I https://mongoliegrill.com/Find-Us/; the response should be 301.
en_US. This signals US English to Facebook, LinkedIn, Apple Intelligence, and other consumers of the OG protocol. The business is in Whistler, British Columbia. The correct locale is en_CA. This is a localisation bug that affects social previews and AI entity disambiguation.
og:locale meta tag directly via the Yoast filter wpseo_locale.
/privacy-policy/ URL exists on the site. Canada's PIPEDA (Personal Information Protection and Electronic Documents Act) requires any commercial organisation that collects personal information, including via a contact form, reservation submission or feedback form, to publish a privacy policy. Mongolie Grill collects all three. Beyond the legal exposure, the absence is also a Trustworthiness signal failure for both Google and AI engines.
/privacy-policy/, link to it from the footer of every page, and reference it in the schema publishingPrinciples property.
slide-1.jpg, a 125 KB JPEG declared as a CSS background-image inside post-2.css. It is not preloaded and not converted to WebP. Meanwhile fetchpriority="high" is applied to the logo, a 13 KB PNG that loads quickly regardless. Estimated mobile Core Web Vitals: LCP 3.8 to 5.5 seconds (Poor); INP 350 to 600ms (Poor); CLS 0.10 to 0.20 (Needs Improvement).slide-1.jpg to WebP or AVIF and replace the CSS background-image with a <picture> element so it can be preloaded with fetchpriority="high".fetchpriority="high" off the logo.$6.80 per 100g; the menu page advertises $6.40 per 100g. This is a 6% price discrepancy on the same site, visible to anyone comparing the two pages. It is both a customer trust failure and a Trustworthiness signal failure for E-E-A-T. AI engines decline to cite contradictory pricing. Users tend to assume the higher figure and are annoyed by either.
Menu schema in the same change.
AggregateRating in schema to ground the claim.
Award schema; or (b) remove the claim entirely and replace it with a live AggregateRating populated from Google, Tripadvisor or Yelp, all of which already hold genuine review data for this restaurant.
/about/ page that introduces the owner(s) and the head chef. Include each person's name, role, time at the restaurant, professional background, signature dish, and a real photo. Add a Person schema entity with sameAs pointing to LinkedIn, Instagram, or any chef-association profile. Repeat for the head chef. Reference both individuals in the Restaurant schema's employee property.
/catering/: corporate and large-group revenue/private-events/: group dining capture/order-online/: takeout intent/gift-cards/: gifting demand/vegan/ or /vegan-menu/: captures "vegan whistler" tourist intent/about/: the thirty-year history/privacy-policy/: PIPEDA legal requirement (covered separately above)/food-bar-menu/ and /food-drink/ are near-duplicate pages that cannibalise each other, and /thank-you-for-your-feedback/ should be noindexed and removed from the sitemap.
noindex, nofollow meta to the thank-you page and remove the URL from the Yoast sitemap.
Mongolie Grill has thirty years of operating history in Whistler, a real address with an active Google Maps profile, five linked social profiles, and competent hosting. The fundamentals are intact. What is missing is the layer of structured data, current content, named individuals, accurate analytics, and a working reservations flow that Google and AI engines now use to identify and rank a local restaurant.
Sprint 1 alone, which fits inside a single day of work, lifts the score by sixteen points. Sprint 2 adds the schema and AI surfacing that drives the largest visibility gains. By the end of Sprint 3 the site is in genuine shape to compete for tourist intent in the most-searched Canadian dining destination.