A relationship can affect review independence
Google’s Maps policy says content based on a conflict of interest can be misrepresentation. It notes that conflicts may include current or former employment, contractual or consulting relationships, and other professional or personal affiliations.
The policy does not mean every comment from a known person will disappear automatically. The business should document the relationship and explain why it makes the review biased or misleading. Google evaluates the report and decides whether the content violates policy.
Confirm identity and relationship carefully
A familiar display name is a starting point, not a conclusion. Verify the person through appropriate records and consider whether another person could share the name. Record employment or contract dates and the nature of the relationship without copying unnecessary personnel information.
Involve human resources or legal leadership when the evidence comes from protected records. The review-management team needs a policy rationale and approved supporting material, not an employee file. Limit access and follow retention requirements.
Separate workplace claims from customer experience
A former employee may post a general attack about management, or they may also have been a customer. Read what the review actually claims. Google’s off-topic and conflict rules depend on context, and a genuine customer experience cannot be dismissed solely because the person once worked there.
Ask whether the content describes service at the specific location or uses the review surface for an employment grievance. State the distinction neutrally in the internal case. Avoid declaring motive beyond what evidence supports.
Report the strongest policy match
Save the review link, screenshot, date, and verified relationship. Compare the content with Google’s conflict-of-interest, off-topic, harassment, or other relevant provisions. Choose the category that best captures the violation rather than submitting several speculative theories.
Use the Business Profile report flow or Reviews Management Tool and track the result. If Google finds no violation, an eligible review may receive a one-time appeal. Supply concise additional context and accept Google’s final decision.
Keep the public response restrained
Do not post employment dates, termination reasons, performance concerns, contract disputes, or private communications. A response such as “This post does not appear to describe a customer experience, and we have reported it through the appropriate process” may be enough when counsel approves.
In some cases, no response is preferable while a sensitive matter is reviewed. The public goal is not to defeat the former employee’s account. It is to avoid compounding the situation while Google and the business’s own processes address it.
Prevent internal review campaigns
Train current employees not to post reviews to improve the rating, counter a critic, or review competitors. Do not organize friends and family to defend the business. Those actions can create additional biased content and unusual patterns.
Recognition programs should never depend on staff generating or soliciting favorable reviews from personal networks. If employees ask genuine customers for feedback as part of their job, give them a neutral, universal request process and no reward tied to star ratings.
Close both processes without mixing them
The Google case tracks the review URL, policy, evidence, report, appeal, and decision. The employment or contract process belongs in its own confidential system. Cross-reference only what policy and access rules allow.
This separation protects people and improves decision quality. It lets the business make a precise platform report without using a public review as a substitute for internal conflict resolution, and it keeps the response team from exposing information it should never publish.
After closure, remove former workers and vendors from Business Profile access if that offboarding step was missed. Review any shared assets, notification routes, and business groups they could reach. Account hygiene will not settle the dispute, but it reduces the chance of a second operational problem.
TakeawayDocument the relationship, report the relevant policy concern, and keep employment facts inside the proper confidential process.
Check the current primary guidance.
Google’s policies and product workflows can change. Use the current source before acting on a specific review.