Compare rank-grid baselines with identical search settings

Define the baseline question in plain language

A useful baseline asks where one listing appears for one service phrase across a defined set of locations. Record the service intent and why those locations matter to the business. Do not start with a favorable-looking map and later choose a question that fits it. Local search is influenced by location, and a coordinate-based provider search also has explicit settings. The comparison must preserve those inputs to make a useful observational trend.

Source checks: Google Maps live advanced SERP results · Tips to improve your local ranking on Google

Save the configuration rather than recreating it from memory

Retain target identity, keyword text, grid center, generated coordinates, shape, size, radius convention, exclusions, result depth, map zoom, language, device, and provider. Record the scan time and any mode or environment details relevant to the data source. A campaign template can help preserve these values, but verify the actual repeated configuration. The same business name and colored outline are not enough to establish a like-for-like sample.

Check completion and identity before comparing

Review successful, failed, and pending states for both dates. Confirm that the target matches the same listing rather than a similarly named branch or changed identity. If unavailable points differ, compare a clearly defined common successful set or obtain a fresh comparable run. Keep whole-run completion visible. Do not count failed points as low ranks or silently remove inconvenient locations to improve the percentage.

Treat a changed question as a new baseline

A larger radius, different keyword, altered zoom, or new exclusions can be useful for studying another market question. Label it as a new configuration instead of presenting its headline score as direct performance improvement. Preserve the previous baseline for its original task. If providers use different result definitions or scoring conventions, report the switch and avoid claiming that their averages are directly interchangeable.

Separate observation from explanation

A same-settings increase supports an observation about that sampled run. It does not by itself establish that a recent profile edit, review, or website change caused the movement. Competitors, search conditions, data variation, and other business changes may also matter. Keep a change log and review point-level patterns, while using legitimate profile and content practices. Advertising spend does not buy better organic local rank, and a grid change is not customer revenue.

Use the comparison to choose the next investigation

Review which locations changed, which services still lack relevant visibility, and whether actual qualified inquiries changed in the same operational period. Inspect the business information and useful service destinations for a concrete correction. Repeat only when the next observation answers a stated question and fits the scan budget. The report should end with one evidence-based task and clear uncertainty, rather than a guarantee that a map percentage will become a fixed number of additional clients.

Worked example: illustrative figures

For example, the same 25 included points complete successfully on both dates. The target is top three at five baseline points and nine later points, giving 20% and 36% coverage. The difference is 16 percentage points; relative to the baseline it is an 80% increase in this sampled coverage. It is not 80% more customers or proof of a particular edit's impact. If the later run instead moved the center or excluded weak locations, that direct comparison would require a new baseline or an explicitly defined common sample.

Questions about this task