Café reviews and listings: the drink people name, and one set of hours

A review that names the drink gives a question something to match

People ask about cafés in specifics: a milk, a pastry, a seat near a plug, a quiet corner. A review is a brand mention you did not write, and when it names one of those things it contains the same words the question does. A review that praises the vibe and nothing else is kind, and contains none of them. Both count toward a rating; only the first is a sentence, by someone who was there, about the thing being asked.

The reviews worth noticing name a drink or a dish, the space, a time of day, or a request the staff handled: a milk swapped, a table found for a stroller, a laptop welcomed on a slow afternoon. You cannot write those reviews and should not script them. You can notice them, quote them and reply to them.

Reviews as an AI signal covers what a crawler can read of reviews in general. This article is the café part: which reviews to quote where, which to leave alone, and the listing data they sit beside, all of which has to agree with what the café's own site states.

Which reviews to quote on your own pages, and where

Quote a handful, as text, with the reviewer's first name, the date and the platform named. Quoting is one of the source-side changes Aggarwal et al. tested in GEO: Generative Engine Optimization (KDD 2024): adding quotations, statistics and citations to a source raised its visibility in generated answers by up to about 40% on the paper's benchmark. The benchmark held no café pages, so read it as the mechanism, not as a forecast.

The third column matters. A review beside your own statement confirms it; a review on its own is asked to carry a fact the café never stated. One customer finding it easy to bring a stroller in is an experience. A step-free entrance on [street], with the restroom on the same floor, is the café's fact. Publish the fact, and let the review agree with it.

Reviews a café should not quote on its own pages

Some reviews read well and still do not belong on your pages. The main one is any review that makes a dietary or allergy claim on your behalf: that a pastry was safe for someone's celiac disease, or that the kitchen has no nuts in it. Quoted on your site, a customer's experience becomes your claim, and it is a claim your menu's allergy line deliberately does not make.

• Reviews naming a barista or a manager who has left. The praise was real; the person is not there to meet.
• Reviews of a menu, a price or a room you have since changed. Quote the ones that are still true.
• Reviews you cannot attribute: no first name, no platform, no date. A quote nobody can check reads as invented.
• Anything from staff, family or friends, or given in return for a free drink. That should not exist on any platform, and quoting it makes it yours.

Structured data follows a stricter line than text. Google's review snippet documentation says not to aggregate reviews or ratings from other websites, and it treats reviews a business controls about itself, on its own site, in markup or through an embedded widget, as self-serving and ineligible for review stars. Its local business page recommends aggregateRating only for sites that collect reviews of other businesses. So a café's site quotes reviews as text and carries no Review or AggregateRating node built from any platform's reviews.

One name, one address, one set of hours, on every listing

Start with a list of every place the café is listed: the map services, the review platforms, each delivery app, any ordering or booking tool, local guides, your own social profiles. Each carries some version of the name, the address, the phone and the hours, and each was filled in on a different day by whoever was at the counter.

Listings are only half of it. In our audit of 9,483 small business websites (40 trades, 90 metros, September 2026), 43.1% of the sites were inconsistent about who and where they are on their own three main pages, and 36.9% gave more than one phone number; the audit has no café cut. A café that fixes its listings and leaves two numbers on its own site has fixed the copies and not the original.

Google's guidelines for representing a business ask for the real name, the real address and accurate hours, and the same discipline suits every other listing. Decide the correct form of each field once, write it on your own site first, then copy it outward, character for character.

The name, the accent and the ampersand

Café names are easy to write two ways: with the accent and without it, with an ampersand and with "and", as Coffee Co. and as Coffee Company, with the street in the name and without. To anything matching your site against a listing, and a listing against a review, each variant is a different string. Pick one form, the one on your sign, and use it everywhere you control.

People will spell it their own way anyway. In the markup, every schema.org type inherits alternateName from Thing, which can hold the unaccented spelling or the short name locals use without changing the name itself. On a listing, the name field takes the name on your sign and nothing added to it. The aim is one entity: one café, whatever a review calls it.

A second location is a second business: its own page, its own listing, its own hours, its own LocalBusiness node, and the reviews about it quoted on its page, not pooled with the first one's.

Keeping every copy in step when something changes

Café data goes wrong on the day something changes and only one copy is updated: holiday hours, the switch to summer hours, the terrace opening, a new milk, a price rise, a closure for renovation. Keep the list from the table, and go down it in the same order every time a fact changes.

1. Change the fact on your own site, on the one page that holds it, and date it. Holiday hours can also go into the markup as specialOpeningHoursSpecification, which schema.org describes as overriding the regular hours, with validFrom and validThrough dates.
2. Change it on each map listing, special hours and status included.
3. Change it on the review platforms' business pages and on each delivery app.
4. Change the social bios, then note the date you finished.
5. A week later, ask one assistant the question the change answers ("is [café name] open on [holiday]") and see which version comes back. Asking the AI about your café turns that into a monthly check.

When a review states a fact that has since changed, reply with the current one. A review from two winters ago saying there was no oat milk can get a short reply saying there is now, since when, and where it is on the menu. An owner's reply sits on the same public page as the review, so the two are read together.