Local Search and Map Visibility Disputes

There is no single local ranking

Start here, because it disposes of much of what gets asserted in these matters. Google states three local ranking factors: relevance, how well a profile matches the search; distance, how far each business is from the searcher; and prominence, how well known a business is, based on factors including links, reviews and ratings. Google also states there is no way to request or pay for better local ranking, and that where a user does not share a location, Google uses what it knows about it.

Because distance is an input, the same query returns different orderings at different points on the map. It follows that “the business ranked third” has no determinate meaning without the coordinates at which the measurement was taken. That single observation defeats a large share of the rank evidence offered in local disputes, and it does so from Google's own documentation.

Three consequences follow. Rank evidence has to be geo-specified: a defensible exhibit is a grid of measurements at a stated set of coordinates, radius and spacing, on a stated date, for a stated query, with the method disclosed. Damages cannot be scaled from a single rank, because visibility is lost across a surface weighted by where the customers are, and that weighting comes from the business's own records rather than the grid. And a defendant will argue any observed difference is an artifact of where the measurement was taken.

The two policy documents everything is measured against

Business Profile disputes are measured against two published documents: the guidelines for representing a business on Google, and the prohibited and restricted content policies for Maps contributions. Both are public, both are dated by their archived versions, and both convert vague allegations into fact questions.

From the representation guidelines: a business must have a physical location customers can visit, or travel to customers, with in-person contact required. The name must reflect the real-world name used consistently on the storefront, website and stationery — excluding marketing taglines, store codes, trademark symbols or capitalized words, hours, phone numbers or URLs, characters not on real-world signage, and service, location or containment descriptors. Post office boxes and remote mailboxes are not acceptable, nor are virtual offices unstaffed during business hours, and businesses must maintain permanent fixed signage at the address. Service-area businesses should have one profile for the central office with a designated service area, and should hide the address.

Read that as a list of testable propositions, because that is what it is. Was there permanent signage on the relevant date? Was the location staffed? Those are answered with photographs, leases, payroll records and dated street-level imagery — ordinary evidence, not search data.

Suspensions and the appeal path

Google states it may suspend or disable profiles that do not follow its guidelines. The documented path is to open the appeals tool, select the profile, review the stated reason for the moderation action, submit an appeal with optional evidence within sixty minutes of starting, and await a decision by email. Statuses are submitted, approved, not approved, and eligible for appeal. Google lists acceptable evidence as business registration and licenses, tax certificates, and utility bills.

One instruction deserves attention, because ignoring it recurs in these matters: do not create a new profile for the same business while an appeal is under review. Creating a duplicate during an appeal is a self-inflicted aggravating fact, documented by timestamps the party cannot later characterize away.

Two cautions on vocabulary. Google's documentation does not state a review turnaround time for profile appeals, so an expert should not offer one. And the practitioner shorthand for degrees of suspension is industry vocabulary rather than Google's. Describe what happened to the profile — what was visible, what verification state it held, on what dates — rather than reaching for a category the platform does not use.

Hijacking, fake listings, and lead-generation spam

Three mechanisms get grouped under one complaint, and they need separating: the evidence differs.

Hijacking is a third party claiming ownership of a verified profile, or altering a live profile's name, category, website or phone number through the edit-suggestion mechanism or by claiming an unverified duplicate. The evidence is the profile's edit history, ownership and verification records, and archived snapshots of the field values before and after.

Fake listings are profiles created at addresses the operator has no authority to use. They concentrate in verticals where customers call the first result they see — locksmiths, towing, garage door repair — because there, position converts directly into a call.

Lead-generation spam is profiles existing only to capture calls that are then sold or routed to whichever contractor pays. The tell is that the website and phone number resolve to a call center rather than the nominal business.

Google's own enforcement is worth noting: on 19 March 2025 it announced it had sued over a network of fake Maps listings, having removed more than ten thousand illegitimate listings. Each of Google's reporting channels — reporting a business on Maps, requesting removal of a profile, reporting inappropriate reviews — generates a dated record, worth using precisely because the record exists whether or not Google acts.

Review manipulation in the map pack

