My business is not showing on Google Maps… from across town

You almost certainly do show up — the problem is where people search from

My business is not showing on Google Maps almost never describes what is actually happening. What usually sits behind it is a very specific scene: a customer told you they looked you up and could not find you, you tried it on your phone and came up first, and now you do not know who to believe. You are both right. You searched standing inside your store. Your customer searched from their office four miles away, with thirty businesses in your category between the two of you.

The Google local pack — those three map results at the top — is not a fixed list that sorts the same way for everyone. It is assembled at query time, and one of the heaviest signals is where the searcher is standing. Which means there is no such thing as “your Google Maps ranking” as a single number. There is your position for this keyword, from this point, at this moment. Change any of the three and the result can change with it.

That is why the question most people arrive with is badly framed, and not through any fault of their own. The pages that rank for why am I not showing up on Google Maps all repeat the same six-item list — verify the listing, complete your info, add photos, get reviews, pick the right category, post updates — and none of them ever asks where the person who could not find you was standing. You leave with tasks but no diagnosis, you do all six, and a month later the customer across town tells you the same thing.

This post runs the other way. It first splits the case into two branches that have nothing in common: the binary failure, where you are excluded from the query for a concrete verifiable reason, and the coverage question, where you are included but only inside an area around your location. The first branch gets fixed. The second gets measured, bounded, and sometimes widened a little — but it does not get “fixed”, because it is not broken. Confusing the two is what costs people months.

One clarification up front: geography also shapes your organic results, not just the map, though with different logic and at city rather than neighborhood scale. We cover that side in the guide to tracking rankings across multiple cities. Here we stay inside the local pack. And if you want the overview of what can be measured continuously on each surface, it is summarized in the Rankiamos feature breakdown.

The Google Maps proximity algorithm is not a bug you fix, it is a radius you measure

Google has said for years that local results are ordered by three factors: relevance (how well your listing matches what was searched), distance (how far you are from the search point or from the area named in the query) and prominence (how well known the business is, online and off). What people call the Google Maps proximity algorithm is not a separate system — it is the weight of that second factor. And that weight is not constant.

The intuition is easy if you put yourself in the search engine's shoes. If someone types “bakery” while standing downtown, showing them an outstanding bakery fifteen miles out is a bad result no matter how good the bakery is: they want bread now and they are not driving across the metro. Distance dominates. If someone types “fertility clinic” or “immigration attorney”, the logic inverts. There are few providers, the decision is expensive, and the searcher genuinely will travel. Google widens the area it considers and prominence starts to matter far more than miles.

Which gives us the core idea of this post: every business has an effective visibility area, and the width of that area is not up to you. It is set by your category, the density of competitors around you, and your strength relative to them. These three scenarios cover most real cases.

None of this is an excuse to do nothing. It is a frame for deciding where the effort goes. If your category is dense, spending six months trying to “show up across the city” is burning money. If your category is sparse and you are invisible six miles out, something is wrong with the listing and the radius is not to blame. The only way to know which case you are in is to stop arguing about it and measure it, which is where the next sections go.

Before reading anything as a distance issue you have to rule out the binary failures. They are called binary because they do not lower your position — they remove you. If you have one of these, it makes no difference where people search from, which is why they come first. When somebody says Google Maps cannot find my business even by its exact name, the cause is almost always in the top three rows of this table.

This is the triage to run in one sitting, top to bottom, without skipping rows. Each one has a way of being verified that does not depend on your opinion.

Notice the logic of the table. Rows 1 through 3 are binary and their effect is total. If your listing is suspended you appear nowhere, and no volume of reviews compensates for it. Row 3 is the one most often missed: the primary category behaves like a hard filter, so if you run a motorcycle repair shop and picked plain “auto repair shop”, you may be entirely outside the candidate set for “motorcycle repair” rather than sitting in a low position. It is an eligibility failure wearing the costume of a ranking failure.

Row 4 is the hinge between the two branches, which is why it sits in the middle. A misplaced pin — extremely common in malls, office towers and areas with confusing addressing — does not remove you from the map, but it makes Google calculate your distance from a point that is not your front door. If your marker landed half a mile off, your whole radius shifts: you will show up well for people far from you and badly for people standing across the street. It is one of the few items on this list that takes ten minutes to correct and changes the outcome immediately.

Rows 5 and 6 are gradual, and that is where the other problem starts. Watch out for the most common logical trap: because those two rows are never finished — you can always chase another review, always land another mention — it is easy to stay there forever, doing things, with no idea whether any of them worked. That is precisely the moment to stop optimizing blind and start measuring.

How to turn a vague “I don't show up on Google Maps” into data

Here is the step almost nobody takes. A complaint cannot be verified; a statement can. As long as the problem stays “I don't show up”, there is no way to know whether anything improved, and every conversation with your team or your client ends in opinions. The point of this section is to walk out with a sentence that can be true or false, and that you can re-check a month from now.

Six steps, about an hour, most of it on paper. This is not yet the mechanics of measurement — how often to check, how the series is recorded, what makes two checks comparable — which is a separate and considerably longer subject. This is the protocol that comes before it: writing the problem down in a form that can be measured at all.

1. Step 1 · Write the exact query, not the category

   “I don't show up” is not a query. “Dentist” is not one either — nobody searches like that. Write the three or four literal phrases you believe people use, exactly as a customer would type them, including the ones with an area in them: “dentist near me”, “dentist downtown Miami”, “orthodontist north side”. If you have no idea which ones they are, the most honest source is your own front desk: ask what people say they searched for.

