Online Reputation Monitoring: How to Track Mentions and Reviews
Build a practical system for tracking brand mentions and customer reviews, routing alerts, responding constructively, and spotting recurring issues.
Online reputation monitoring is the repeatable work of finding public discussion about your business, products, and people, then deciding what needs a response or operational follow-up. Track customer reviews separately from broader mentions across social platforms, news sites, blogs, and forums: the sources and access available to each monitoring method differ.
A useful system has four parts: a carefully scoped list of search terms, sources that matter to your audience, alerts routed to a responsible person, and a process for replying or fixing recurring problems. Start with the setup below, then refine it as you see irrelevant results and missed conversations.
1. Decide what to monitor
Write down the terms and sources that would reveal a meaningful customer conversation. Begin with:
- Your business name, product names, and common misspellings.
- Names of executives or public spokespeople when their public comments are relevant to your organization.
- Campaign names, distinctive product phrases, and branded hashtags.
- Terms that distinguish your brand from unrelated words or organizations.
- Competitor or category terms only when you need to understand comparisons or broader category discussion.
Give each alert a clear purpose. For example, one alert can find reviews of a location, while another finds public posts mentioning a product name. Add exclusions for unrelated meanings, and use source, country, and language filters when the service supports them. Review sample matches before you rely on the alert; a large number of irrelevant results makes important mentions easier to miss.
2. Cover review sites and open-web conversation
Reviews and social listening answer different questions. Review pages show ratings and detailed feedback submitted on particular services. Listening tools may surface public posts, comments, news, blogs, and forums, depending on the sources they can access. Do not assume one alert covers every platform or every conversation.
| Source type | What to monitor | Coverage check |
|---|---|---|
| Business review profiles | New reviews, updated reviews, ratings, and customer concerns. | Confirm the profile, locations, notification path, and who can access it. |
| Industry review sites | Reviews on sites customers use to compare providers in your category. | Check that the monitoring service supports the exact site and region. |
| Owned social accounts | Comments, mentions, and messages on accounts your team manages. | Check account connection requirements and whether the tool sees comments or only other activity. |
| Public web sources | News, blogs, forums, and public social conversations about the brand or product. | Verify source, country, language, delay, and any access restrictions. |
Some services support monitoring selected social pages and review websites, but that is not the same as universal access to every platform. Verify exact sources, connected-account requirements, countries, languages, and notification options before choosing a service. Distinguish analytics available through accounts you connect from public listening across the web.
3. Set up alerts and review the results
- Create separate alerts for separate jobs. Keep review alerts distinct from broad brand mentions so each can have useful filters and an owner.
- Add variants and exclusions. Include misspellings and distinctive phrases. Exclude common unrelated uses that repeatedly appear in sample results.
- Choose relevant source and geography filters. Add language filters where appropriate, but check that they do not hide posts from customers who use another language.
- Inspect sample matches. Mark results as relevant or irrelevant and adjust terms, exclusions, and filters.
- Confirm alert delivery. Check whether alerts arrive in the service, by email, or through another supported integration, and whether delivery depends on your plan.
- Revisit the configuration. Add new product or campaign terms when they become relevant, and remove alerts that no longer support a decision.
For Google Business Profile, Google documents notifications for new and updated reviews through a configured Google Cloud Pub/Sub topic. This is an API configuration, not evidence that every business has the same one-click notification setting. Consult the [Google Business Profile Notifications API reference](https://developers.google.com/my-business/reference/rest/v4/Notifications) and verify current availability and setup in the current documentation before building an integration.
4. Assign ownership and decide what happens next
An alert without an owner is easy to overlook. Assign a primary reviewer and a backup, and define how the team handles issues that need a specialist. A simple routing plan can look like this:
| Alert type | First owner | Possible follow-up |
|---|---|---|
| Routine review or product question | Customer support or location manager | Answer the question and record any useful product feedback. |
| Repeated service complaint | Support lead or operations owner | Group similar reports and send the underlying issue to the responsible team. |
| Safety, legal, or sensitive allegation | Named escalation contact | Follow the organization’s established escalation process before replying publicly. |
| Suspected policy-violating review | Profile manager | Use the platform’s reporting process and address the customer issue where appropriate. |
Daily or weekly review may suit ordinary operations; a significant incident may call for more frequent checks. Treat that as a workflow decision, not a universal response-time benchmark. Agree on internal expectations for acknowledgement and escalation based on your staffing and the issue’s urgency.
5. Respond to reviews and mentions constructively
Keep replies professional, relevant, and short. Acknowledge the specific concern, avoid sharing private customer information, and offer a suitable next step when one is available. Take account-specific details to a private channel when that is appropriate, while keeping the public reply useful to other readers.
Do not treat criticism as removable by default. Google says only reviews that violate its policies are eligible for removal; disagreement or dislike alone is not enough, and review evaluation typically takes several days. Report suspected violations through the platform’s process, and continue to address the underlying customer issue. See [Google’s review reply tips](https://support.google.com/business/answer/3474122?hl=en-en) and [review reporting guidance](https://support.google.com/business/answer/4596773?co=GENIE.P&hl=en).
Keep review requests genuine. Google requires reviews to reflect actual experiences and prohibits incentives in exchange for posting, changing, or removing a review. Do not buy reviews, offer a discount for a desired rating, or pressure a customer to delete criticism. See [Google’s review content policy](https://support.google.com/business/answer/7400114?hl=en).
6. Measure whether monitoring leads to action
Track a small set of operational measures that help improve the process:
- Time from an alert arriving to someone reviewing it.
- Unresolved complaints and their age.
- Recurring issue categories and which team owns each one.
- Rating trends for the review profiles you monitor.
- The share of alerts judged relevant, which can reveal noisy search terms.
- Follow-ups completed after feedback is routed to a product or operations team.
These are suggested internal measures, not published benchmarks. Mention volume is not a representative measure of all customers’ views: the people who post publicly may not reflect everyone who uses your product or service. Use the signals to identify conversations and operational themes, not to claim a complete picture of customer opinion.
7. Choose a monitoring service carefully
Compare tools against your actual monitoring list and expected workload. Check:
- Which review sites, social sources, public web sources, countries, and languages are covered.
- Whether the product monitors public conversations, connected accounts, or both.
- Alert delay, filtering and exclusions, and notification delivery routes.
- Team assignment, reporting, exports, and any account or plan requirements.
- Total cost at the volume and number of sources you expect to monitor.
Mention’s help documentation describes brand and competitor alerts, source filters, notifications, reporting, and monitoring for specified social pages and review websites. These are vendor-described capabilities, not an independent evaluation or a claim of coverage for every platform. Verify current source coverage, account requirements, pricing, and integrations before selecting it: [Mention overview](https://en.support.mention.com/en/articles/8695163-mention-social-listening-analytics-explained) and [alert guidance](https://support.mention.com/en/articles/13350774-mention-social-listening-analytics-explained).
If an agency or other third party manages Google Business Profiles, Google requires reports to distinguish Google data from other platforms’ data and requires explicit approval before the third party responds to reviews for a client. Review [Google’s third-party policy](https://support.google.com/business/answer/7353941?hl=en-en) before defining that workflow.
8. Troubleshoot common monitoring problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Too many irrelevant mentions | A brand or product term has unrelated meanings, or the alert is too broad. | Add phrase or source filters, exclude recurring unrelated terms, and inspect fresh samples. |
| Important mentions are missing | The source is unsupported, a term variant is absent, or a filter is too restrictive. | Verify source coverage and account requirements; add relevant spelling variants; test country and language settings. |
| Review notifications do not arrive | The profile or notification route is not configured, or the workflow depends on an API setup. | Check account access and current platform settings. For a Pub/Sub integration, verify the Google Cloud topic and subscription configuration against current documentation. |
| Alerts arrive but nobody responds | No primary owner, backup, or escalation path has been assigned. | Name an owner and backup, route sensitive issues to a defined contact, and check unresolved alerts on a schedule. |
| Sentiment or volume looks misleading | Mentions are being treated as a representative customer survey or automated classification is being accepted without review. | Read the underlying conversations, label uncertainty, and use volume as a signal for follow-up rather than a measure of all customer opinion. |
| A negative review remains visible after reporting | It may not violate policy, or review evaluation is still in progress. | Check the policy criteria, allow time for the platform’s evaluation, and respond to the customer concern where appropriate. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. A screenshot can help document a public review page or mention for an internal follow-up record; it does not replace monitoring alerts or review-policy workflows. Make a capture with one GET request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for free ScreenshotNeo access.
FAQ
How can I get alerts for new Google reviews?
Check the notification options available for your Business Profile and assign someone to monitor them. Google also documents an API notification route using a configured Cloud Pub/Sub topic; verify the current setup requirements before implementing it.
How often should I check mentions?
Choose a cadence your team can reliably maintain. Daily or weekly checks can fit routine operations, while a major incident may require more frequent review.
Should I reply to every negative review?
Use judgment based on the issue and available information. A concise, professional reply can acknowledge a concern and explain a next step. Avoid disclosing private details or arguing publicly.
Can I ask customers to leave a review?
You can request genuine feedback, but do not offer incentives for posting, changing, or removing reviews, and do not pressure customers to change a rating.
Does a monitoring tool see every post about my company?
No tool should be assumed to cover every platform or conversation. Confirm its exact source access, account requirements, geography, language, and alert delay.


