Skip to content
Vancouver RestaurantsCanada · Vancouver, BCCase study

Seven Vancouver restaurants, scored against absolute tiers

Scored against absolute tiers rather than each other. The lowest score is a documentation gap, not a quality gap.

Evaluated

7 organizations
Range across seven restaurants
4.0 → 8.2

Average of manual and structural models.

Lowest score in the field
4.0

Driven by an undocumented recurring offer.

Field leader
8.2

Menus, offers and booking paths documented everywhere.

Baseline restaurants
0

Absolute tiers, no house comparison.

Summary

Restaurant discovery runs through Google, Yelp, reservation platforms, happy-hour aggregators and AI answers. This study scored seven Vancouver restaurants against absolute visibility tiers rather than against a chosen baseline, so the field is readable on its own terms. The lowest-scoring restaurant in the set is a well-regarded room whose weekly offer simply does not exist as current, indexable source content. The leaders score highest because menus, offers and booking paths are repeatedly documented across owned and third-party surfaces.

What was measured

  • Whether the offer exists as crawlable text on the owned site.
  • Whether titles, social tags and schema describe the offer accurately.
  • Google Business Profile currency and offer awareness.
  • Listing and aggregator coverage: reviews, happy-hour directories, editorial mentions.
  • Whether the offer connects to a reservation path.

Results

Field scorecard

Priority order runs from the lowest average score upward.

PriorityRestaurantManualStructuralAverageTier
1Chambar3.74.34.0Needs improvement
2Bridges Tap & Barrel6.16.36.2Watchlist
3JOEY Burrard6.46.66.5Watchlist
4Savio Volpe6.66.86.7Watchlist
5Nightingale7.07.57.2Watchlist
6Earls7.67.87.7Leader
7Cactus Club7.98.58.2Leader
Priority fixes
RestaurantFixChannelWhyImpact
ChambarWeekly offer pageOwned siteOffer invisible to crawlersHigh
ChambarOffer and menu schemaSearch / AIParseabilityHigh
ChambarAggregator submissionDirectoriesCitation layerHigh
BridgesOwned happy-hour detailsLocation pageReduce aggregator dependencyMedium
JOEY BurrardStatic menu fallbackOwned siteJavaScript crawl riskMedium
Savio VolpeOffer and event pagesOwned siteFindabilityMedium
NightingaleOwned happy-hour pageOwned siteLess third-party relianceMedium
LeadersMaintain freshnessProfile / siteDefend positionMedium
The evidence layers
LayerStandardWhat low scorers need
Owned siteOffer exists as crawlable textA stable page with price, day, hours and a call to action.
MetadataTitles, social tags and schema describe the offerRestaurant, menu and offer schema with clean social tags.
GoogleProfile is current and offer-awareWeekly posts for recurring offers.
ReviewsListing supports review and offer languageFresh photos, menu cues and an editorial pitch.
AggregatorsDirectories validate the offerConsistent hours, pricing and items submitted.
BookingOffer connects to a reservationDeep links from the offer to the booking path.
FreshnessA dated proof trailWeekly profile and menu updates.

Findings

  • An offer that only exists on social does not exist to an answer engine.
  • Aggregator strength can carry a weaker brand story further than a strong brand story with no source page.
  • JavaScript-only menus are a crawlability risk; a static fallback is cheap insurance.
  • The leaders are not more creative — they are more repeatedly documented.
  • Recommendation logic follows the score: fix owned source clarity before asking aggregators or AI systems to cite the offer.

What the sector should fix first

  • Publish every recurring offer as a dated, crawlable page on the owned site.
  • Add restaurant, menu and offer schema before spending anything on distribution.
  • Submit consistent hours, pricing and items to the directories your customers actually check.
  • Give each offer a direct route to a reservation.
  • Keep a weekly freshness cadence; staleness reads as closure.

Limitations

  • Publicly observable evidence only. Private analytics, internal process and unpublished work are outside scope.
  • Point-in-time measurement. Scores reflect the evidence visible on the evaluation date.
  • Scores are comparable within this study and this methodology version only.
  • Seven restaurants is a snapshot of a market, not a census.
  • Scores are absolute-tier reads; they are not adjusted for restaurant size or format.

Sources, inclusion and corrections

  • Vancouver Restaurant Benchmark, Phase 1 snapshot, 2026 — manual and structural scorecards.
  • Direct site fetches, profile checks and aggregator listing reviews across the seven-restaurant field.

Inclusion in a Brand & Signal benchmark is not an endorsement, and the organizations evaluated are not clients, sponsors or partners of the benchmark. Evaluation is unsolicited and based on publicly observable evidence.

Any organization may request a correction. We review the evidence, and where a factual error is confirmed we republish with a dated change note. Corrections address factual accuracy only — scores cannot be purchased, negotiated or removed, and no commercial relationship changes a result.