Free tool · No sign-up
Google Play opt-in link checker
Paste your closed-testing opt-in link (play.google.com/apps/testing/your.package), your package name, or whatever link you were about to send. You get back what kind of link it is, what Google's opt-in page and store listing answer right now, and in plain English what to do before you send it to 12 testers.
What to do
What this checks, and what it cannot
- The kind of link. The closed-testing opt-in link, the internal-testing link, the Play Store listing and a Google Group link all look alike to a busy developer; only the first one gets a tester into a closed test that counts toward the 12. The checker names which one you pasted and builds the right one from the package name.
- Google's opt-in page. The server asks
play.google.com/apps/testing/<package>without following redirects. Google sends every visitor who is not signed in to its sign-in page first, so from outside, an existing closed test and a misspelled package look the same. The checker reports exactly what Google answered and does not pretend to see the "Become a tester" page; open the link signed in with a tester's account for that. - The store listing.
play.google.com/store/apps/details?id=<package>answers 200 only when the app has a public store page (production or open testing). A 404 is normal for an app that is only in closed testing, and it is why testers who open the store link before opting in see "item not found". - What it cannot know. Whether a particular tester's account is on your list, which countries the track allows, or whether the latest release finished review. Those are the three usual reasons for "app not available for this testing program", and they are checked in Play Console, not from a link.
"This app is not available for this testing program"
| What the tester sees | Usual cause | Fix |
|---|---|---|
| "Not available for this testing program" on the opt-in page | The track's release is not rolled out, or is still in review | Releases tab → roll out; wait for review to finish |
| Same message, release is live | The tester's account is not on an attached email list or Google Group | Add the address they are signed in with; or have them join the group with that account |
| "Item not found" on the Play Store page | Opened the store link before opting in, or the opt-in has not propagated yet | Open the opt-in link first; wait 5–10 minutes |
| "This item isn't available in your country" | Country not selected on the closed track | Countries / regions tab → add the country |
| "Your device isn't compatible" | Minimum SDK, ABI or feature requirement excludes the device | Check the device catalog; lower the requirement |
The long version, with the exact clicks in Play Console, is in where to find your closed-testing opt-in link.
Short answers
What does a working opt-in link look like?
https://play.google.com/apps/testing/ followed by your package name. You copy it in Play Console under Test and release → Testing → Closed testing → your track → Testers tab → "How testers join your test". It only appears once a tester list is attached to the track.
Why does the opt-in link ask my testers to sign in?
Google shows the "Become a tester" page only to a signed-in Google account, because it has to check that the account is on your tester list. The tester must sign in with the same account their phone's Play Store uses. The same rule is why this checker cannot see the page itself.
Why does the Play Store say "item not found" for my closed test?
The store page of an app that is only in closed testing is not public until the visitor has opted in with an account on your tester list. Share the opt-in link, not the store link, and tell testers to tap Become a tester first.
Can I use the internal testing link instead?
No. Internal testing has its own link (play.google.com/apps/internaltest/…) and its testers do not count toward the 12-testers requirement. You need a closed testing track with a rolled-out release, a tester list and its opt-in link.