<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Restaurants - Blog | Cloutly | Reviews, Reputation and Digital Marketing Insights]]></title><description><![CDATA[Discover review strategies, templates and tips to elevate your reputation and win new business]]></description><link>https://cloutly.com/blog/</link><image><url>https://cloutly.com/images/favicon.png</url><title>Restaurants - Blog | Cloutly | Reviews, Reputation and Digital Marketing Insights</title><link>https://cloutly.com/blog/</link></image><generator>Astro</generator><lastBuildDate>Fri, 25 Sep 2026 05:07:49 GMT</lastBuildDate><atom:link href="https://cloutly.com/blog/tag/restaurants/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Restaurant reputation management: how to run it across every venue]]></title><description><![CDATA[Most venues do not have a review problem. They have a no-system problem, where the ask happens when someone remembers and the replies happen when someone is angry.]]></description><link>https://cloutly.com/blog/restaurant-reputation-management/</link><guid isPermaLink="false">https://cloutly.com/blog/restaurant-reputation-management/</guid><category><![CDATA[Restaurants]]></category><category><![CDATA[Reviews]]></category><dc:creator><![CDATA[Lachlan Fea]]></dc:creator><pubDate>Sun, 06 Sep 2026 00:00:00 GMT</pubDate><media:content url="/images/blog/restaurant-reputation-management/restaurant-reputation-management-feature-cover-2026.jpg" medium="image"/><content:encoded><![CDATA[<img src="/images/blog/restaurant-reputation-management/restaurant-reputation-management-feature-cover-2026.jpg" alt="Restaurant reputation management: how to run it across every venue"><p>Restaurant reputation management is three habits rather than a project. Ask every guest the same way after the visit, answer what comes back, and read the reviews across your venues for the complaints that repeat. It matters more for a restaurant than for most businesses because the rating sits between the search and the booking. Someone standing on the street at seven o'clock deciding where to eat never opens your website.</p>
<p>What follows is the venue version of that job: where the ask belongs in a service, what Google forbids at the table, which sites are worth the effort, what to write back, and how any of it survives a second and a fourth venue. Most advice on reputation management for restaurants stops at reply politely and ask for reviews, which is true and useless.</p>
<figure><img src="/images/blog/restaurant-reputation-management/venue-theme-grid-hospitality-page.png" alt="A grid of four restaurants against five complaint themes, each cell holding a count of negative mentions, with each restaurant&#x27;s total review count in the last column and a THIN label beside the venue that has only 88 reviews"><figcaption>The venue view from our hospitality page, drawn with an invented four-restaurant group. Counting complaints venue by venue is what turns a rating into something you can act on.</figcaption></figure>
<h2 id="what-reviews-do-for-a-restaurant">What reviews do for a restaurant</h2>
<p>Start with the map result. Google's guidance on <a href="https://support.google.com/business/answer/7091" rel="noopener">local ranking</a> lists relevance, distance and prominence, and puts reviews inside prominence: "More reviews and positive ratings can help your business's local ranking." Prominence itself is "based on info like how many websites link to your business and how many reviews you have". For a restaurant that covers most of the searching that happens near you.</p>
<p>Then the walk-in. Someone two hundred metres from your door is comparing you with two other places on the same street, and what they see is a rating, a count and the two most recent reviews. A venue with 480 reviews at 4.5 reads as busy. The same venue with 46 reads as untested, whatever the food is like.</p>
<p>Managing restaurant online reviews gets simpler once you accept that both of those happen on Google. Everything after them is a decision about who eats with you.</p>
<h2 id="when-to-ask-a-guest-for-a-review-and-why-never-at-the-table">When to ask a guest for a review, and why never at the table</h2>
<p>Ask after the visit is over. Two moments work: shortly after the bill closes, while the guest is in the taxi or walking home, and the next morning, which suits a long dinner and not a lunch. Either beats a week later, when the meal has blurred into every other meal.</p>
<p>The table itself is out, and not because it is awkward. Google's <a href="https://support.google.com/contributionpolicy/answer/7400114" rel="noopener">prohibited and restricted content policy</a>, read on 6 September 2026, says under rating manipulation: "When soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor should they request that specific content be included."</p>
<p><img src="/images/blog/restaurant-reputation-management/google-on-premises-and-staff-solicitation-rule.png" alt="Google&#x27;s Maps user generated content policy, listing under things merchants may not do that when soliciting reviews they should not require or pressure users to leave ratings or write reviews while on the premises, nor request that specific content be included, followed by two sub-points saying this includes merchants requesting that staff solicit a certain number of reviews, or reviews that include content identifying a staff member"></p>
<p>Read that closely, because most articles get it wrong in one direction or the other. It is not a ban on a review link existing inside your building. A QR code on the bill folder is fine, and Google's own <a href="https://support.google.com/business/answer/3474122" rel="noopener">tips page</a> says that "to leave reviews, you can ask customers to visit a Google link or scan a QR code". What is banned is a person standing there while the guest types. A tablet on the pass, a server waiting for the phone to come out: that is pressure on the premises, and it is how you end up with a page of five-word reviews that read like they were written under supervision.</p>
<p>The same policy bans the other shortcut. Merchants may not "offer incentives ... in exchange for posting any review or revision or removal of a negative review", so a free dessert for a five-star breaches it however friendly the sign is. Nor may you sort your guests: sending happy diners to Google and unhappy ones to a private form is review gating, which the policy covers under "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers". Ask everyone the same way at the same point.</p>
<h2 id="let-the-till-or-the-booking-system-decide-the-moment">Let the till or the booking system decide the moment</h2>
<p>An ask that depends on somebody remembering stops on a busy Saturday, which is the night you most want reviewed. Hang it off something that already happens.</p>
<p>The till is the obvious trigger, because payment is the one event every seated guest generates. Cloutly connects to Square and Clover for this: Square can fire on "Payment received" or on "Order completed and payment received", Clover on "Payment Completed", and you choose how long after that the message goes out. A booking system reaches the same place through Zapier, so a completed reservation can be the trigger instead if that suits your floor better.</p>
<p>What matters more than the trigger is what the ask does with a regular. Someone who eats with you fortnightly should be one contact asked once, not one ask per visit, and a guest who reviewed you two months ago should not be asked again on their next booking. Cloutly holds one contact per person, moves the send time when they book again rather than adding a second ask, skips anyone who has reviewed you in the last 90 days, and stops the follow-ups the moment a review lands.</p>
<p>No till reaches the walk-in who paid cash. That is what a QR on the bill folder is for, and it is the honest limit of automation in a dining room. More of this is on our <a href="/solutions/hospitality">hospitality page</a>.</p>
<h2 id="which-sites-to-send-guests-to">Which sites to send guests to</h2>
<p>Two, for almost every venue. Google takes the ask at every venue, on every service. Tripadvisor takes the second ask if travellers are a real share of your covers, and nothing at all if your room is mostly regulars from three suburbs. Check your bookings before you decide which you are.</p>
<p>Then stop, because the rules stop you. OpenTable asks the diner itself the day after a seated booking. Yelp tells businesses never to ask. Zomato answers selective asking with a public disclaimer on your own page telling diners your reviews look suspicious. Which sites allow the ask, which punish it and what each lets you say back are in <a href="/blog/restaurant-review-sites/">restaurant review sites: the 9 that matter</a>. The wording of the ask itself is in <a href="/blog/get-more-google-reviews/">how to get more Google reviews</a>.</p>
<h2 id="the-complaints-every-venue-gets-and-what-a-reply-has-to-do">The complaints every venue gets, and what a reply has to do</h2>
<p>The negatives repeat. The wait, cold food, noise, price, a member of staff, and a booking that went wrong: after a few hundred reviews you can name the complaint before you have finished reading it. The star ratings vary. The complaints do not.</p>
<p>A reply that works takes about ninety seconds. It uses the guest's name, says plainly which part of their account is true, names the change in one sentence if there is one, and offers a way back that is a person rather than a form. Google's <a href="https://support.google.com/business/answer/3474122" rel="noopener">reply guidance</a> adds a rule that catches restaurants: be "conversational, not promotional", because "your reviewers are already customers". Putting right one bad night is not a promotion. Closing every reply with a discount code is.</p>
<p>Two rules are specific to hospitality.</p>
<p><strong>Answer the one-shot sites when you are calm.</strong> Google lets you edit a reply after it publishes. Tripadvisor does not: "At this time, it's not possible to edit a management response. However, you can delete a response and then submit a new one in its place." Deleting pulls your answer off the review straight away, so the reply you type at eleven at night either stays or leaves the review bare while you write another.</p>
<p><img src="/images/blog/restaurant-reputation-management/tripadvisor-cannot-edit-management-response.png" alt="Tripadvisor&#x27;s owner help centre article Editing or deleting management responses, saying it is not possible to edit a management response and listing the four steps to delete one from the Management Center and submit a new one"></p>
<p><strong>Never trade a comp for a review coming down.</strong> Making good on a bad night is fine and expected. Offering a meal in exchange for a revision is the same breach as buying the review outright, and Google's policy names both in one sentence.</p>
<p>Here are three templates for complaints venue-specific enough that generic advice fails on them. The wait, the price and a complaint about a person already have worked examples in <a href="/blog/positive-review-response-examples/">review response examples</a>, and ten written for the Tripadvisor format are in <a href="/blog/how-to-respond-to-a-bad-tripadvisor-review/">how to respond to a bad Tripadvisor review</a>. Every business below is invented.</p>
<h3 id="noise-we-could-not-hear-each-other">Noise: "we could not hear each other"</h3>
<blockquote>
<p>Thanks for the review, Marianne. The room is brick and glass and it gets loud the moment it fills, which is a fair thing to be annoyed about and not something you should have to shout through. The two booths along the back wall are the quietest tables we have and they are yours if you ring and ask for them. We have also brought the music down after seven, which will not change the room but it takes the edge off.
Rosa, Owner, Bramble &#x26; Rye</p>
</blockquote>
<p>Noise is the complaint owners answer worst, because the honest answer is that the room is the room. Do not promise an acoustic rebuild. Offer the quiet table, name the one thing you changed, stop.</p>
<h3 id="cold-food-when-the-guest-said-nothing-at-the-time">Cold food, when the guest said nothing at the time</h3>
<blockquote>
<p>Thanks for writing this, Owen. The pork should not have reached you cold, and it is not on you to have flagged it at the time, so I am not going to ask why you didn't. That plate sat on the pass while a table of twelve went out, which is a service problem and not a kitchen one. The pass is split between the two sections from this week. Ring the restaurant and ask for me and dinner is on us next time.
Callum, General Manager, Bramble &#x26; Rye</p>
</blockquote>
<p>The instinct to write "we wish you had told us at the time" is strong and always wrong in public. It reads as blame. Take the point, name where the failure sat, and leave the invitation unattached to the review.</p>
<h3 id="a-booking-or-a-function-that-went-wrong">A booking or a function that went wrong</h3>
<blockquote>
<p>Thanks for writing, Ellery. Fourteen people booked six weeks out and then split across two rooms on the night is not a mix-up, it is us not reading our own diary. The function sheet now goes to the floor manager on the Monday of that week instead of the morning of, so a room can be held properly. Your deposit went back to the card that paid it on Tuesday. If you will let us have the birthday next year, ask for me and I will run it myself.
Tam, Floor Manager, Bramble &#x26; Rye</p>
</blockquote>
<p>Booking failures produce the angriest reviews a venue gets, because the guest planned around you and told other people to come. The refund goes before the apology, and the process change is what stops the next one. More of what a reply should never say is in <a href="/blog/examples-of-bad-reviews/">examples of bad reviews</a>.</p>
<h2 id="give-the-floor-the-credit-inside-the-rule-you-just-read">Give the floor the credit, inside the rule you just read</h2>
<p>Guests name people. "Marianne looked after us all night" is the most common shape a five-star restaurant review takes, and it is worth more to the person named than any roster note.</p>
<p>There is a rule sitting under the on-premises one that almost nobody in hospitality has read. In the screenshot above, Google lists among the things merchants may not do "requesting that staff solicit a certain number of reviews" and "requesting that staff solicit reviews that include specific content, including content that identifies a staff member". A target of ten reviews a shift is out. So is asking guests to mention Marianne by name.</p>
<p>What is left is arithmetic you do afterwards. Give each person their own review link or QR code and the reviews arriving through it are counted to them, with nothing asked of the guest. Cloutly reads it that way on its staff recognition board, and where there is no personal link it falls back to matching names in the review text and says so in the product: name matching fills the gaps, it can credit the wrong person, and it can miss a review that names nobody.</p>
<p>That caveat is the useful part. Two Georges on the floor and no review text will tell them apart. Personal links fix that, and a board read out at a Monday briefing beats one nobody opens.</p>
<h2 id="read-every-venues-reviews-for-the-theme-not-the-score">Read every venue's reviews for the theme, not the score</h2>
<p>A rating tells you something is wrong. It never tells you what. Hospitality reputation management at more than one venue is mostly the work of turning a few thousand reviews into the two or three things worth fixing this month.</p>
<p>Do it by counting rather than by feel. Take a quarter of reviews per venue, count how many mention each recurring complaint, and put those counts beside each venue's total review count so a busy site is not punished for volume. Look for a theme heavy at one venue and light at the others: that is an operational difference you can go and stand in, rather than a fact about your food.</p>
<p>Cloutly does this as Signals, against ten hospitality themes: Food &#x26; drink, Service, Bookings &#x26; entry, Price &#x26; value, Cleanliness, Venue &#x26; facilities, Safety, Events &#x26; functions, Digital &#x26; contact, and Other. It reads by venue as well as by theme, carries the denominator on every number and a verbatim quote under every signal, and marks a venue with too few reviews in the window as thin instead of pretending the number means something. Our team switches it on for an account rather than you enabling it yourself, so ask us.</p>
<h2 id="restaurant-reputation-management-across-a-group">Restaurant reputation management across a group</h2>
<p>Nothing above gets harder at four venues. It gets repetitive, which is a different problem with a different fix.</p>
<p>Each venue has its own Google Business Profile, its own Facebook Page and its own Tripadvisor listing with its own identity check. No single reply box answers for a group, and a tool claiming otherwise is describing an inbox rather than a shortcut. What you can standardise is the ask: same trigger, same delay, same wording, so a guest at your newest site gets the same message at the same point as a guest at your first. Merivale is one of the restaurant groups that manages its reviews in Cloutly.</p>
<p>Decide who replies before you roll anything out. Head office replying to everything is consistent and reads like a call centre. The venue replying to everything is warm and stops dead in a busy December. What survives is the venue manager replying, with head office writing the four or five answers to the complaints that repeat and checking they go out. The argument in full, league table included, is in <a href="/blog/franchise-marketing/">multi-location review management</a>.</p>
<h2 id="frequently-asked-questions">Frequently asked questions</h2>
<h3 id="how-do-restaurants-get-more-google-reviews">How do restaurants get more Google reviews?</h3>
<p>By asking every guest the same way, shortly after the bill or the next morning, with the ask hung off something automatic like the till rather than a person remembering. Google encourages asking and suggests a link or a QR code. It bans incentives, and it bans sorting guests by how happy they are.</p>
<h3 id="can-a-restaurant-ask-for-a-review-at-the-table">Can a restaurant ask for a review at the table?</h3>
<p>Not by standing over the guest. Google's policy says merchants should not require or pressure users to leave reviews while on the premises, or ask for specific content. A QR code on the bill folder that the guest uses later is fine. A server waiting while they type is not.</p>
<h3 id="should-a-restaurant-reply-to-every-review">Should a restaurant reply to every review?</h3>
<p>Reply to every negative one, and to positive reviews that name a person or a dish. Answering everything is a nice ambition and the first thing to lapse in December. Write your Tripadvisor responses when you are calm, because you cannot edit one after it publishes, only delete it and start again.</p>
<h3 id="who-should-reply-to-reviews-in-a-restaurant-group">Who should reply to reviews in a restaurant group?</h3>
<p>The venue manager, with head office writing the standard answers to the complaints that repeat and checking the replies go out. Head office replying to everything reads like a call centre, and the venue replying alone stops during service peaks. Splitting it survives both.</p>]]></content:encoded></item><item><title><![CDATA[Restaurant review sites: the 9 that matter in 2026]]></title><description><![CDATA[Every list of restaurant review sites names the same platforms, and almost none says which ones a restaurant is actually allowed to ask on.]]></description><link>https://cloutly.com/blog/restaurant-review-sites/</link><guid isPermaLink="false">6522999a9367088c7bbd1842</guid><category><![CDATA[Restaurants]]></category><category><![CDATA[Reviews]]></category><category><![CDATA[Guides]]></category><dc:creator><![CDATA[Lachlan Fea]]></dc:creator><pubDate>Tue, 06 Sep 2022 05:48:49 GMT</pubDate><media:content url="/images/blog/restaurant-review-sites/restaurant-review-sites-feature-cover-2026.jpg" medium="image"/><content:encoded><![CDATA[<img src="/images/blog/restaurant-review-sites/restaurant-review-sites-feature-cover-2026.jpg" alt="Restaurant review sites: the 9 that matter in 2026"><p>Google is the restaurant review site that decides. It is where the search ends for most diners, and its rating is the one they compare. The other eight restaurant review sites worth knowing in 2026 matter for narrower reasons, and one of them will put a public warning on your page if you collect reviews the wrong way.</p>
<p>What separates these platforms is not audience size. It is who may post, and whether you are allowed to ask. Yelp tells businesses never to ask. Zomato answers selective asking with a public disclaimer on your page telling diners your reviews look suspicious. OpenTable does the asking for you and will not accept a review from anyone who did not book through OpenTable and turn up. Most lists of restaurant review sites name the same platforms and skip all of that.</p>
<p>This is the hospitality version of our guide to <a href="/blog/review-sites-for-service-businesses/">review sites for businesses</a>. Every rule below was read off the platform's own help or policy pages on 6 September 2026.</p>
<figure><img src="/images/blog/restaurant-review-sites/opentable-who-can-leave-a-review.png" alt="OpenTable&#x27;s Diner Help article on ratings and reviews, showing that only diners who booked and honored a reservation through OpenTable can leave a review, and that a canceled reservation or one booked directly with the restaurant gives the diner no option to review"><figcaption>OpenTable's diner help page, read on 6 September 2026. It is the only one of the nine where the reviewer has to have booked through the platform and turned up.</figcaption></figure>
<h2 id="the-9-restaurant-review-sites-and-who-you-may-ask">The 9 restaurant review sites, and who you may ask</h2>

































































