Online reputation management
What do customers find when they check your business?
Start with the evidence a customer can see.
A recommendation often leads to a search. Someone checks your business name, reads a few reviews and looks for evidence that you can do the job. Your own website is only part of the picture. Business profiles, public replies, directory entries and other people’s accounts also shape that decision.
Online reputation management means checking that picture, correcting what you control and addressing the experiences behind it. A higher star average cannot repair a broken booking process. A good service can still lose enquiries when its address or contact details are wrong.
Make a short, usable record.
Search your business name and the services customers associate with it. Check the important results and profiles directly. For each issue, record the URL, date, exact problem, who can act and the next step. Keep private customer details out of any shared public document.
Rank the work by its effect.
A wrong phone number can stop every caller. An unresolved complaint may reveal an urgent service failure. An obscure old mention may matter less. Fix clear errors quickly; investigate allegations before treating them as established facts.
Correct, respond or report?
These are different jobs. Match the action to the evidence instead of treating every unfavourable result as something to remove.
You control an inaccurate detail.
Correct it at its source: your website, your verified business profile or the directory’s editing process. Then reopen the public page and check the result. If several listings repeat the mistake, record and verify each correction.
A customer describes a real problem.
Check the relevant records, acknowledge what you know and offer a practical next step. A reply should help the customer and show future readers how you handle problems. It is not a courtroom argument with the reviewer.
The content appears to break a platform rule.
Record the specific rule and report through that platform. Google accepts review removal requests for policy violations; disliking a negative review is not a reason for removal. Use its review reporting process and check the decision in the Reviews Management Tool. Eligible rejected requests can be appealed once. Reporting does not guarantee removal.
Worked example
A useful reply makes the next step clear.
Imagine a customer says a repair appointment was missed and nobody called. This is an invented example. Check the booking and contact records before claiming you know what happened.
If the records confirm the failure
“We missed the appointment and did not update you. I’m sorry. Please contact our service desk through the number on our website and ask for the service manager, so we can arrange the next step.”
If the facts are still unclear
“I’m sorry this has been frustrating. We would like to check the booking and understand what happened. Please contact our service desk through the number on our website so we can review the details privately.”
Adapt the wording to the facts and to a contact route that actually works. Promise a response time only when someone can meet it. Do not post names, booking references, medical details or other private information to prove your side. Google’s reply guidance recommends clear, relevant responses and moving sensitive details to a private conversation.
Change the promise that keeps causing complaints.
Replies can address an incident. Repeated incidents need an operational fix. Look for a common failure, then test the explanation against actual cases. Several complaints about timing may have different causes; do not assume one pattern explains all of them.
Example: “You promised Friday.”
Suppose order records show that the website calls Friday a delivery date, but the warehouse treats it as a dispatch date. That mismatch is a testable cause. Confirm it across the relevant orders before changing the process.
Make the correction visible.
Clarify the delivery estimate before purchase and in the confirmation. Give staff the same explanation. Check subsequent orders and complaints to see whether the misunderstanding continues. A rewritten apology alone leaves the original promise in place.
Build proof without manufacturing praise.
Ask for honest reviews.
Invite customers with genuine experience to leave an honest review. Use a consistent approach instead of asking only people you expect to be positive. Google prohibits incentives for reviews, selective solicitation of positive reviews and rewards for changing or removing negative reviews under its fake engagement policy.
Make the invitation optional. Do not write the review for the customer or pressure them to give a particular rating.
Show work buyers can evaluate.
Keep service details current. Explain the job, the relevant constraints and what was delivered in real examples you have permission to publish. Use accurate photographs and specific evidence. Remove unsupported claims rather than surrounding them with more promotional copy.
This gives a buyer more to judge. It does not let you choose the order of search results or guarantee that an unfavourable page disappears.
Judge progress by what was resolved.
Review the issue record regularly. Count incorrect details still visible, complaints awaiting a next step and recurring problems after a fix. Give each open item an owner and a review date. Confirm closure from the customer’s side of the process, not just from a completed internal task.
Track review volume, ratings and enquiries as context. A changed average or an increase in enquiries does not prove that a particular reply caused the change. The clearest evidence is often simpler: the phone number works, the customer received help and the misleading promise has been corrected.
Start with one visible problem you can verify and resolve. That creates something more useful than a reputation report: a better reason for the next customer to trust you.