A pattern I see on almost every local audit: the map-pack rankings look healthy, the owner feels safe, and the calls still quietly drop.
The catch is that your rank tracker and the place you are actually losing local visibility are not the same thing, and that gap is where the leads disappear.
Key Takeaways
- Plain “near me” searches still get the local pack; AI Overviews show on only about 15%.
- Informational-local searches return an AI Overview about 77% of the time, and most trackers never check them.
- The AI local pack shows one or two businesses (about 32% of the old inventory) and removes the call button.
- Many businesses report 50 to 70% fewer calls from Maps.
- The path is shifting to in-answer booking, so a fast booking endpoint now matters.
- You find the lost queries in Search Console by query type, not by map-pack rank.
Why this matters for local businesses
Local search used to be simple: rank in the 3-pack, get the call. AI Overviews and the new AI local pack changed both halves of that.
They changed which searches even show a map pack, and what a person can do once they see one. If you only track rank, you miss both, and the first sign is a slow month on the phones.
Where your rank tracker goes blind
Your rank tracker watches the searches that have barely changed. For a plain “near me” or “plumber chicago” search, Google still shows the local pack on more than 90% of results and an AI Overview on only about 15%, according to Whitespark’s local AI Overview research.
That group looks stable, so your tools stay green. The visibility you are losing sits in a different group of searches, one your tracker was never set up to watch.
Which local queries you are losing
Split local searches into two groups. Transactional “near me” searches still bring up the pack.
But local searches with an informational angle, the “how long does an eye exam take near me” or “is X worth it in [city]” type, now return an AI Overview about 77% of the time. Those are the questions people ask while they are still choosing, and they are exactly the ones a map-pack tracker ignores.
So on those searches you do not show up at all, and nothing in your reports tells you.
| Local search type | What shows | Does your rank tracker watch it? |
|---|---|---|
| Transactional “near me” / “city + service” | Local pack (90%+); AI Overview ~15% | Yes, and it looks healthy |
| Informational + hybrid local | AI Overview ~77%; local pack rarely | No, this is the gap |
| Where the AI pack does show | 1-2 listings (~32% of old inventory), no call button | Partly; rank hides the lost calls |
What the AI local pack changed
Where the AI local pack does appear, it is smaller and it converts differently. Joy Hawkins
Joy HawkinsOwner, Sterling SkyOwner of Sterling Sky and one of the most-cited local SEO researchers.LinkedInXSterling Sky‘s research found it surfaces only about 32% of the businesses the old 3-pack did (5,943 against 18,330 across the same searches), usually one or two listings instead of three.
It also removes the call button, and businesses have reported 50 to 70% fewer calls from Maps as a result.
Google is pushing the action into the answer itself. For “HVAC repair near me”, AI Mode wants to book the slot directly through your scheduling endpoint, so a fast, bookable endpoint is becoming part of local visibility, not just a website nicety.
How to find the lost queries in Search Console
To see it, stop leaning on the rank tracker and go to Search Console. Split your local queries into the two groups, transactional and informational, then check which informational ones now return an AI Overview.
The distance between “we still rank” and “we still get called” is your real exposure, and it only shows when you look at the right group of searches.
From there the work is familiar. Write real content for the informational-local questions buyers actually ask, keep your name, address, and phone consistent so Google trusts you as the business to surface, and make sure someone can reach or book you even without a call button.
The March 2026 update also rewarded review recency and owner responses over raw review count, so active profiles recovered while stale ones with high counts slipped (Search Engine Roundtable). Staying on top of reviews now pays twice.
This is the local version of the method in our piece on measuring which queries lose traffic to AI Overviews, and the consistency basics for local SEO matter more here, not less.
So, is your rank tracker still enough for local?
In my view, no, the rank tracker is no longer enough for local. Treating map-pack position as your health metric is how you lose ground without seeing it.
I would watch the informational-local queries in Search Console, keep your entity and contact details consistent, stay active on reviews, and make sure people can reach or book you where the call button is gone.
The businesses that adjust to how people actually search now will hold their ground. The ones still reporting a healthy 3-pack will keep wondering where the calls went.
Worried your local visibility is slipping without showing it?
This is exactly the kind of gap I check on an audit. Contact us or email me, and we will see whether the AI shift is quietly costing you calls.
Update Logs
23 Jun 2026
- Added an inline author hovercard on the Joy Hawkins mention.
22 Jun 2026
- Added a table of contents, captions on the comparison table and the diagram, and renamed the closing section to a natural question.
12 Jun 2026
- Moved Key Takeaways, CTA, and update logs to class-based blocks (no inline styles).
- Made the diagram class-based and dark-mode aware.
11 Jun 2026
- Published. Consolidated three earlier drafts.
- Verified the local AI Overview stats.
- Added the AI-local-pack section, the booking-endpoint point, and the diagram.
Want our posts to show up more often on Google?
One step & Google will surface this site in your Top Stories.
