Winning local search for a restaurant in El Jadida.
How we rebuild a Google Business Profile around the query, not the brand story
Client
Confidential — available on request
Advertising
F&B · Local
Availability
On request
Sector
Restaurant · El Jadida
Method note
This page documents a method, not a client result. It is written in full because the approach is the reusable part of the work. The client's name and the figures from their engagement are not published yet, because they have not been cleared for publication — we would rather show the method than invent a result.


What Usually Goes Wrong
A profile is almost always written to describe the business rather than to match a search. The category is too broad, the description repeats the name, and the opening hours reflect when the owner would like the doors open rather than when the kitchen actually serves. Each of those fields is a ranking surface being left empty.
The photography answers the wrong questions. A shot of the room or the façade looks good on a laptop and tells someone hungry on a phone nothing about whether the food is any good or whether the table is worth the drive.
Reviews get treated as a launch-week task rather than a weekly one, so unanswered reviews accumulate. To a first-time visitor an unanswered review reads as an abandoned business rather than a busy one.
The Approach
Local work fails for a mechanical reason: the profile is not built for the query a hungry person types. The approach is to rebuild the listing around those queries, then connect every one of them to a way to book.
Rebuild the profile around real queries
The category was narrowed, hours were set to match the actual service rhythm, and the description was rewritten to name the dishes and the neighbourhood rather than to repeat the business name. Every field was treated as a search result in its own right.
Photography that answers the visit
Menu photography was shot to be legible at thumbnail size, and the interior was photographed because the most common question before booking a Moroccan restaurant is what the room looks like. Both were uploaded at the resolution a phone actually requests.
Reviews as a first-week priority
Every existing review was answered, and a system was put in place to ask for one at the moment of highest satisfaction rather than at checkout. Reviews are the only third-party signal in local search, and unanswered ones are worse than few.
One tap from map to table
The profile was configured so that direction requests, a call and a booking link were all one interaction away. The metric that mattered was not impressions but the direction request, because that is a person already deciding to come.
What We Measure
This page documents the method and the measurement frame rather than a result set. The restaurant's name and figures are published once clearance is in place. What follows is what we measure and how each signal is read.
Visibility
Rank across the target query set
Intent
Direction requests per month
Reputation
Reviews, answered weekly
Visibility in Maps
- Map views are read before and after, never off a trend line on its own — local gains are seasonal and a single month tells you very little.
- Rank is read across the whole target query set rather than for one keyword, because nobody searches with a single term and behaves as though they had.
- The share of impressions arriving from discovery rather than direct search is what shows a profile being surfaced, not merely found.
Physical intent
- Direction requests are the metric that counts, because each one is a person who has already decided to come.
- Direct calls and bookings started from the profile are reported separately; in a city where people reserve by phone, a call is often a better signal than a booking.
- Nothing above the intent line is treated as a result, impressions included — those are a marketing number rather than a business one.
Reputation
- New reviews per month once the ask system is in place measures the system; the running total since opening measures how long the restaurant has existed.
- Average rating is read at the start and the end of the period, with the response rate reported alongside it, because an unanswered review costs more than a mediocre score.
What Makes It Work
- The profile was rewritten for the query, not for the business's own description of itself
- Photography answered the pre-visit questions instead of decorating the page
- Reviews were treated as a weekly task rather than a launch-week task
- The success metric was the direction request, which is the closest thing local search has to a sale
Conclusion
Local work is almost entirely mechanical, which is exactly why it is worth writing down: a profile is a set of ranking surfaces, and the only metric that counts is a direction request. This restaurant's figures are not published because the owner has not cleared publication. When they do, this page is updated in place with the measured values and the comparison window.
More method notes

Social Media
Running a social channel for a Moroccan fashion label

Full System
Rebuilding a B2B paid pipeline around closed revenue