Hotel online reputation management: a weekly routine for a small team

Hotel online reputation management is the weekly work of collecting what guests say on every site they use, replying in their language, tagging each review by topic and department, and sending repeated causes to the team that can fix them. It is an operating routine, not a marketing campaign.

A guest writes three lines about a cold breakfast and a slow check-in. The review appears on two sites. Nobody in the hotel sees it for eleven days, and the reply that finally goes out is in the wrong language and promises a fix no department has been asked to make. This is not a staff problem. It is a missing routine. After reading this article you will be able to set up a weekly reputation routine for a small team: what to collect, how to tag it, who replies to what, which four numbers to track, and what the 2026 review rule in Türkiye means for your daily work.

What is hotel online reputation management made of?#

It is everything a guest can read about your hotel without asking you: review scores and comments, map and place listings, complaint platforms, social posts, and the answers you write under all of them.

The surfaces differ in audience and in how long they matter. A booking-site review is read by someone comparing two hotels tonight. A map listing is read by someone already nearby. A complaint platform is read by someone who has a problem and is looking for company. A social comment is read once and buried. Treating all of them as "reviews" wastes the different value each one carries.

Separate what the hotel controls from what it does not. You do not control who reviews, the score they give, or the order a site displays results in. You do control the reply, the fix behind it, the accuracy of your listing (photos, amenities, check-in times, parking), and whether and how you invite a review. This distinction decides where your hour goes.

Reputation is not one number. For example, the same hotel can sit at 8.6 on one site and 4.2 on another because the guest mix and the questions asked differ. A blended score hides which surface is costing you bookings. A review is a sample of one stay, not a measurement of the hotel: the guest who writes is not the average guest, and a quiet month with no reviews is not evidence of quality.

Keep reputation and operation apart on paper and joined in practice. Reputation is what people say. The operation is what happened. Reputation work only pays when the second one changes. In a small hotel the roles are simple: front office owns the reply, department heads own the cause, the general manager owns the loop between them.

The review is written at the end of a journey the hotel designed, so most review topics trace back to a stage: arrival, room, food, departure. That mapping is what makes tagging possible later, and it is worth reading our guide to designing the guest journey stage by stage before you build your tag list.

Why does review work slip in a small hotel?#

Because it is nobody's named job, it has no fixed time, and the visible output (a reply) is easy while the real outcome (a fixed cause) is not.

The default state is easy to recognise. Replies are written in batches when someone notices, often weeks late, by whoever is on shift. By then the guest has forgotten the stay and the department has no reason to act. The fix is structural, not motivational: one owner, one fixed hour, one log, one monthly meeting. Nothing in that list needs new software.

No owner. "Front office" is a shift, not a person. Name one person and one backup, and put both names in the routine. No log. Reviews sit in five browser tabs, so nobody counts topics, and the same complaint (bar noise, weak Wi-Fi on the third floor, a tired mattress in one wing) repeats for a year without anyone seeing the pattern.

The reply is treated as public relations. It is written to look good to future guests instead of routing the cause to housekeeping, maintenance or the kitchen. Language slips too: replies go out only in Turkish under English and Russian reviews, or a machine translation is posted without anyone reading it first. And fear keeps staff away from unfair reviews, so the only unanswered ones end up being the angry ones, which is exactly the wrong pattern for a reader to see.

What does a weekly reputation routine look like?#

Four short blocks a week, roughly two hours in total, done by a named person at a fixed time, plus one monthly meeting.

Monday, collect. Open every surface the hotel is on and copy new reviews into one log. A spreadsheet is enough: site, date, score, language, stay dates if the guest gave them, the text, and the reply status. Monday, route. Give each review one or two topics and a department, then send the operational ones to that department the same day as a question ("did we have a problem with hot water on the fourth floor on these dates?"), not as a verdict.

Tuesday to Wednesday, reply. Draft replies for the week's reviews in the reviewer's language. Anything touching money, safety, staff conduct or legal matters waits for the general manager. Thursday, check the ask and the listing. Confirm the review invitation is going out at the right moment, usually at or after checkout, and that nobody is standing over the guest while they write it. Check that photos, hours and amenities on each listing are still true.

Friday, count. Fifteen minutes: new reviews per site, replies posted, replies still open, and the topics that appeared more than once. The block has to be in the calendar with the backup's name on it, or it will be the first thing dropped on a busy week. In a bad week, do not wait for a perfect answer: reply with what you know and when you will know more, then follow up when the investigation closes.

How do you tag reviews so the right team sees them?#

Give every review one topic from a short fixed list and one department, so that the count by topic becomes the hotel's list of things to fix.

