Here are common scenarios for troubleshooting Reputation Score.
Who are the businesses that I’m compared against in “Industry Average,” and how do I find out their scores?
To calculate industry benchmarks, our algorithm selects a representative sample of over 1,000 locations in your industry (Reputation.com customers and non-customers). We calculate an average score across all locations in the sample.
We also take the locations with the highest reputation in that sample (typically top 1%) and create an average score of those. That average is the best-in-class benchmark for that industry.
We can’t disclose who the businesses are or what their scores are. If you’re interested in those metrics, consider our Competitive Reporting options.
Is the industry standard / best-in-class specific to region or location?
Your score as a whole *is* industry- and region-specific (national). For example, the scoring algorithm differs between OEM businesses in UK vs. Retail businesses in US.
The industry standard and best-in-class use the same scoring algorithm. However, those scores are not broken down further for location-by-location comparison. If you know that locations in SW Arizona typically do better than NW Arizona, you’ll still compare them both to the national benchmarks for comparison.
I got 20% more reviews this quarter. Why isn’t my score increasing?
- The score reflects a 30 day rolling average (see below), so day-to-day fluxuations won’t be as noticeable.
- Where did those “new” reviews come from? If the positive reviews were all on YP, while meanwhile you got 3 *negative* reviews on Google, the Google reviews are always going to have a bigger impact. Not all review sites are treated equally.
- The higher score that you get, the harder it is to improve. Improvement is measured in much smaller, incremental changes as you near a perfect score.
Suggested Yearly Target Gains For Score Brackets100 – 50%
200 – 30%
300 – 20%
400 – 13%
500 – 8%
600 – 4%
700 – 0%
What does 30-day rolling average mean?
The Reputation Score is updated daily using the average of the last 30 days of data. For example:
- Today is May 1. The score is an average of data accumulated from April 1 – April 30.
- If you go back and look at what your score was on February 1, the score is an average of data accumulated from January 2 – 31.
The platform relies on your data for ALL TIME so that you can make comparisons against any time period, but scores—including individual thermometers—rely on the last 30 days of data.
Why did my score go down?
There can be any number of reasons, but the most common reasons include a recent dip in the number of reviews on Google, a spike in negative reviews on Google, or a drop in response rate. Go to the Reviews tab, and look at the Sentiment Trend for Google.
Also look at the Responded Reviews chart to look for a dip over the last quarter (green). Respond as soon as you can–especially to Google reviews. Negative reviews from Google that are unresponded hurt the most to the review response score. (Let us help you with Managed Response services!)
What do the percentages mean on each thermometer?
The percentages are there for you to quickly identify which thermometers require the most attention. The color goes from red to green as the percentage goes from 0-100%—the redder the thermometer, the more attention it requires.
The percentages are assigned based on our algorithm. Although we don’t provide the algorithm, we show you where each thermometer lands on a scale (with 100% being perfect) so that you have a consistent measurement across all areas. Consider the Star Average thermometer, for example.
Our 30-day star average is at a 4.8! However, if we extrapolate that 5-point scale to 100 (4.8×100/5), we should be at a 96%. What gives?
This metric measures each third-party review’s average star rating, with weights assigned to the popularity of the review site (Google and Facebook) and the position of the review. Even though the rating is high in this case, the positions of the reviews and the lack of star rating from other review sites might be impacting this score.