Why your city-level rank is a number that lies to you
Google's local results are three things stacked: relevance (does this business match the query), distance (how far is it from the searcher or the place they named) and prominence (how well known is it, in reviews, citations, links and brand search). Google states those three openly. The second one is the reason a single rank number is worthless.
Run "dentist near me" from outside a clinic in Bandra West and it might be first. Run the same search from Khar, three kilometres away, and it can be nowhere — not because anything changed about the clinic, but because there are eleven dentists between you and it. Your agency's dashboard, checking once from a city centroid, reports position 2 and everyone feels fine.
So we don't measure that way. Around each outlet we plot 20 points, run the target searches from each of them, and record the rank per point. What you get back isn't a number, it's a shape — a map with the strong zone in the middle and the drop-off visible at the edges. When the shape grows month to month, you're winning. When it grows in one direction and shrinks in another, a competitor did something and we can tell you where.
Reading the grid report: which ring tells you what
Once you're looking at a grid instead of a number, the report becomes diagnostic. Where you're weak tells you what's broken.
| Distance from the outlet | What weakness here means | What we do about it |
|---|---|---|
| At the door, 0–500 m | Something basic is wrong: category, verification, a duplicate listing, or a suspension you didn't notice. | Fix the primary category, verification and duplicates before anything else. Nothing else matters until this ring is green. |
| Neighbourhood, 500 m–2 km | Relevance isn't carrying you past the nearer competitor. | Primary and secondary categories, services list, the review language customers use, and the landing page the profile points at. |
| District, 2–5 km | Prominence. Google doesn't consider you well-known enough to justify the extra distance. | Review velocity and recency, local citations, links to the specific location page, and branded search demand. |
| City edge, 5 km+ | Mostly brand. At this range distance is a heavy penalty and only reputation overcomes it. | This is where local SEO ends and ordinary SEO begins — organic rankings, PR and brand search do this work. |
Five outlets or two hundred: the data problem nobody wants
Single-outlet local SEO is mostly craft. Multi-outlet local SEO is mostly data hygiene, and it's unglamorous enough that it's usually the thing nobody has done.
The work splits three ways.
One source of truth for NAP
Name, address, phone — plus hours, category, and the landing page URL — for every outlet, in one sheet that somebody owns. Most chains we look at have three versions: one in the GBP dashboard, one on the website, one in a franchise operations file, and all three disagree about at least four outlets.
- Duplicate listing detection and suppression, which on older chains is often dozens of profiles created by individual managers.
- Consistent formatting across citations and directories, because Google is matching entities, not strings.
- A change process, so the next store manager who edits their own listing at 11pm doesn't undo six months of work.
Location pages that aren't clones
One page per outlet, each with something only that outlet has: staff, parking, the nearest metro station, floor-level directions, its own reviews, its own photos. If your 60 location pages differ only by the city name in the H1, you've built the exact thing the scaled content problem describes, and Google will index a fraction of them.
A store locator a crawler can use
Every outlet needs a real, indexable URL that's linked from a crawlable locator. A JavaScript map with no underlying links is invisible, and it's the single most common reason a chain's location pages never get indexed at all. For chains above ten outlets, Google supports bulk location management, which makes this considerably less painful than the manual route.
The numbers we report: calls, directions, WhatsApp taps
Local search converts differently from the rest of SEO. Someone finding a clinic doesn't fill in a form, they tap the call button. So the report is built from actions, per outlet, per month.
Two of those come from Google's own Business Profile performance data: calls, and direction requests. The third has to be built on your side. Google retired native chat on Business Profiles in 2024, so a WhatsApp tap is tracked as an event on your location page, wired into GA4 at setup. That's the number Indian clients care about most and it's the one most reports quietly omit, because it takes an hour of setup nobody billed for.
- Calls per outlet, month on month, with the seasonality noted so a Diwali dip doesn't get read as a failure.
- Direction requests — the strongest intent signal in local, and the closest thing to a footfall proxy Google gives you.
- WhatsApp taps and website clicks from the location page, tracked as GA4 events.
- Grid average rank per outlet for the target query set, plus the shape change since last month.
- Review volume, rating and response rate per outlet, because response rate is the one staff actually control.
- Outlets going backwards, named. Averages across 40 branches hide the three that are dying.
What's included, what isn't, and what it costs
From ₹40,000/mo for a single outlet, ex-GST. Multi-outlet programmes are quoted per band after scoping, and the honest reason we don't publish a per-outlet rate is that outlet count isn't what drives the work — data quality is. A 200-outlet chain with one clean feed and a franchise policy costs less to run than a 30-outlet chain with three conflicting spreadsheets and managers who edit their own listings.
What holds across every tier: month-to-month after the first quarter, 30 days' notice, no lock-in, and you keep every asset including the location pages and the profile access. The full rate card covers where this sits against SEO and the bundles.
| Included | Not included |
|---|---|
| Google Business Profile setup, category, services and attribute work per outlet | Buying reviews, or review gating that filters unhappy customers out |
| 20-point geo-grid tracking per outlet, reported monthly | Any promise of a map pack slot for a keyword |
| A written location page per outlet, not a cloned template | Rebuilding your booking, ordering or POS system |
| NAP audit, duplicate suppression and citation cleanup | Paid listing-submission packages — those buy noise |
| Review request flow, plus response templates your staff can actually use | Replying to reviews as you; we draft, your team posts in your voice |
| Local schema, store locator fixes and internal linking | Front-end development inside your site or app |
| Call, direction-request and WhatsApp-tap tracking wired into GA4 | Staffing the phone when the calls start arriving |
| Suspension and reinstatement handling if a profile goes down | Creating listings for addresses where nobody works |
What we guarantee on local, and what we won't
Three numbers get frozen on day one, per outlet: your grid average rank for the agreed query set, your monthly calls, and your direction requests. The 90-day report is against those, not against a cherry-picked week.
The company guarantee applies as it does everywhere else — we freeze your trailing-90-day qualified leads from organic search at kickoff, and if we haven't beaten that number in 90 days we keep working free until we do. On a local engagement, "qualified leads" usually means calls and direction requests rather than form fills, and we agree the definition in writing before the baseline is set, because arguing about what counted is how these promises get wriggled out of.
What we will never promise is a map pack position. The three slots move with the searcher's location, their history, the time of day and Google's own experiments. Anyone guaranteeing you the top spot in the map pack is either unfamiliar with how local ranking works or counting on you not checking from outside your own office.
If most of your demand is city-wide rather than doorstep-level, local SEO may be the wrong instrument — read local SEO versus national SEO before you commit a budget to it.