FlowsBook a callSign inCreate free accountSign up
Business and places data

Competitor ratings and reviews tracking: a watchlist that tells you when a rival slips

Pick the rivals that matter, decide how far a rating must move, and hear about it the week one slips or climbs. How to set up the watchlist and read what it sends.

Part of the guide Location intelligence automation

By the xMap team · · 6 min read

Competitor ratings and reviews tracking means keeping a fixed list of rivals, checking their public star rating and number of reviews on a timetable, and being told only when one of them moves past a line you chose in advance. Done well, it is quiet for weeks and then sends one short message: this rival dropped from 4.6 to 4.2 since last month, that one closed, a new one passed 4.8. Done badly, it is a spreadsheet someone fills in by hand and stops updating in March.

This article is for owners and managers of clinics, cafes, hotels, gyms and salons, and for agency account teams who watch rivals on a client's behalf. It covers who belongs on the list, which movements are worth an alert, a made-up example, the traps, and an AI employee that does the checking. It does not cover reading the words of reviews: the watchlist below works from the rating, the count and whether the place is still open.

Decide who belongs on the list

Most watchlists fail because they are too wide. A dental practice does not compete with every dentist in the city; it competes with the five or six a patient would consider instead. Start with two lists and keep them apart.

  • Named rivals. The handful of businesses your customers mention, compare you with or leave you for. You know their names. They go in a small table: name, address, and why they matter.
  • Everyone of your kind within reach. All the places of your type within a distance of your branch, found fresh each time. This list catches the rival you have not heard of yet, including the one that opened last month.

The first list is for alerts. The second is for a monthly picture of where you stand. Mixing them gives you either too many messages or a blind spot.

Which movements deserve a message

A rating that wobbles by a tenth of a star from one week to the next is noise: a few new reviews in either direction will do it. Set a threshold before you start, and write down why. A common choice is a move of 0.3 in either direction, which catches 4.6 falling to 4.3 but ignores 4.6 to 4.5.

  • A drop of 0.3 or more. Something changed at that business: staff, owner, prices, a bad month. Its customers may be looking around.
  • A rise of 0.3 or more. They fixed something, or they are asking customers for reviews. Find out which.
  • Closed. The place now says it is closed or closed for now. Its regulars need somewhere new to go.
  • A new name or address. Often a new owner or a move, which can change what they offer.

Read the number of reviews next to any rating move. A place with 12 reviews can swing half a star on two bad visits; a place with 900 reviews moving by 0.3 is a real shift. The count also tells you whether a rival is gathering reviews quickly, which usually means they started asking for them.

622Cafes listed
297Rated, of the 312 nearest
4.4Average rating
162Rated 4.5 or more
Cafes within 10 km of the centre of Toronto, xMap's places database, November 2026. The rating figures are of the 312 cafes nearest the centre.

Figures like these set the bar. In that part of Toronto a cafe rated 4.3 sits below the average of its neighbours, so a rival falling to 4.3 has gone from good to ordinary in the eyes of anyone comparing. The same 4.3 can be strong in another category or city, which is why the threshold matters more than the absolute number.

A worked example, made up for illustration

Say a group of three boutique hotels in Cape Town keeps a list of nine rivals that guests mention in their emails. It checks them every Monday and asks to hear about a move of 0.3, a closure or a new name. For six weeks nothing arrives. In week seven one message lands:

RivalBeforeNowReviewsWhat changed
Harbour View Lodge4.64.2214Rating 4.6 to 4.2
The Bay Rooms4.44.488Closed for now

Made-up figures for illustration only.

The sales manager reads it in a minute. Harbour View has a solid number of reviews, so the drop is real; she asks the front desk to watch for guests who mention it. The Bay Rooms closing matters more: its guests have bookings to move, and the group's nearest hotel is two streets away. She calls the agencies that send guests to both. Neither change would have been noticed for weeks by someone checking by hand.

Mistakes to avoid

  • Watching too many places. Fifty rivals and a 0.1 threshold give you a daily message nobody reads by the third week.
  • Judging a rating without its count. A new place on 5.0 from seven reviews tells you almost nothing yet.
  • Checking more often than ratings move. Daily checks of a quiet market mostly confirm that nothing happened. Weekly is enough for most; daily for your own branches or a client you are paid to protect.
  • Comparing across categories. A supermarket on 4.0 and a salon on 4.0 are not in the same position. Compare a rival with its own kind in its own area.
  • Forgetting the first check. The first check only records where everyone stands; there is nothing to compare with yet. Alerts start from the second.

Let an AI employee keep the watchlist

In xMap Flows the watchlist is an AI employee that runs on a timetable and writes to you only when something moved. It is one way of putting location intelligence automation to work on a question you would otherwise answer by hand.

  1. Upload your named rivals as a table in My data (name and address are enough), and bring it in with the My data block after a Schedule set to every Monday.
  2. Add Map business scan with Look for set to Each place itself, so each rival is looked up live on online maps and comes back with its current rating, status and details.
  3. Add What changed with Rating moved by 0.3, Closed, and Name or address ticked. Only the rivals that changed go past it, each with a change line and the values it had before.
  4. Optionally add xMap LLM to write one line per rival on what the change may mean for you, from the rating, the count and the change line.
  5. End with Email or a Slack message to the people who act on it, and deploy.

What lands in the inbox is a short list: the rival's name, its rating before and now, the number of reviews, what changed, and a link to it on the map. Weeks with no change send nothing. For a faster signal on a few places, the When something changes trigger checks up to five places from every 15 minutes to once a day and starts the flow only when a rating falls from your line or more to under it, or a place closes. For the wider picture of everyone of your kind nearby, a monthly flow with Nearby places around each branch gives each rival's rating and review count, and the template How customers rate competitors turns that into a scored list.

Questions

How often should I check competitor ratings?

Weekly suits most local businesses, because ratings move slowly. Check daily only for your own branches or for a client you are paid to protect.

Does it read the text of the reviews?

No. This watchlist works from the star rating, the number of reviews, whether the place is open, and its name and address. It tells you when to go and read the reviews yourself.

What threshold should I use for a rating alert?

A move of 0.3 in either direction is a sensible start: it catches real shifts and ignores the small wobbles that a few new reviews cause. Lower it for your own branches.

Why did the first run send nothing?

The first real run only records where each rival stands, because there is nothing to compare with. Changes are reported from the second run onward, and each change is reported once.

Templates that do this

Read next

More on business and places data · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.