A fixed list of ten to twelve topics beats free text, because free text cannot be counted. Keep it short enough that a receptionist can apply it in ten seconds. One review, at most two topics: more than two usually means the whole stay failed, which is itself a signal worth flagging separately.

Map every topic to a department: housekeeping, technical or maintenance, food and beverage, front office, management. A topic with no department is a topic nobody fixes. Record whether the review describes a one-off or a pattern. A pattern needs a date range and a location (which wing, which floor, which shift), not a mood.

Keep reviews in the same log as guest requests and complaints. A review is a complaint that arrived late, and it belongs next to the ones that arrived at the desk; the mechanics are covered in our guide to logging, assigning and closing each guest request. Count weekly, read monthly. "Eleven reviews mentioned noise in six weeks, eight of them on the pool side" is a work order. "Guests complain about noise" is not. Never tag by score: a 9 with a specific complaint inside is more useful than a 3 with nothing in it.

Three checks before a review leaves the desk: it has exactly one department, it has no more than two topics, and any tag with three or more mentions in a month has a named owner.

How should you reply to hotel reviews?#

In the language the guest wrote in, within a day or two, short and specific, with no personal data, and only after the department has confirmed what happened.

Language first. Reply in the review's language. If nobody on the team writes it, a short honest reply through a checked translation beats a long one in Turkish that the reader cannot use. Structure the reply in three to five sentences: thank the guest, name the specific thing they raised, say what changed or what you will check, and give one route back to the hotel. Generic paragraphs read as templates and are treated as such.

Personal data stays out. No full name beyond the display name, no room number, no stay dates, no bill or deposit figures, no health or family details. Data protection applies to what you publish as much as to what you store. Do not argue about facts in public: if the review is wrong, correct one point calmly and move the rest to a private channel.

Set an approval rule and keep it small. Routine replies can be posted by the owner of the routine; anything mentioning money, safety, staff conduct or legal matters goes to the general manager. For unfair or fake reviews, use the site's own reporting process, reply once and briefly, keep the evidence, and stop. Never offer anything in exchange for removal. Draft the same day, post the next working day: the gap is where the facts get checked. For concrete wording by complaint type, see our article with example replies by complaint type.

Which numbers should you track, and how do you review them monthly?#

Four numbers, read once a month and compared with the same month a year earlier: score per site, new reviews per site, reply time, and the count of repeated topics.

Score per site, never blended. A score moving from 8.4 to 8.6 on six reviews is noise, not progress, and a blended figure hides which surface is losing you bookings. Volume matters too: how many new reviews each site received. A falling count with a stable score usually means fewer guests are being asked, not that guests are happier.

Reply time. Median working days from publication to reply, per site. Choose an internal target, for example two working days, and hold it. Repeated topics: the count by tag per month, and whether the same tag appears three months running. That is the number that changes the operation.

Sample size. On a small hotel one 1-star review can move the average more than a month of good work. Read direction over three to six months, not week to week. Leave out anything you cannot verify yourself: a single reputation score from a tool, ranking positions, and any effect on price or bookings that you have not measured in your own hotel.

The monthly meeting: 45 minutes in the first week, the general manager plus housekeeping, technical, food and beverage and front office. Agenda: the month's four numbers, the top three repeated topics, what was fixed last month and whether the reviews noticed, and one fix for next month with a name and a date. To feed the same meeting with your own survey data, see our guide to the guest satisfaction survey: questions, timing and follow-up.

What does Turkish law say about hotel reviews in 2026?#

Since 1 August 2026, Türkiye's advertising rules set conditions on review areas that sellers and providers run online: who may review, how long reviews stay up, and paid untrue reviews.

The source is amended Article 28/B of the Commercial Advertising and Unfair Commercial Practices Regulation, published in the Official Gazette on 1 July 2026, No. 33297 (opens in a new tab), in force 1 August 2026. Only people who bought the goods or service may review. Reviews stay published for at least one year, and positive and negative reviews may not be separated. If the provider resolves the complaint and this is reported, the resolution is published after verification in the same place as the original review.

Nobody may be paid or engaged to write untrue reviews. That bans paying or engaging anyone to write untrue reviews, and it also rules out separating the bad ones out of a widget the hotel controls. The operational consequence is a record: "the provider resolved the complaint and this is reported" needs evidence, so keep a written note of what was fixed, when, and by whom.

What is not settled here: whether the article covers a hotel's replies on third-party review sites was not verified, and this article states no response deadline for complaint platforms. Confirm dates, penalties and your own case with a legal adviser. Nothing in this rule says how any site orders hotels; do not read it as a ranking factor.

What to do next#

Put a one-hour block in next Monday's calendar, name one owner and one backup, and open the log with the last thirty reviews you can still find. The routine is the method: collect, tag, route, reply, count, and meet once a month to turn the count into one fix with a name and a date.