Response Analytics computes how many reviews you answered, broken down by rating, by location and over time, entirely from your stored review data. Where Google omits a timestamp, the metric is marked unavailable rather than estimated.
Everyone agrees you should reply to reviews. Almost nobody can say what percentage they replied to last month, whether the one-stars were answered faster than the five-stars, or which of their five locations is quietly ignoring customers. The number is knowable. It is just not being counted.
Google shows you reviews, not your coverage of them.
Averaging percentages across locations produces a figure that is simply wrong.
One-star reviews are the ones that matter most and the ones most often skipped.
Tools that estimate response time from missing data are making it up.
What Dropwebs does: Response Analytics measures answered vs unanswered reviews, response rate by rating, monthly activity, and response time when both timestamps exist.
Coverage
Total reviews, how many carry a reply, and the resulting rate. Across multiple locations the figure is computed as total answered over total reviews, not as an average of each location's percentage, because averaging percentages of different-sized sets gives you the wrong answer.
By rating
Response rate is broken out per star rating. It is a common and uncomfortable pattern: five-star reviews get a cheerful reply within a day, one-star reviews sit unanswered for a month. This is the view that surfaces it.
Honesty
Average response time is computed only from reviews where Google supplied both the review time and the reply time. If those are missing, Dropwebs shows the metric as unavailable and explains why. It never fills the gap with an estimate that would look like a fact.
Select a location with synced reviews.
Review response rate and unanswered counts.
Check response time only if timestamps are available.
Open Review Manager for weak spots.
Total over total, so multi-location figures hold up.
Per-rating coverage exposes the reviews you avoid.
Monthly series shows whether you are improving.
Unavailable is stated, not estimated.
Sync reviews before reading charts.
Focus on unanswered count first - that is actionable today.
Use Multi-Location Manager to compare branches.
After publishing replies, sync again to refresh rates.
Response time requires both a review timestamp and a reply timestamp from Google. Missing either, the metric is unavailable.
Figures cover reviews Dropwebs has synced. Sync a location before reading its analytics.
These are your own coverage metrics. They are not Google performance or impression data.
What it does, what it will not do, and where the data comes from.
Google must provide both review and reply timestamps. If either is missing, we show UNAVAILABLE.
Zero means no synced reviews yet - not fake activity.
Because Google did not return a reply timestamp for those reviews. Dropwebs will not estimate a duration it cannot measure, so the metric stays unavailable with an explanation rather than showing a number you might repeat to a client.
Because averaging percentages ignores size. A location with 400 reviews and one with 8 do not carry equal weight. Dropwebs divides total answered by total reviews, which is the correct calculation.
Free plan, no card. Connect Google and this tool has real data to work with in about a minute.
Workspace steps and real screens. This is a how-to, not a second overview of the tool.
DROPWEBS
DROPWEBS