Guide
How do I run a repeatable local search ranking check?
Freeze the query, language, search location, device and session, grid design, result cutoff, and run date before every check. Repeat those settings for the next run, record the observed result at each declared point, and keep the Google Business Profile Performance report in a separate record. A grid is a sample of map-point observations, not a Google-issued universal rank.1,2,3
This is the operational companion to tracking your local search rankings. That answer explains which instrument answers which question. This guide gives you a monthly worksheet for running the local observation and the profile report without blending their numbers.
What does this monthly check actually measure?
Use two records, and add a third only when the website's web-search performance is also part of the question.
| Record | What it tells you | What it cannot tell you |
|---|---|---|
| Local observation or geo-grid | Where the profile appeared for the declared query at the declared map points and time1,4 | The position every customer sees, a universal local rank, or the reason a result changed |
| Google Business Profile Performance report | Profile searches, views, and available actions for its selected date range2 | Where the profile appeared on a map or how many grid points showed it |
| Google Search Console Performance report | Website clicks, impressions, click-through rate, and average position in web Search3 | A Business Profile position, a Local Pack position, or a map-point result |
Google says local results are mainly based on relevance, distance, and popularity. It also says that distance is measured from the searching customer and that the ranking system details are confidential. A repeatable worksheet controls the context of an observation; it does not reveal Google's ranking formula.1
What should I freeze before I run the scan?
Write down the following fields before starting the scan. These are measurement controls for a comparable observation, not Google requirements.
| Field | Record before the run | Why it matters |
|---|---|---|
| Query | The exact search string, language, search type, and whether it is branded, non-branded, or location-specific | A changed query measures a different search question. |
| Location | Grid center or target point, point coordinates, spacing or distance, and the neighborhood or service area being sampled | Google says location affects nearby results. A grid location is a sample location, not one official business location for every searcher.1,5 |
| Device and session | Device type, browser or app, signed-in state, and the location source being used | Google names time, place, device, and recent history as result context. Record the session instead of calling one device neutral.3 |
| Grid design | Grid dimensions, active points, target, spacing or distance, and tool or report ID | The points and design define the sample you observed. A later scan must use the same design for a clean comparison. |
| Cutoff | The result cutoff shown by the tool and the exact rule for “not found” | A cutoff is a worksheet choice. Do not present it as a Google threshold. |
| Run date and time | Start and end time, timezone, tool run date, and any report comparison period | Time is part of search context. A report date range is different from the timestamp of a grid observation.3 |
If the tool lets you choose the points, save the coordinates or a report export. BrightLocal's Local Search Grid documentation lists custom points, grid sizes from 3×3 through 15×15, adjustable distance, and a movable target. It describes 5×5 as a starting point for most local businesses, but that is BrightLocal's recommendation, not a Google standard.4
How do I run the local observation?
- Create the run record. Give the check an ID and fill in the frozen fields above before opening the report.
- Run the exact query. Use the declared language, device or app, session settings, and target location. Do not silently add a second query because the first one looks unhelpful.
- Run the same query at each active point. Save the point, result position as the tool reports it, business name or profile identifier, cutoff, and whether the business was not found under that cutoff.
- Save the raw report. Keep the tool name, report ID, run date and time, export filename, and a screenshot or export when available. The report is evidence of those declared observations.
- Label anything that changed. If the query, point set, device, grid, cutoff, or comparison period changed, apply the matching design-change label before comparing the result with the previous run.
The result is a map of the declared checks. It is not proof that a profile occupies one fixed position across the whole service area. Google says that search results are specific to the time, place, device, and recent history of the person searching.3
How do I record Google Business Profile Performance separately?
Record the profile report after the local observation, but do not put its values into the grid result column. Google says Performance data is available only for verified Business Profiles, and the operator must be signed in to the Google Account associated with the profile.2
In Google Search, use Business Profile → Performance, choose the report period, and click Apply. Google also documents a spreadsheet path in Business Profile Manager: select the profiles, choose Actions → Insights, select the timeframe, and click Download Report.2
| Performance field | What to record | How to read it |
|---|---|---|
| Profile access | Verified status and associated Google Account | This confirms that the report is available to the profile you intended to measure.2 |
| Report period | Exact start date and end date | The period belongs to the profile report, not to the timestamp of a grid point. |
| Searches | Value as shown, plus the date read | Google says this metric updates at the start of each month and may take up to five days to appear. Record a report within that window as not yet settled.2 |
| Views | Value as shown | Google describes this as unique visitors to the Business Profile on Search and Maps. A person can be counted only once per day, and the metric does not count every view of the business on Google.2 |
| Available actions | Directions, calls, website clicks, messages, bookings, or other metrics that appear | Only metrics that apply to the business appear. Keep a missing metric as unavailable, not zero.2 |
| Download | Export filename or report link, when used | The export preserves the report period and the values you used for the monthly record. |
Do not compare a Performance report's searches, views, or actions with the number of grid placements as if they shared a denominator. The report and the local observation describe different populations, surfaces, and periods.2,4
How should I compare this month with the previous month?
Compare like with like first. BrightLocal documents side-by-side comparison of Local Search Grid reports and recommends the same keyword and reporting period for a competitor comparison. Extend that discipline to the query, target, points, device or session, cutoff, and date convention in your own worksheet.4
| Comparison state | Label | Safe interpretation |
|---|---|---|
| All frozen fields match | BASELINE for the first run; otherwise no change label |
Compare the direction at the same points. Describe which points changed and by how much the tool reports. |
| Query or language changed | QUERY_CHANGED |
This is a new search question. Start a new baseline or report it as a qualified comparison. |
| Target, center, points, or spacing changed | LOCATION_CHANGED or GRID_CHANGED |
The sampled locations changed. Do not call the difference a local ranking movement. |
| Device, browser, app, account, or location context changed | DEVICE_CHANGED |
The search context changed. Explain the change before interpreting the result. |
| Result cutoff or not-found rule changed | CUTOFF_CHANGED |
The observed result boundary changed. The counts are not directly comparable. |
| Business Profile report dates changed | REPORT_PERIOD_CHANGED |
The profile activity period changed. Keep it separate from the grid timestamp. |
When every comparison field is the same, report the direction and affected points first. Then state what changed in the Business Profile Performance report for its own date range. If any design-change label applies, explain that change before saying whether visibility moved. A month-to-month difference does not establish that one profile edit caused the difference.
How do I interpret common result patterns?
| What you see | What you can say | What you should not say |
|---|---|---|
| The profile appears at more declared points under the same cutoff | The profile was observed at more of this month's sampled points for this query and design | The profile gained the same position for every customer |
| The profile is not found at some points | The profile was not found at those declared points under the saved cutoff | The profile is absent from Google everywhere |
| The grid changed and the observed count changed | The measurement design changed, so this is a qualified comparison or a new baseline | The business gained or lost local rank because the count changed |
| Performance searches or views changed while the grid did not | The profile report and the sampled map observation moved differently in their own records | One instrument explains the other or supplies its denominator |
| The grid's top-three share changed | The vendor metric changed for the exact query set, points, cutoff, and date recorded | Share of Local Voice is a Google ranking score |
Keep the cause open unless the evidence supports it. Google's public guidance names relevance, distance, and popularity as main factors, but it does not publish a formula that lets a sampled grid delta prove which factor caused a change.1
What should the monthly worksheet look like?
Copy this record for each run. Leave a field blank only when the tool does not expose it, and write “not available” rather than guessing.
Run ID:
Run date and time:
Timezone:
Query:
Language:
Search type:
Branded, non-branded, or location-specific:
Target or grid center:
Coordinates or named points:
Neighborhood or service area sampled:
Device:
Browser or app:
Signed-in state:
Location source:
Grid dimensions:
Active points:
Point spacing or distance:
Target movement:
Tool:
Report ID:
Result cutoff:
Not-found rule:
Business Profile verified:
Associated Google Account:
Performance report start:
Performance report end:
Searches:
Views:
Available actions:
Export filename:
Design-change label:
Compared with run ID:
Observed point-level change:
Interpretation and limits:
Sources
-
Google Business Profile Help, “Tips to improve your local ranking on Google”: Google local-ranking guidance (read 2026-10-10)
-
Google Business Profile Help, “Understand your Business Profile performance & insights”: Business Profile Performance guidance (read 2026-10-10)
-
Google Search Console Help, “Performance report (Search results): Overview and basic setup”: Search performance guidance (read 2026-10-10)
-
BrightLocal, “Local Search Grid - Track Business Rankings on a Map”: Local Search Grid guidance (read 2026-10-10)
-
Google Search Help, “Understand & manage your location when you search on Google”: Search location guidance (read 2026-10-10)
See where your profile stands
The audit shows how this applies to your own profile: it reads a verified Google Business Profile and scores it the same way every month.
Visibility Score
0 to 100
20 scored factors across profile completeness, performance, competitive position. Free, no signup, on any verified Google Business Profile.
No signup, no card. You get the score and the factors behind it.
Common questions
- Does Google recommend a specific geo-grid size or radius?
- No. Google's public local-ranking guidance explains relevance, distance, and popularity, but it does not prescribe a geo-grid size or radius. A provider's 5×5 starting point, a 3×3 grid, or any other design must stay attributed to that provider and recorded as part of the observation.
- Can I call the grid average a Google ranking?
- No. Call it a grid observation, sampled map-point result, or the tool's attributed metric. Google says its ranking-system details are confidential, and no one can request or pay for a better local ranking. The guide to how big a geo-grid scan should be covers the design choice; this worksheet covers the repeated run.
- Why did the same query show different results?
- Google says search results depend on time, place, device, and recent history. Location also helps Google show nearby results. Record those dimensions and compare declared points and sessions instead of treating one search as a universal reproduction.
- Is the Business Profile Performance report a ranking report?
- No. It reports profile searches, views, and available actions for a selected date range. It does not tell you where the profile appeared at a map point. Keep it beside the grid record, not inside it.