A plumber with one truck and a shop on the east side of town pays for local SEO for a year and sees the profile ranking first when he searches from his own driveway. He concludes it works. The customers who call from the west side of the service area never saw him. This case is hypothetical, but it shows how a belief survives when nobody tests it where the customers actually are.
Here are four beliefs worth retesting before the next invoice, plus one to drop. None of them is false by default. Each is simply unproven for your service area, and a test costs less than another month of guessing. This sits inside our complete guide to Google Business Profile and local SEO in the United States.
Belief one: a single ranking number describes my visibility
Rankings in Google Maps change with the location of the person searching, so one number checked from one spot says little. Google describes local results as a mix of relevance, distance and prominence, and it does not publish the weights.
To retest, scan a grid over the whole service area instead of checking one address. A heatmap scan of your whole service area shows the position at each point. Solo plans scan up to 21×21 points with 5 keywords per scan, which is enough to cover one keyword per core service: drain cleaning, water heater repair, emergency plumber, and so on. Save the result before you change anything.
Belief two: a wider service area reaches customers farther out
Listing more towns in the service area tells customers where you work, but nothing published says it moves the ranking farther from your base. Distance is one of the three factors, so the shop’s location keeps weighing on every search.
The retest is a before-and-after on the same grid. Scan with the current service area, add the extra towns, give the change time to appear, then scan again with identical keywords and grid size. If the far points stay empty, the wider list did not extend your reach, and the budget is better spent elsewhere, such as work on the categories and services you actually perform.
Belief three: more posts and photos move the ranking
Posts and photos keep a profile current, and customers do look at them. Whether they lift your position is a separate question, and a dependable way to answer it for your market is to change one thing at a time.
Pick a quiet stretch with no new reviews or other edits. Post and add photos on a steady schedule, log the dates, and rescan. The rescans need the heatmap, which comes with Solo. Lite includes 4 posts and 4 photos per month, and the LocalEdge Lite and Solo plans are described on one page. If the grid does not change, the posts still serve customers, but they are not a ranking tactic for you.
One belief to drop, not retest: paying customers for reviews
Google does not allow offering incentives for reviews, and it does not allow asking only the customers likely to be happy. A discount for a five-star review is a policy risk, so there is nothing to test.
What you can test is the process. Ask every customer after the job, in the same way, and reply to what comes in. Lite gives AVI drafts of review replies that you read and edit before sending, which keeps the replies in your own words.
Belief and reality at a glance
The table sums up what each belief assumes, what Google publishes, and the test that settles it.
| Belief | What is known | Retest |
|---|---|---|
| One ranking number | Results depend on where the searcher stands | Grid scan across the service area |
| Wider service area reaches farther | Distance is one of three factors, weights unpublished | Same grid before and after the change |
| Posts and photos lift rank | Weights unpublished, effect unproven | One change, logged dates, rescan |
| Incentivized reviews are a shortcut | Not allowed by Google | None: drop it, fix the asking process |
For a plumber running tests on several trucks or franchise territories, or an agency doing the same for several clients, the agency plan with scheduled scans repeats them daily, weekly or monthly and keeps the history and evolution of each scan.
A retest checklist for the next spending decision
- Save a baseline grid for each core service before any change.
- Change one thing per test, and write the change and the date down.
- Rescan with the same keywords and the same grid size.
- Compare against your own call log, not against a feeling.
- Keep only the changes that moved the far points, and stop paying for the rest.
A position you have measured at every point is worth more than one you assume. If you want a first reference, you can start with a free GBP Score check on LocalEdge Lite.