2. Step 2 · Separate branded queries from generic ones

   They are two different problems and mixing them ruins the diagnosis. If you do not show up when someone searches your business name, you have a binary failure from the table above, no debate. If you show up by name but not for the generic category, your listing exists and works: what you are facing is competition and distance. Never use a branded search to conclude that “everything is fine”.

3. Step 3 · Name the areas where showing up actually matters

   Not “the whole city”. Two or three specific areas that already send you customers or that you want to, chosen on business grounds: where your highest-spending clients come from, where the competitor that worries you is, how far you can realistically serve. This short list is what will later define how much quota you need and how much work is worth doing.

4. Step 4 · Run the five-minute test

   Search your generic query plus your own neighborhood, from inside your business. If you do not show up there either, stop: you do not have a radius problem, you have a listing problem and it is back to the table above. You are failing in the exact place where distance works for you, and no coverage strategy makes sense until that is resolved.

5. Step 5 · Turn every area into a row

   One row per query-and-area combination, with a column for position and one for the date. Even if you can only fill half of it today, the format is what matters: it converts “I don't show up” into “for this query, in this area, I have been outside the top 3 for six weeks”. The second sentence can be defended in front of a client. The first cannot.

6. Step 6 · Define the threshold before you look at the result

   Write down what counts as success before you have the data: top 3 in two of your three priority areas within ninety days, for example. Defining it afterwards is cheating yourself, because you will always find a number that looks good. Set the minimum window too: the local pack drifts on its own, and a single measurement is not a trend.

With those six rows written down you have a diagnosis instead of a complaint. The mechanical part — how that position gets recorded in a comparable way, how often to check, and how much history you need before deciding anything — we handle separately in the local pack measurement guide, because it carries enough substance of its own. If what you are dealing with is a drop rather than an absence, the criteria for separating noise from a real decline are in the post on telling a real ranking drop from normal volatility.

Compare your radius against whoever does show up in that area

An isolated data point says nothing. Knowing you are outside the top 3 in an area five miles away is not very useful. Knowing that the business that does rank there is even farther away than you are — that is useful. It is the only contrast that turns your log into a decision, and it is the question to ask for every area on your list: who has my spot, where are they, and why does their radius reach?

There are three possible answers and each one leads somewhere different. First: whoever ranks is clearly closer to the search point than you are. Then nothing is broken, distance did its job, and your only real lever is building enough prominence to offset the miles — which in dense categories rarely pays off. Second: whoever ranks is roughly as far away as you, or farther. Now you have something to attack, because if distance is equivalent and they appear and you do not, the difference is in relevance or prominence, and both can be worked. Third: whoever ranks is farther away and has fewer reviews than you. When that happens, suspicion swings back to the listing — primary category, pin, duplicates — and it is worth re-reading the triage table before deciding Google is being unfair.

This exercise also has a side effect nobody expects: a competitor you were not tracking almost always shows up. Not the historic rival, but a newer business with a very well built listing quietly taking the queries in two or three areas. Catching that early is half the value of measuring. The other half is finally letting go of a competitor who has not actually been taking anything from you for a while.

For the comparison to mean anything it has to be consistent: same query, same reference area, same cadence. If one month you check from downtown and the next from the north side, you are not comparing anything. It is the same principle that makes searching for yourself useless as a measurement — without fixed conditions there is no series, and without a series there is no conclusion. On the organic side the same problem is solved by fixing the city of the query, which we walk through in the guide to per-city rankings for a single domain.

What can move and what cannot: honest expectations about the radius

This section exists because it is the one missing from nearly everything written on the subject. Nobody tells you what you will not achieve, and that omission is what leads a business to spend a full year chasing a result that was never on the table.

The general rule: what you can correct is your eligibility and your relative strength. What you cannot correct is where your business physically sits or how many competitors stand between you and the searcher. With that in mind, here is how it divides.

There is a temptation worth naming out loud because it circulates a lot: creating fake addresses, using a relative's house on the other side of town, or renting a mailbox to “extend coverage”. Beyond being a direct violation of Google's policies, the usual ending is a suspension of the main listing — trading a radius problem for a binary one where you stop appearing anywhere at all. This is not a gray area. It is the worst trade available.

The boring, effective alternative is to accept the frame and play inside it: make sure your natural radius is clean, push prominence consistently, go after the area-named queries where you genuinely can compete, and measure so you know which of those things is working. Not spectacular, but it is the only thing that holds a result over time.

The practical objection always lands at the same point: if I need to see my position in several locations, am I going to be charged for each one? In many tools, yes. The usual model multiplies — the same keyword measured in three cities bills as three keywords, and if mobile and desktop are separated too, as six. That billing detail decides whether a plan works for you far more than the feature list on the sales page does.

In Rankiamos the model is explicit and worth understanding before you subscribe: every keyword-by-city combination consumes one unit of your quota. The plan price does not go up when you add cities — there is no per-location surcharge — but the quota does get used. And there is one point where the model breaks from the rest of the market: on Pro, mobile and desktop share the same unit, so measuring both devices doubles nothing (Free measures one device of your choice). Here is how the math works out on the current plans.

The reading of that table is the discipline the model imposes: quota is finite, so the short list of areas from step 3 stops being an exercise and becomes a real constraint. Watching five queries across five cities costs twenty-five units; expanding to twenty queries on a whim leaves you with no room. Choosing what you measure is part of the work.

One platform note that also belongs up front: Rankiamos runs on iPhone, iPad, Mac and Apple Watch, and the app interface is in Spanish only. There is no web version and no Android app, no client login to a portal, and no automatic report delivery. What you can do on Pro is export a PDF with your name and your color, or an unbranded CSV, and share it yourself from the iOS share sheet. Plan quotas and prices are on the pricing page.