<table><thead><tr><th>Site</th><th>Who can post</th><th>May you ask for reviews</th><th>How you reply</th></tr></thead><tbody><tr><td>Google Business Profile</td><td>Anyone with a Google Account</td><td>Yes, and Google tells you how</td><td>Publicly, editable later</td></tr><tr><td>Tripadvisor</td><td>Anyone with an account</td><td>Yes</td><td>A public Management Response under the review</td></tr><tr><td>Yelp</td><td>Anyone with an account</td><td>No, never</td><td>Publicly or by direct message, once claimed</td></tr><tr><td>Facebook</td><td>Anyone logged into Facebook</td><td>Meta publishes no rule</td><td>Meta publishes nothing on Page replies</td></tr><tr><td>OpenTable</td><td>Only diners who booked through OpenTable and turned up</td><td>No need, OpenTable asks the day after</td><td>One public response, then private only, no edits</td></tr><tr><td>Zomato</td><td>Anyone with an account</td><td>No, and it is punished in public</td><td>One management response, no edits</td></tr><tr><td>Uber Eats</td><td>Customers, inside the app</td><td>No published rule</td><td>Merchant articles sit behind a store login</td></tr><tr><td>DoorDash</td><td>Customers with an order, in selected US, Canada and Australia markets</td><td>No published rule</td><td>Privately, within 7 days</td></tr><tr><td>The Infatuation</td><td>Its own writers</td><td>No</td><td>No</td></tr></tbody></table>
<p>The sites anyone can post to are mostly the ones you may ask on, and the sites that check a real visit ask on your behalf. So the list of places a restaurant should chase reviews is much shorter than the list of places it should be listed.</p>
<h2 id="google-restaurant-reviews">Google restaurant reviews</h2>
<p>Google is barely a restaurant review site. It is the layer above them, and anyone can post. The only gate is that customers "must be signed into a Google Account to leave a review", and one can be set up with a non-Gmail address.</p>
<p>Google also wants you to ask. Its <a href="https://support.google.com/business/answer/3474122" rel="noopener">tips to get more reviews</a> say that "to leave reviews, you can ask customers to visit a Google link or scan a QR code". What it bans is paying for the answer: "offering incentives, like free or discounted goods or services, in exchange for customers to post reviews ... is considered fake &#x26; misleading content and is strictly prohibited". A free dessert for five stars breaches that, whatever the sign on the counter calls it.</p>
<p><img src="/images/blog/restaurant-review-sites/google-ask-with-a-link-or-qr-code.png" alt="Google&#x27;s Business Profile help page &#x22;Tips to get more reviews&#x22;, which says businesses can ask customers to visit a Google link or scan a QR code, that offering free or discounted goods in exchange for reviews is strictly prohibited, and that customers must be signed into a Google Account to leave a review"></p>
<p>Google also lets you edit or delete a reply after it publishes. Zomato and OpenTable never do, so Google is the one site here where a reply written at eleven on a Saturday night can be fixed on Sunday.</p>
<h2 id="tripadvisor-restaurant-reviews">Tripadvisor restaurant reviews</h2>
<p>Tripadvisor is where the traveller decides. If a real share of your covers are people who do not live within ten minutes of your door, it is your second site and it is not close.</p>
<p>You may ask, and Tripadvisor would rather you answered. Its <a href="https://www.tripadvisor.com/Trust-lpgT1CmsfQ3E-Management_response_guidelines.html" rel="noopener">management response guidelines</a> say owners "can and should respond by adding a Management Response", posted "directly underneath the traveler review" and "visible to anyone looking at the website".</p>
<p>What gets a response rejected, and replies worth copying, are in <a href="/blog/how-to-respond-to-a-bad-tripadvisor-review/">how to respond to Tripadvisor reviews</a>; how to ask for one is in <a href="/blog/tripadvisor-review/">how to get more Tripadvisor reviews</a>.</p>
<h2 id="yelp-online-restaurant-reviews-and-ratings">Yelp restaurant reviews and ratings</h2>
<p>Yelp carries real weight for restaurants in US markets and close to none elsewhere, so whether it belongs on your list is a geography question. The costly mistake is asking, and Yelp buries the rule in the conflicts-of-interest bullet of its <a href="https://www.yelp.com/guidelines" rel="noopener">content guidelines</a>.</p>
<p><img src="/images/blog/restaurant-review-sites/yelp-never-ask-for-reviews.png" alt="Yelp&#x27;s content guidelines, conflicts of interest section, ending with the bolded sentence &#x22;Businesses should never ask customers to write reviews.&#x22;"></p>
<p>So Yelp is a site you read and answer, never one you feed.</p>
<p>Answering is simple once the page is claimed. Yelp says that "if you've claimed your business page, you can reply to your reviews by clicking Respond, Direct message, or both", and that "responses are public and appear below the review". When one needs to come down instead, <a href="/blog/how-to-delete-yelp-review/">what actually works on a Yelp review</a> covers the grounds that succeed.</p>
<h2 id="facebook-restaurant-reviews">Facebook restaurant reviews</h2>
<p>Facebook still earns its place for a suburban venue, where the local audience genuinely lives and the Page often does more work than the website.</p>
<p>The rating is a Recommendation percentage rather than stars, and anyone logged in can leave one. Meta does "not verify that users purchased the product or used the service that they are reviewing".</p>
<p>Two rules decide whether the number on your Page moves at all. <a href="https://www.facebook.com/help/500762053364226" rel="noopener">Meta says</a> "a Page may not have a rating if it hasn't received at least five reviews", and that "only recommendations that are shared publicly are included in a Page's overall rating". So a regular who writes something lovely and posts it to friends only has changed nothing.</p>
<p>Meta publishes no rule on asking, and nothing at all on how a Page replies. The settings path is in <a href="/blog/facebook-reviews/">Facebook reviews for business</a>.</p>
<h2 id="opentable-reviews">OpenTable reviews</h2>
<p>OpenTable is the closed loop, and it behaves differently from everything above it.</p>
<p>Only a diner who ate can review you. OpenTable's help centre is explicit: "only diners who booked and honored a reservation through OpenTable can leave a review", tied to that reservation in the account that booked it. The diner signs into that account, opens their past reservations, picks the one they want to review and leaves star ratings, written comments, optional photos and an optional private note to you. Moderation can take up to 72 business hours. Diners can edit or delete their own review afterwards, but a deleted one cannot be replaced.</p>
<p>A cancelled booking gets no review option. Neither does a guest who came along on somebody else's reservation, or anyone who rang you directly or walked in.</p>
<p>That is why your OpenTable review count looks thin beside your covers. On a 120-cover Saturday where thirty tables came through OpenTable, thirty diners get asked and ninety do not. Star-only ratings count towards your score but never appear on the public profile. And the Ratings and Reviews section does not show at all until you have been listed 30 days or collected ten reviews with comments, whichever lands first.</p>
<p>You do not send the request. OpenTable sends it the day after the reservation is marked seated, or automatically updated to assumed seated, by email and push notification. The operator's lever is not the ask. It is making sure bookings actually run through OpenTable and get marked seated on the night. Correct a no-show to seated after the fact and the guest can still review from their account, they just never get prompted.</p>
<p>The reply rules are the strictest of the nine.</p>
<ul>
<li>One public response per review. Everything after that goes privately to the guest.</li>
<li>No editing, ever. Responses "won't be removed regardless of mistakes, including typos or posting the response to the wrong review".</li>
<li>Public responses show on your OpenTable profile on the desktop site only, not in the app.</li>
<li>You can reply privately to a star-only rating that carries no comment, and that reply is not published.</li>
<li>Links and email addresses are allowed in private responses and not in public ones.</li>
</ul>
<p>The rating window catches people out too. In the United States, Canada and Mexico the score runs on a rolling 120 days, and outside North America on 365, counted from the reservation date rather than the date the guest wrote.</p>
<p>Report a review that breaks the rules to <a href="mailto:reviews@opentable.com">reviews@opentable.com</a>, with the text, the dining date and your reason. What OpenTable will not have is you going round the outside: "never directly contact a guest to ask them to remove or alter a review."</p>
<h2 id="zomato-reviews">Zomato reviews</h2>
<p>Check the market before you spend a minute here. Zomato's home page on 6 September 2026 calls it "India's #1 food delivery app", covering 800-plus cities. If your venue is not in India, Zomato is not your list, whatever a 2022 article told you.</p>
<p>Where it does operate, anyone with an account can review and Zomato polices it after the fact. Its <a href="https://www.zomato.com/policies" rel="noopener nofollow">guidelines for restaurants</a> are the bluntest of the nine. "Selective solicitation is a strict NO." So is offering freebies, asking staff to compete with each other to collect reviews, and hiring anyone who offers to fix your ratings.</p>
<p><img src="/images/blog/restaurant-review-sites/zomato-selective-solicitation-disclaimer.png" alt="Zomato&#x27;s Guidelines for Restaurants, headed &#x22;Don&#x27;t solicit reviews&#x22;, listing prohibitions on offering freebies for reviews, incentives to remove reviews and staff review competitions, and ending with a line saying Zomato will activate a disclaimer on the restaurant&#x27;s page informing the community that its reviews are suspicious"></p>
<p>The penalty is the part nobody quotes: "we will activate a disclaimer on your restaurant's page, informing the Zomato community that your reviews are suspicious." No other platform on this list punishes asking in public, on your own page, where your next customer will read it.</p>
<p>You get one management response, and Zomato's warning about it is worth taking literally: "your response can't be edited after posting, so choose your words well."</p>
<h2 id="uber-eats-doordash-and-delivery-ratings">Uber Eats, DoorDash and delivery ratings</h2>
<p>A delivery rating is not a restaurant review, and treating it as one is how kitchens end up chasing a number they cannot move.</p>
<p>DoorDash publishes the most detail. A public review tied to an order carries a "Verified Order" label, and only customers in selected US, Canada and Australia markets can leave one. The scale is not stars: it is Loved, Liked or Didn't Like, with tags for parts of the experience. You reply privately, from the Merchant Portal, within seven days. There is no public reply and no opt-out, and reviews that "focus primarily on delivery issues (such as delivery time or food temperature), which are outside a merchant's control" may be rejected in moderation.</p>
<p>Uber Eats cannot be described honestly from the outside. Uber's merchant help centre demands a "log in with your store's account" before it will show its articles on customer feedback, so this piece will not tell you what that dashboard offers. Open Uber Eats Manager and look.</p>
<h2 id="the-infatuation-and-the-sites-you-cannot-work">The Infatuation, and the sites you cannot work</h2>
<p>The Infatuation is on this list for a different reason: it is real, and there is nothing you can do about it. Its reviews are staff-written and scored out of ten across a handful of cities including New York, Los Angeles, Chicago, London and San Francisco. There is nothing to claim and nowhere to reply.</p>
<p>Other directories older guides still name have quietly closed, Foursquare's city guide among them; the <a href="/blog/review-sites-for-service-businesses/">dead ones are listed here</a>. For whatever survives, the test is whether a diner has ever mentioned it. If not, keep the listing accurate and stop.</p>
<h2 id="where-to-send-the-ask">Where to send the ask</h2>
<p>Concentrating the ask beats spreading it. A venue with 300 Google reviews and 8 on Tripadvisor reads as busy. The same venue with 40 spread over six platforms reads as quiet everywhere.</p>
<p>Google takes the ask at every venue, on every service. Tripadvisor takes it second, but only if travellers are a real share of your covers: a harbourside bistro like Bramble &#x26; Rye sends the ask there, a suburban pizzeria three streets from the station does not. Nowhere else, by design. OpenTable has already asked, Yelp forbids it, and Zomato will label your page for it.</p>
<p>Ask every diner the same way at the same point after the meal. Never build a step that routes happy diners to the review link and unhappy ones to a private form: that is review gating, and Google's <a href="https://support.google.com/contributionpolicy/answer/7400114" rel="noopener">prohibited content policy</a> tells merchants not to "selectively solicit positive reviews from customers". The timing that works is in <a href="/blog/get-more-google-reviews/">how to get more Google reviews</a>.</p>
<h2 id="running-this-across-several-venues">Running this across several venues</h2>
<p>Nothing here lets you answer once for a group. Each venue has its own Google Business Profile, its own Facebook Page needing five reviews before a rating appears, its own Tripadvisor listing and its own OpenTable profile, so a four-venue group is four logins per platform.</p>
<p>Sort the queue by how permanent the reply is rather than by how bad the review is. Google is editable; Zomato and OpenTable are not, and OpenTable will not take a response down even when you post it under the wrong review. Answer the one-shot sites when you are calm and Google whenever you have ten minutes.</p>
<p>Then fix the listings before you widen the list of sites. Most one-star reviews at multi-venue groups are about a locked door, a wrong number, or hours that changed at Easter and never changed back. Our <a href="/blog/examples-of-bad-reviews/">worked examples of bad reviews</a> show what those replies look like, and the whole programme across venues is in <a href="/blog/restaurant-reputation-management/">restaurant reputation management</a>.</p>
<p>If reading them all is the bottleneck, that is what software is for. Cloutly reads 39 review sites, Google, Facebook, Yelp, Tripadvisor, Booking.com and Zomato among them, brings every venue's reviews into one inbox you can filter by location, and publishes hours, phone and address to Google Business Profile and Facebook while watching Yelp, Tripadvisor and Google's public view for <a href="/listings-management">drift</a>. OpenTable and the delivery apps are not among the 39, so you still open those yourself. More for venues is on our <a href="/solutions/hospitality">hospitality page</a>.</p>
<h2 id="frequently-asked-questions">Frequently asked questions</h2>
<h3 id="what-is-the-best-restaurant-review-site">What is the best restaurant review site?</h3>
<p>Google, for almost every restaurant in almost every market. It is the only one here that both encourages you to ask customers and lets you edit your reply afterwards.</p>
<h3 id="can-a-restaurant-ask-customers-for-reviews">Can a restaurant ask customers for reviews?</h3>
<p>That depends on the site. Google encourages it and suggests a link or a QR code. Yelp tells businesses never to ask. Zomato answers selective asking with a public disclaimer on your page. OpenTable sends the request itself the day after a seated reservation. Offering a discount or a free item in exchange is banned by Google outright.</p>
<h3 id="how-do-i-leave-a-review-on-opentable">How do I leave a review on OpenTable?</h3>
<p>Sign into the OpenTable account that made the booking, open your past reservations, choose the meal and follow the prompts on the site or in the app. You can only review a reservation you booked through OpenTable and turned up to, so a cancelled booking or a table someone else reserved gives you no option.</p>
<h3 id="do-uber-eats-and-doordash-ratings-affect-my-google-rating">Do Uber Eats and DoorDash ratings affect my Google rating?</h3>
<p>No. They are separate scores on storefronts those platforms own, tied to a delivery order rather than to a profile you control, and they never appear in the Google result a diner sees when they search your restaurant by name.</p>]]></content:encoded></item><item><title><![CDATA[How Tripadvisor ratings and rankings actually work]]></title><description><![CDATA[Your Tripadvisor rating and popularity ranking are different numbers. One summarises review scores; the other compares you with nearby businesses.]]></description><link>https://cloutly.com/blog/tripadvisor-ratings/</link><guid isPermaLink="false">6522999a9367088c7bbd1819</guid><category><![CDATA[Tripadvisor]]></category><category><![CDATA[Reviews]]></category><category><![CDATA[Restaurants]]></category><dc:creator><![CDATA[Lachlan Fea]]></dc:creator><pubDate>Mon, 27 Jun 2022 00:45:35 GMT</pubDate><media:content url="/images/blog/tripadvisor-ratings/tripadvisor-ratings-feature-cover-2026.jpg" medium="image"/><content:encoded><![CDATA[<img src="/images/blog/tripadvisor-ratings/tripadvisor-ratings-feature-cover-2026.jpg" alt="How Tripadvisor ratings and rankings actually work"><p>A Tripadvisor rating is the bubble score shown on your listing. Popularity ranking is your position against similar businesses in the same destination. They are related, but they are not the same calculation. That is why a hotel's rating can stay at 4.5 while its local rank moves from 12th to 9th, or the other way around.</p>
<p>Tripadvisor says popularity ranking is based on four things: review quality, recency, quantity and consistency. It recalculates the ranking daily and compares a business with its local competitors.</p>
<h2 id="rating-and-popularity-ranking-are-different">Rating and popularity ranking are different</h2>
<p>The rating is an easy summary for a traveller. Popularity ranking is a relative position, such as number 8 of 143 hotels in a destination.</p>




















