Joy Hawkins has spent the last few days looking at a version of Google's AI-powered local pack that reads the Google Business Profile and then declines to show most of what is in it. Her description, posted to X and replicated by Barry Schwartz at Search Engine Roundtable on 10 November, is exact about the mismatch: "It uses the Google Business Profile but yet removes a ton of its features (reviews, address, hours etc)."
This is a test two people have reported
Schwartz puts the change in one sentence: "Google is testing removing the action buttons, reviews, photos, etc from the AI Overview version of the local pack." He could replicate what Hawkins saw, which is as far as the corroboration goes. Google has published nothing about it, and Hawkins is not expecting it to stay. She calls it "probably the ugliest version of the AI Overview I've seen in local thus far" and says she is "Hoping this one reverts soon."
Tests like this revert often enough that treating one as settled would be a mistake. The interest is not in whether it lasts, but in what it shows about the terms on which a profile gets rendered.
The missing fields are fields filed with Google
Count what goes. Action buttons, reviews, photos, the address, the opening hours. Reviews are written by diners; the rest a restaurant types into the Business Profile form itself. That data is still there, still correct, and still Google's to display or not. Hawkins's observation is that the unit queries the profile and then renders a fraction of it.
A restaurant keeping its hours current in the profile has done the work asked of it. Whether a searcher ever sees those hours is a layout decision made somewhere else, and in this version it has gone the other way.
What survives is a name
Remove the buttons, the stars, the photographs, the address and the hours, and the unit comes down to business names inside generated prose. Schwartz is blunt about the cost: the version he saw "cannot be good for clicks, calls and direction actions to businesses."
For a diner the effect is a shortlist with nothing attached to it. Names get listed, and anything that would let someone choose between them — whether the kitchen is open, whether there is a dish on the menu they can actually eat — has to be found after the pack rather than in it.
On mobile there is no second unit underneath
Hawkins reported this part plainly: "On mobile, every time I get this version, the traditional local pack is gone." She did not describe desktop behaviour.
That changes the arithmetic. On a page carrying both units, a thinned AI pack is an inconvenience, because the ordinary local pack below it still carries the fields the AI version drops. When the thinned version replaces that outright, no second rendering picks up the slack.
Dish-level data was never in this unit
The removal list doubles as an inventory of what this pack has always carried: reviews, photos, hours, an address. A dish, a price, an allergen, a dietary tag have never been in it, in any version, which is why a test that empties the profile out of the unit leaves the dish-level description of a restaurant exactly where it was. Google can withhold the profile fields because it holds them, and it can only withhold what it was given.