Google's Maps contribution policies define the operative categories, and the definitions do useful work in a pleading. Fake engagement is content not based on a real experience or not accurately representing the location, including paid reviews, posting from multiple accounts, and emulators used to mimic genuine activity. Conflict of interest covers current or former employment, contractual or consulting relationships, and other professional or personal affiliations — the basis on which reviews from employees or competitors are removed. The policies also address impersonation and off-topic content, and prohibit merchants from offering payment or free goods for reviews.

The removal process produces its own record. Reports go through the profile or the reviews management tool; Google states evaluation typically takes several days; statuses are decision pending, reviewed with no policy violation, and escalated. Where the outcome is no violation, the owner may submit a one-time appeal covering up to ten reviews — a practical cap, worth knowing before a party burns its appeal on the wrong ten.

The map-pack dimension distinguishes this from a general review dispute: ratings feed prominence, prominence feeds local ranking, and the loss is therefore geographic rather than sitewide.

Name, address and phone evidence across sources and dates

Practitioners refer to name, address and phone data as NAP, and its consistency across directories is a routine subject of local audits. In litigation the useful question is not whether the data is consistent in the abstract. It is what each source displayed on each date, because citation data propagates with lag, and a directory showing a stale address in June may be reflecting a change made in April.

The capture method follows. For each directory and aggregator carrying the business, record the displayed name, address, phone, website and category with a dated screenshot and, where available, an archived snapshot, and preserve the submission records showing when a change was pushed.

Google's requirement that the name be the one used consistently on the storefront, website and stationery makes offline evidence directly relevant, which surprises people. Signage photographs, letterhead, invoices and the assumed-name filing are all probative on a question that appears to be about a database. Street-level imagery is particularly useful, because it carries its own capture date and speaks to the signage requirement on a date nobody chose in advance.

What the account holds, and why it has to be exported now

The Business Profile Performance API exposes daily metrics under fixed names, which makes a discovery request specific rather than aspirational: profile impressions split four ways across Maps and Search by desktop and mobile; message conversations; direction requests; call button clicks; website clicks; bookings; food orders; and menu clicks. All four impression metrics are deduplicated, so multiple impressions by one user in a day count once. The same data appears in the Business Profile Manager interface, with a settable date range and a download function.

Now the part that matters most, and it is a negative finding. Google does not document how far back this performance data goes. Neither the Business Profile Manager help page nor the API reference states a retention window or a latency figure. I will not state one either, and I would treat any confident published number with suspicion.

The practical consequence survives the uncertainty and is arguably strengthened by it: because the window is finite and undocumented, profile performance data has to be exported and preserved contemporaneously or it is gone, and nobody can tell you in advance how long you have. That is an unusual preservation posture; the ordinary assumption that a platform holds the data and it can be subpoenaed later does not hold here.

The rest of the account-held record should be captured at the same time: the profile's edit history as surfaced to the owner, ownership and verification records, Google's notification emails about suspension, reinstatement and review removals, the reviews list with names and dates, questions and answers, posts, photographs with upload dates, and messaging transcripts. Alongside it: dated grid rank measurements, archived Maps snapshots, street-level imagery with capture dates, and competitor snapshots showing name changes over time.

Causation in a local matter

Local disputes carry every causation problem the rest of this discipline carries, plus one of their own. The general ones are familiar: core updates run on public, dated schedules that frequently overlap the period of interest; the business may have changed its own site, hours, categories or service area; and local demand moves for reasons unrelated to search.

The problem specific to local is that the dependent variable is not a number. It is a surface. A business can lose visibility across half its service area while holding position at its own address — exactly the pattern a grid shows and a screenshot conceals. Any before-and-after comparison therefore has to compare like designs: the same coordinates, radius, spacing, query set, device and location settings. Where the “before” measurement was never taken to that standard, the honest report says so.

Where a matter turns on this, the measurement design and the preservation steps benefit from being settled early with counsel, because most of the material evidence is held by the party rather than the platform and is not durable. Google's representation guidelines, its statement of local ranking factors, and the performance metric reference are the documents to work from.

Frequently Asked Questions

Published 2026-08-11