Reading all of a restaurant's Google reviews now requires a Google account. Sorting them needs one, and so does leaving one. The requirement turned up on Business Profiles at the end of September with no announcement attached, and Google has said nothing about it since.
Nobody at Google has explained the wall
Search Engine Roundtable published the find on 30 September, crediting Syed Amir on X along with Michael B. Snow and Jean-Sébastien Girard on LinkedIn — three people who hit the same prompt separately. The prompt asks for a sign-in and offers Google's standard pitch in return: "Sign-in to get the best of Google Maps." Behind it sits the ability to "read and search through every review and photo", to sort reviews by rating or by date, and to post one. Barry Schwartz, who wrote the Roundtable piece, offered the obvious guess and was careful to label it as a guess:
I assume this was done to help prevent AI, bots, and third parties from scraping the Google reviews.
Antonio Fernandez reached the same reading at Relevant Audience the following day and was equally exact about its status, describing it as "reasoned speculation, not something Search Engine Roundtable or Google has confirmed". So the only stated rationale for the change is an inference drawn twice by people outside the company.
The same wall went up in February and came down inside a week
This is the second attempt. Ryan McNeal reported a near-identical limited view at Android Authority on 18 February and wrote then that "it's unclear if this is just a bug or if this is an intentional change made by Google". On 23 February he updated the piece: Google "has now rolled back the change and/or fixed the issue". Five days up, then gone, with no statement at either end.
The detail worth carrying forward from February is the shape of what the wall covered. Writing it up at How-To Geek on 19 February, Cory Gunther set out what a signed-out visitor lost: "Unless you sign in, you won't be able to see the menu, user reviews, dine-in or takeout options, and related information."
The menu was inside the wall. Whether the current version reaches that far has not been reported either way, and a wall that covered menu data once is not a safe thing to assume about.
The signed-out profile is a pin and a phone number
Gunther also recorded what survived in February: the location, the address, the phone number, a single photo. Those are the fields Google kept outside the wall, and not one of them says anything about the food.
For anyone watching their own reviews, the practical effect is immediate. A restaurant checking what diners are saying, or a reputation tool doing it on the restaurant's behalf, was reading a page that anyone could load. Fernandez's advice is to audit the profile and measure what actually moved, which is right, and harder to do from outside an account than it was last week.
The menu is the part with no account in front of it
Reviews are the one element of a restaurant's web presence it neither writes nor hosts. Diners supply the text, Google holds the database, and access to the whole of it is now a setting on Google's side.
A restaurant's own menu page carries no sign-in step. Published as Schema.org markup — which is what GMMO exists to produce — the dish names, prices, sections, allergens and dietary flags stay readable by anything that can fetch a URL, including the assistants now reading restaurants off the open web.
That does not replace reviews, and nothing a restaurant publishes about itself will. What it does is keep the part of the record that describes the food out of a corpus whose access rules have changed twice in eight months. Google has published no rule covering who may read the reviews it collected, which leaves the February rollback as the only evidence of where the limit sits, and that rollback was never explained either.
