A 4-location restaurant chain in Riyadh, struggling with thin map-pack visibility despite strong food and a loyal walk-in base, came to RankRush in August 2025. Nine months later, monthly map-pack calls had grown from 47 to 812, with a measurable lift in dine-in covers and delivery orders. This case study breaks down what we changed, in what order, and what generalizes for other Saudi F&B operators.
By RankRush Team ·
The client (name withheld per agreement) is a 4-location Lebanese restaurant chain in Riyadh — two locations in Olaya, one in Al-Malqa, one in Al-Aqiq. Each location is a 60-100 seat sit-down restaurant with a substantial delivery business through Talabat, HungerStation, and Jahez.
Pre-engagement state (August 2025):
The client had previously worked with a generic SEO agency for website work but never had focused local SEO attention on the GBP profiles.
The client's owner described the problem clearly: walk-in business was strong (the restaurants were profitable on dine-in alone), but the chain was invisible on Google for high-intent local searches. New customer acquisition was happening through Talabat/HungerStation discovery, where margins are compressed by platform fees. The goal was simple — get the GBP profiles working as a direct customer acquisition channel, with first-party customer relationships (calls, direction requests) rather than platform-mediated ones.
Concrete success metric agreed at engagement start: 3x map-pack calls within 6 months, with a 12-month target of 10x.
The first 2 weeks were diagnostic. We audited each of the 4 profiles in detail and surfaced 31 distinct issues across them. The breakdown by category:
The biggest pattern: NAP (Name, Address, Phone) was inconsistent across the 4 profiles AND across third-party citations (Foursquare, Wamda, restaurant directories). Each profile had slight variations in the business name format ("Restaurant Beit Beirut" vs "بيت بيروت Restaurant" vs "Beit Beirut"), and the phone numbers in directories didn't always match the GBP phone.
Beyond NAP: primary categories were generic ("Restaurant") rather than specific ("Lebanese restaurant"). Photo uploads had stopped 18+ months ago — Google reads photo velocity as a freshness signal. The review request system was ad-hoc — servers were reminded "sometimes" to ask satisfied customers, but with no system or tracking.
We worked in 3 phases over 9 months. Each phase had specific deliverables and ranking checkpoints.
The phasing was deliberate. Foundation work in months 1-2 was the unsexy but essential cleanup — category, NAP, hours. These changes alone moved 2 of the 4 profiles into top-10 by end of month 2. Photo and content work in months 2-3 maintained the freshness signal and gave the profiles visual depth.
The biggest single inflection point was the review velocity system going live in month 3. Reviews per location went from an average of 1.2/month pre-engagement to 9-14/month sustained. Google's prominence signal responded within 6-8 weeks of consistent review velocity.
The call volume trajectory across the 9 months looks like this:
The pattern shows a slow build for months 1-3 (foundation work in place, but Google rankings hadn't yet responded), then sharp acceleration in months 4-6 as the review velocity and content cadence work compounded, then a tapering toward a sustained ~800/month total by month 9.
The 4 locations grew similarly but with differences — Olaya 1 and Al-Malqa benefited most from being in high-search-volume catchments, while Al-Aqiq (suburban, lower search volume) had proportionally similar growth in % terms but smaller absolute numbers.
Calls are a leading indicator, not a business outcome. The downstream business impact:
Direct GBP calls grew from 8% of new customer acquisition to 22%. This was matched by a contraction in Talabat (38% → 28%) and HungerStation (32% → 24%) discovery share — not because those platforms were doing less, but because more customers found the restaurants directly and bypassed the platform fee. The estimated annual margin impact was substantial, on the order of 12-15% of the chain's total contribution margin recaptured from platform fees.
What translates from this engagement to other Saudi F&B operators:
The same playbook applies to most Saudi F&B operators with multi-location footprints. We document the [Local SEO](/services/seo/local-seo/) approach in detail on the service page, and the [Google Business Profile](/services/google-business-profile/) hub covers the ongoing operational layer that makes the gains sustainable.
No. This engagement was purely organic local SEO work on the GBP profiles plus citation cleanup. The client maintained their existing Talabat and HungerStation paid promotion separately. We focused exclusively on the unpaid Google map pack and organic profile signals. Adding paid Snap or Meta ads on top of this foundation would compound the results further, but wasn't part of the brief.
The methodology transfers broadly to any local service business — dental clinics, beauty salons, automotive service, retail. The specific tactics adapt: photo cadence is higher for F&B and beauty than for B2B services, review velocity is critical for all service businesses, NAP consistency matters universally. We've run similar engagements for clinics, salons, and auto-repair operators with comparable trajectories. The magnitude of the lift depends on starting point — heavily under-optimized profiles see larger relative gains.
We don't publish specific pricing on case studies (each engagement is scoped to specific scope and deliverables), but for context: a 4-location GBP optimization engagement of this depth is typically structured as a 6-9 month engagement with a monthly retainer in the mid-to-upper SAR thousands range. Engagements like this typically pay for themselves within 4-6 months at this scale of business — the recaptured platform fee margin alone exceeded the engagement cost by month 6.
Yes, gradually. The structural fixes (NAP, categories, hours) remain in place permanently — those don't decay. But the ongoing signals (review velocity, photo uploads, content posts) decay if abandoned. A profile that stops review-request operations will see review velocity drop from 9-14/month to 1-2/month within 3 months, and prominence ranking will follow within 3-6 months. The sustainable model is either ongoing agency engagement or transition to in-house operations after the agency builds the systems. We typically structure engagements to transition operational work in-house by month 9-12, with the agency reverting to strategic/optimization role.
Yes — the methodology is city-agnostic. Saudi-specific elements (Arabic name handling, hijri-aware hours, Mada/Talabat platform context) apply across the Kingdom. We've run comparable engagements for restaurants in Jeddah, Dammam, and Khobar with similar trajectories. The variable that affects magnitude is competitive intensity — competitive Riyadh categories (e.g., Indian restaurants in Diplomatic Quarter) take longer to dominate than less-saturated suburban catchments. We scope engagement length based on the specific competitive landscape during initial audit.