<table><thead><tr><th>Number</th><th>What it tells a traveller</th><th>Why it changes</th></tr></thead><tbody><tr><td>Traveller rating</td><td>The overall review score shown on the listing</td><td>New review scores change the underlying average</td></tr><tr><td>Popularity ranking</td><td>How the business compares with similar nearby listings</td><td>Your review pattern and competitors' review patterns both change</td></tr></tbody></table>
<p>The second row is where confusion starts. You can improve and still fall if nearby competitors improve faster. You can also climb without a visible change in the bubble score because recent, consistent reviews affect the relative ranking before the rounded display moves.</p>
<h2 id="the-four-ranking-inputs">The four ranking inputs</h2>
<p>Tripadvisor explains the inputs in its <a href="https://www.tripadvisor.com/business/en-gb/insights/resources/tripadvisor-popularity-ranking" rel="noopener">popularity-ranking guide</a>.</p>
<h3 id="quality">Quality</h3>
<p>Higher review scores help. There is no credible shortcut around the experience itself. A queue at check-in, a room that does not match the photographs or a bill nobody can explain will surface in reviews no matter how polished the request is.</p>
<h3 id="recency">Recency</h3>
<p>Newer reviews carry more weight than older ones. A strong year from long ago does not protect a venue forever, and a difficult month does not define it forever either. Recent reviews tell travellers and Tripadvisor what the experience is like now.</p>
<h3 id="quantity">Quantity</h3>
<p>Tripadvisor needs enough reviews to compare businesses with statistical confidence. More reviews can help, but raw volume does not beat quality. A venue cannot bury repeated poor experiences under a large campaign and expect the ranking to ignore them.</p>
<h3 id="consistency">Consistency</h3>
<p>A steady pattern is more convincing than bursts separated by silence. That does not mean forcing a quota. It means giving every eligible guest the same honest opportunity to review at a sensible point in the journey.</p>
<h2 id="why-your-rating-stayed-the-same">Why your rating stayed the same</h2>
<p>Tripadvisor displays a rounded rating. The underlying numbers can change without crossing the next visible threshold. A new five-star review may improve the average but leave the page showing 4.5. A low score may reduce the average without immediately changing that display.</p>
<p>At the same time, popularity rank can move because:</p>
<ul>
<li>your recent mix changed</li>
<li>a nearby competitor received new reviews</li>
<li>the comparison set changed</li>
<li>several days of review activity altered the consistency pattern</li>
<li>the daily ranking calculation caught up with recent submissions</li>
</ul>
<p>Do not reverse-engineer a hidden formula from one day's movement. Tripadvisor does not publish the weights or a calculator, and any article offering an exact equation is guessing.</p>
<h2 id="do-management-responses-improve-the-ranking">Do management responses improve the ranking?</h2>
<p>No direct boost is promised. Tripadvisor says management responses are not a popularity-ranking factor.</p>
<p>They still matter. A measured response helps the next traveller understand what happened, shows that the property is paying attention and gives you room to explain a genuine change. That is a conversion and trust job, not a ranking trick.</p>
<p>Tripadvisor's <a href="https://www.tripadvisor.com/business/insights/hotels/resources/add-management-responses-to-reviews" rel="noopener">management-response guidance</a> also makes an operational point: a response can be deleted and submitted again, but it cannot simply be edited after publication. Check names, dates and promises before sending it.</p>
<p>For worked replies, use <a href="/blog/how-to-respond-to-a-bad-tripadvisor-review/">how to respond to a bad Tripadvisor review</a>. If the review appears to break a rule, follow the <a href="/blog/remove-tripadvisor-review/">Tripadvisor removal process</a> rather than arguing about it in public.</p>
<h2 id="what-a-venue-can-improve-this-month">What a venue can improve this month</h2>
<p>Start with the review language, not the rank.</p>
<ol>
<li>Read the newest 30 reviews and tag repeated themes.</li>
<li>Separate one-off complaints from patterns.</li>
<li>Give each pattern to someone who can change the operation.</li>
<li>Reply where context or service recovery helps a future guest.</li>
<li>Invite eligible guests consistently, without incentives or rating selection.</li>
<li>Review the trend monthly rather than reacting to daily movement.</li>
</ol>
<p>If “friendly staff” appears every week, recognise the team and protect what is working. If “nobody answered at night” appears across several reviews, fix the contact expectation. If complaints jump between properties, analyse them by location rather than hiding them inside a group average.</p>
<h2 id="can-you-calculate-how-many-reviews-you-need">Can you calculate how many reviews you need?</h2>
<p>You can calculate how new scores affect a simple arithmetic average. You cannot calculate a guaranteed Tripadvisor popularity position because the published method is relative and the weights are not public.</p>
<p>That distinction saves a lot of pointless spreadsheet work. Use arithmetic to understand the displayed average, and use operations to improve the things guests keep describing. The <a href="/blog/hotel-review-sites/">hotel review-site guide</a> shows where Tripadvisor sits beside Google and booking platforms.</p>
<h2 id="the-useful-way-to-read-the-numbers">The useful way to read the numbers</h2>
<p>Watch three things together:</p>
<ul>
<li>the visible rating over time</li>
<li>popularity rank against the right local comparison set</li>
<li>the themes inside recent reviews</li>
</ul>
<p>The first tells you the summary. The second tells you how you compare. The third tells you what to do next. Only the third one gives the morning meeting something it can actually fix.</p>]]></content:encoded></item><item><title><![CDATA[The hotel review sites worth a hotelier's attention]]></title><description><![CDATA[Hotels do not need to chase every review site. They need to know which profiles guests actually see, who can review, and where a reply is worth the time.]]></description><link>https://cloutly.com/blog/hotel-review-sites/</link><guid isPermaLink="false">6522999a9367088c7bbd1806</guid><category><![CDATA[Reviews]]></category><category><![CDATA[Restaurants]]></category><dc:creator><![CDATA[Lachlan Fea]]></dc:creator><pubDate>Fri, 13 May 2022 04:14:02 GMT</pubDate><media:content url="/images/blog/hotel-review-sites/hotel-review-sites-feature-cover-2026.jpg" medium="image"/><content:encoded><![CDATA[<img src="/images/blog/hotel-review-sites/hotel-review-sites-feature-cover-2026.jpg" alt="The hotel review sites worth a hotelier's attention"><p>Most hotels need to pay close attention to five places: Google, Tripadvisor, Booking.com, the Expedia Group network and Facebook. The order changes by market and distribution mix, but the job does not. Keep the profile accurate, understand who can leave a review, respond where guests will read it and do not ask for something the platform forbids.</p>
<p>You do not need another list of 30 travel websites. You need to know which five deserve a place in the weekly operating rhythm.</p>
<h2 id="the-short-list">The short list</h2>









































<table><thead><tr><th>Site</th><th>Where reviews come from</th><th>Can the hotel ask?</th><th>What the team controls</th></tr></thead><tbody><tr><td>Google</td><td>People with a Google account</td><td>Yes, for honest reviews</td><td>Business Profile details, review link and responses</td></tr><tr><td>Tripadvisor</td><td>Tripadvisor contributors</td><td>Yes, within Tripadvisor's rules</td><td>Listing details, responses and eligible review-collection tools</td></tr><tr><td>Booking.com</td><td>Guests connected to a booking</td><td>The platform handles the post-stay invitation</td><td>Property content and responses where available</td></tr><tr><td>Expedia Group</td><td>Travellers after a completed stay</td><td>The platform solicits after checkout</td><td>Property content and approved management responses</td></tr><tr><td>Facebook</td><td>Facebook users where Recommendations are enabled</td><td>Yes, without incentives or selection</td><td>Page details, Recommendations setting and replies</td></tr></tbody></table>
<p>Google and Tripadvisor are public discovery surfaces. Booking.com and Expedia reviews sit much closer to the booking decision because the guest is already comparing rooms and rates. Facebook matters most where the Page has a real local audience. Treating them as interchangeable creates messy reporting and worse requests.</p>
<h2 id="google">Google</h2>
<p>Google is usually the first profile to fix because its rating appears beside the hotel's map result, photos, phone number and booking options. Guests do not need to have booked through Google to review, which makes the profile broad and easy to use.</p>
<p>Check the primary category, map pin, phone, website, check-in and check-out times, amenities and photos. Then create the hotel's Google review link and use it consistently after stays. Google allows review requests but prohibits incentives, fake engagement and selective practices that distort the rating. Its <a href="https://support.google.com/business/answer/3474122" rel="noopener">review guidance</a> covers the request link and incentive rule.</p>
<p>If the hotel has several properties, work location by location. A group average can hide a broken breakfast service in one building and a front-desk team doing exceptional work in another.</p>
<h2 id="tripadvisor">Tripadvisor</h2>
<p>Tripadvisor is still its own operating channel, not just another star score. It shows both a traveller rating and a popularity ranking relative to nearby properties. Those numbers can move differently, which is why teams often think something is wrong when the displayed rating stays flat but the rank changes.</p>
<p>Claim the listing, keep property details current and answer substantive reviews. Tripadvisor's ranking uses the quality, recency, quantity and consistency of reviews, not management-response volume. The full explanation is in <a href="/blog/tripadvisor-ratings/">how Tripadvisor ratings and rankings work</a>.</p>
<p>Tripadvisor permits its own review-collection tools and links. Keep the invitation neutral. Do not offer a free drink, late checkout or competition entry for a review.</p>
<h2 id="bookingcom">Booking.com</h2>
<p>Booking.com reviews come through the booking relationship, so they carry a different kind of proof from an open review site. The platform invites eligible guests after their stay under its own <a href="https://partner.booking.com/en-gb/help/property-guest-experience/reviews/guest-review-process-and-conditions" rel="noopener nofollow">guest review process</a>.</p>
<p>The hotel should concentrate on the parts it controls: accurate property information, expectations before arrival, service recovery during the stay and a useful public response afterwards. Do not send a separate campaign pretending that anyone can leave a Booking.com review. Eligibility belongs to Booking.com.</p>
<p>Look at review sub-scores and recurring language, not only the headline number. “Clean room, impossible check-in” is an operations note hiding inside a good average.</p>
<h2 id="expedia-hotelscom-and-orbitz">Expedia, Hotels.com and Orbitz</h2>
<p>Expedia, Hotels.com and Orbitz are Expedia Group brands. They should be monitored as a network rather than counted as three unrelated reputation programmes. Expedia Group's <a href="https://www.expediagroup.com/en-us" rel="noopener nofollow">official brand list</a> shows the relationship.</p>
<p>Expedia says its reviews come from verified travellers after a completed stay, and its property systems support management responses. Its <a href="https://connectivityportal.expediagroup.com/documentation/expedia/property_mgmt_apis/reviews/intro" rel="noopener nofollow">reviews documentation</a> says the company solicits feedback after checkout.</p>
<p>For the hotel team, the practical work is familiar: correct content, clean distribution data, prompt issue handling and a response that tells the next guest what changed. Do not assume one reply appears identically across every brand and market. Check the live property page.</p>
<h2 id="facebook">Facebook</h2>
<p>Facebook Recommendations are useful when the hotel already has an active Page, runs events or serves a strong local market. They are less central for a property whose demand comes almost entirely through travel search and online travel agencies.</p>
<p>Keep the Page details and Message button honest. If nobody checks Messenger overnight, say when it is read or <a href="/blog/how-to-turn-off-messenger-on-facebook-business-page/">turn Page messaging off</a> and show the booking or front-desk contact instead. The <a href="/blog/facebook-reviews/">Facebook reviews guide</a> explains Recommendations and their controls.</p>
<h2 id="do-not-spread-the-team-across-every-directory">Do not spread the team across every directory</h2>
<p>Add another review site to the weekly list only when at least one of these is true:</p>
<ul>
<li>it sends bookings you can identify</li>
<li>it ranks for the hotel or destination in your market</li>
<li>guests repeatedly mention it at the property</li>
<li>the hotel has an accurate, claimable profile there</li>
<li>a distribution agreement makes it operationally important</li>
</ul>
<p>A smaller list with clear ownership beats a dashboard full of profiles nobody acts on.</p>
<h2 id="a-weekly-review-routine">A weekly review routine</h2>
<p>Give one person responsibility for the queue, with cover for days off.</p>
<ol>
<li>Check new reviews by property and source.</li>
<li>Escalate safety, discrimination, privacy and active-stay issues immediately.</li>
<li>Reply to reviews where a response helps the next guest.</li>
<li>Tag recurring themes such as check-in, noise, cleanliness and breakfast.</li>
<li>Send the relevant theme to the person who can change it.</li>
<li>Check that the property's contact and booking details are still correct.</li>
</ol>
<p>For a group, a shared inbox makes the queue easier to own, but the reply should still sound like the hotel. The broader <a href="/solutions/hospitality">hospitality reputation approach</a> is useful when the problem spans several venues or properties.</p>
<p>The aim is not to collect the same review everywhere. It is to understand where each review comes from and do the work that particular platform lets the hotel do.</p>]]></content:encoded></item></channel></rss>