Why Astrina review counts differ from Google reviews

Why can Astrina review counts differ from Google reviews?

Short answer: the two counts can come from different rules. Google may show one number on the public listing, while Astrina may read the connected data through a separate process, and those two views do not always land on the same total. That gap can look small or strange, but it usually has a specific cause.

Think about a café with 47 Google reviews on the listing and 45 inside Astrina. Two reviews is not a mystery by itself. It may mean one review is filtered, one is tied to a different profile, or the sync has not caught up yet.

The phrase why Astrina review counts differ from Google reviews often points to the same underlying issue: each platform is measuring the review set through its own rules, timing, and source data. That is especially common with multi-location businesses, where one location can be edited, merged, or relisted without the owner noticing until the counts move.

Does Astrina count reviews the same way Google does?

No, not always. Astrina may count the reviews that are available through the connected Google business profile or linked data source, while Google’s public interface can apply visibility rules that are not obvious from the outside. A review can exist in one system’s record and still be hidden, delayed, or excluded in the other.

One simple example: a five-star review written yesterday may appear on the public listing first, then show up in Astrina after the next refresh cycle. Another example: a review may be attached to a location profile, but Google may not display it publicly if it hits a policy filter. Same business. Different count.

Counting logic matters here. If Astrina includes only visible, connected reviews from the active profile, but Google’s dashboard also reflects pending or internally processed items, you can get a gap of 1, 3, or more. That is not a math error. It is a scope difference.

For teams that manage many locations, this is why the comparison should be made against the exact same listing, not a nearby branch or an old profile. If you need one place to check connected data across locations, every client site in one dashboard can help reduce the guesswork.

Could timing or sync delays cause the numbers to look different?

Yes, and timing is one of the most common reasons. Google may update instantly for one view and later for another, while Astrina may refresh on a schedule or after a sync step completes. A count taken at 9:10 a.m. can differ from a count taken at 9:40 a.m. without any real problem in the account.

Here is the ugly little detail: a review can be live, then briefly invisible, then visible again after processing. That sounds messy because it is. If a support agent, owner, and dashboard all check at different times, each one may see a different number.

API delays can make this more obvious. If the connected profile has a short interruption, Astrina may show the last confirmed count until the next successful pull. Google, meanwhile, may already have advanced the visible total. The result is a temporary mismatch, not a permanent one.

There is a practical way to test this. Check the same listing twice, at least 24 hours apart, and record the time next to each number. If the gap disappears, timing was the cause. If it stays the same, keep looking.

Do deleted, filtered, or private reviews affect the totals?

Yes. Reviews can disappear from public view for several reasons, and each reason can affect Astrina and Google differently. A review might be deleted by the author, removed by Google for policy reasons, or hidden from the public page while still showing in some backend records.

A business owner may remember “we had 128 reviews last month,” then notice 126 today. That kind of drop often comes from removal, not from a bug. Google regularly filters suspicious content, duplicate accounts, spam-like bursts, or reviews that break policy. One hidden review is enough to change the count.

Private or non-public reviews are another wrinkle. If Google suppresses a review from the visible listing, Astrina may not count it in the same way the public page does. A review with text, star rating, and date can still be excluded from one view because it no longer meets display rules.

That is also why a count can go down without any action from the business. A reviewer may delete their own comment. Google may later reevaluate the content. The total changes, and nobody on the marketing team touched a thing.

Are location, profile, or listing mismatches causing the difference?

Very often, yes. A business can have more than one Google profile, an old place ID, or a location name that looks right but points to the wrong listing. Astrina can only count what it is connected to, so a mismatch in profile identity can change the review total immediately.

Picture a clinic with two branches and one old listing still floating around after a move. The public Google page may point to the new branch, while the connected profile in Astrina is attached to the old one. The review counts will not match, because they are not reading the same location.

This gets worse with small name edits. A “Suite 200” update, a street-number correction, or a profile category change can split the data if the listing is treated as a different place behind the scenes. One tiny edit. One large headache.

If you manage multiple branches, check the profile ID, the address, and the map pin before assuming Astrina is wrong. One of those three usually explains the difference. Not always, but often enough to save time.

Can duplicated, merged, or changed listings change review counts?

Yes. Google merges, duplicate listings, and profile edits can move reviews around in ways that are hard to spot from the outside. If two listings were once separate and later merged, their review histories may be combined or reassigned. That can make the count jump, fall, or flatten out.

A restaurant example helps. If an owner created a second profile during a renovation, then later merged it back into the original, some reviews may belong to the merged listing while others stay tied to the surviving profile. Astrina may follow the connected active profile, while the public Google listing reflects the post-merge state.

Category changes can also matter. If a business shifts from “store” to “service business,” Google may recalculate how the profile is represented. The review total can remain the same, yet the visible display changes enough to look different to the person checking it.

Those changes are not rare. They happen after relocations, rebrands, and ownership updates. One branch closes. Another opens. Reviews move with the profile history, not with the logo on the door.

How should you compare Astrina and Google review counts correctly?

Start with the exact listing. Then check the time. Then confirm the scope of what each source is counting. That is the simplest way to avoid chasing a difference that only exists because the two numbers were collected from different moments or different profiles.

A useful checklist looks like this:

• Confirm the Google listing name, address, and place ID.
• Check the last refresh or sync time in Astrina.
• Compare the same date, not different days.
• Look for recent merges, edits, or duplicate profiles.
• Review whether deleted or filtered reviews may be excluded.

If you are trying to monitor changes more closely, Astrina’s reporting tools can help you see whether the count moved because of a sync event or because the connected listing changed. If review monitoring is part of a wider workflow, astrina may also fit into a broader reporting setup.

Do not compare a Google mobile view with an Astrina desktop view and call it proof. That is how people waste afternoons. Use one listing, one timestamp, one review scope. Then compare.

What should you do if Astrina and Google still don’t match?

First, recheck the connected profile. Make sure the business name, location, and map listing are the same one you are viewing on Google. If the business has 2 or more branches, verify that the active branch in Astrina matches the public listing exactly. One digit off can send you down the wrong path.

Next, inspect sync status. A paused sync, stale refresh, or temporary API issue can leave Astrina behind the live Google count for a period of time. If the gap appeared after a listing edit, wait for another refresh before treating it as a permanent discrepancy.

If the count still looks wrong after checking the listing and the refresh time, collect the listing details before contacting support. Include the business name, address, profile ID if available, the count shown in Google, the count shown in Astrina, and the time each was checked. That gives support something useful, not just “the numbers do not match.”

If you want to compare settings, pricing, or connected account behavior while you troubleshoot, astrina pricing vs free plan limits can help you see which features are available on each plan. The plan does not fix a mismatched listing, but it can tell you whether a feature you need is included.

And if the mismatch started after a listing edit, ask whether a merge, duplicate, or address change happened in the last 30 days. That one detail often explains the rest.