Got a Review for the Wrong App? How to Report and Reply to Misfires

A review that's obviously about a different app, or about your phone, the App Store itself, or a package that never showed up, is one of the few review types you have a genuine shot at getting removed. The reason is simple: it's *off-topic*, not just unflattering. Both stores draw a hard line there. A review is supposed to describe experience with your app, and when it plainly doesn't, you have an objective policy violation to point at rather than a vibe. That's a much stronger case than "this one-star feels unfair," and it's the good news.

The bad news is the usual bad news: only the store can pull a review, removal is never instant, and a busy triage queue will happily leave an obvious misfire on your listing for weeks. So the winning move is two-track. Report it through the right channel, and reply in public, because the reply protects you with the next reader while the report grinds through. Below: how to spot the flavors of wrong-app review, how to report each on Google Play and Apple, and how to answer without sounding annoyed at a stranger who wandered into the wrong store.

"Wrong app" covers more ground than a simple case of mistaken identity. The common thread is that the review doesn't describe your current app at all, which is precisely the language the store policies use. Here are the shapes it takes.

Honestly? Better odds than most, worse than you'd like. Both stores publish content policies stating that reviews should be about the app, and Google Play's policy is explicit that off-topic content, spam, and material unrelated to the app can be removed. Because "this review names a different app" or "this is a complaint about a physical delivery" is objectively checkable, flagging off-topic content hands the moderation system something concrete to act on. Compare that to a fake-but-plausible one-star, which is a judgment call the store usually declines to make. If you've ever tried to get a garden-variety unfair review pulled and hit a wall, this is a different, stronger case.

That said, temper the optimism. "Removable in principle" is not "removed by Friday." For the full mechanics of what the stores will and won't take down, [how to remove fake app reviews](/blog/how-to-remove-fake-app-reviews) and [how app review moderation actually works](/blog/app-review-moderation) walk through the real odds on each side.

Each store has its own path, and the framing matters. Report the specific review, name the reason closest to "off-topic" or "spam," and keep it factual. Here's the route on each side.

The report might land in a month. Your reply lands the moment you post it, read by every future shopper who scrolls to that review before deciding to install. That's who you're writing for, not the confused reviewer. A calm, specific redirect quietly tells the next reader "this one-star isn't actually about us," which does more for your conversion than a takedown you can't schedule. The trick is to name the mismatch without a trace of snark: if it's genuine confusion, help them find the right place; if it's a platform gripe, point them at the channel that can fix it. The wider [playbook for negative reviews](/blog/how-to-respond-to-negative-app-reviews) applies here too, aimed at redirection instead of remediation.

That reply is under 350 characters, so it clears Google Play's hard cap with room left. Apple publishes no official limit; community testing suggests a few thousand characters, but keeping replies tight travels safely across both stores (more on those differences in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies)). It never scolds the reviewer for landing in the wrong place. To a future reader, it reads as a company that's paying attention rather than one that's rattled.

Platform and device complaints get the same treatment. You won't fix iOS, but you can separate your app from the thing the reviewer is actually mad at and hand them a real next step.

One stray review is a two-minute fix. The problem is volume: they arrive scattered across two stores, at odd hours, in whatever language the reviewer speaks, and a wrong-app one-star in Portuguese hurts your average exactly like an English one you never saw. This is the boring, repetitive edge of review management, which is exactly the kind of work worth handing to a system.

That's the case for [ReplyArgus](/features). It pulls your App Store and Google Play reviews into one inbox, alerts you in Slack, Discord, Telegram, or email the second new ones land, and drafts a reply for each, grounded in your past approved replies and a knowledge base built from your own listing, so the tone is yours and a redirect never invents a policy you don't have. It translates both directions, so a German review gets a German answer you still read in English. Everything stays approve-by-default. Recent reviews carry more weight than old ones ([here's why that matters](/blog/recent-reviews-weigh-more)), so answering fast and keeping genuine reviews flowing is what quietly buries a misfire while you wait on the report.

A wrong-app review is one of the rare cases where reporting is genuinely worth your time, because off-topic content is removable in a way most unflattering reviews aren't. Flag it in the right place, keep a note of what you sent, and then do the thing that actually protects you today: reply in public, name the mismatch kindly, and let a future reader see a company that's paying attention. [Start free with ReplyArgus](/signup), no card required, and Argus watches both stores, surfaces every misfire the moment it lands, and drafts a calm redirect in the reviewer's own language — so the stray reviews get handled while you get on with building the app they meant to review.