Google's requirements and Console wording change periodically. Where this article and your own Play Console disagree, the Play Console is authoritative.
You recruit 12 testers, several abroad, and by day three two report that Google Play says the app is not available in their country. Nothing looks broken, yet those testers cannot install anything.
Questions about Google Play closed testing different countries tend to share one root cause: country targeting, not a rule about where testers may live. Google does not restrict testers by location, but it does restrict releases by the country registered to a tester's Google Play account — and those are different things.
This guide covers that distinction, how closed-testing country availability is configured, what to check when an international tester is blocked, and why internal testing's country exception does not fix a closed-test problem.
Can testers from different countries join Google Play closed testing?
Yes. Google publishes no requirement that testers share your country, and no rule limiting how many countries they span. What it does publish is a targeting mechanism: you can control release access by country and region across production, open testing, and closed testing.
So the working rule is: testers can be anywhere, but your closed-testing release must be available in the country their Google Play account is registered to. One condition is about people; the other is about configuration.
Two cautions. Google never states "closed-test testers may be in different countries" in those words — the conclusion follows from a targeting system that names closed testing, plus the absence of any same-country rule. And Google's advice to recruit a diverse group of testers is explained in terms of user groups and device types, not geography.
Google Play account country vs. physical location
Google is explicit: country and region targeting is based on where the user's Google Play account is registered, not their physical location. That single sentence explains most "not available" reports.
Take a tester physically in Bangladesh whose Google Play account is registered in the United Kingdom. If your closed test targets Bangladesh only, that tester's account country decides what they see, and the app may not appear for them — even though they are standing in a targeted country.
The reverse happens too: a tester travelling abroad with an account registered in a targeted country can usually still access the release. Physical position is not the variable you configure against.
You therefore cannot infer a tester's eligible country from where they live. Ask each tester which country their Google Play account is registered in, and treat that answer as the compatibility check. Google publishes no procedure for developers to verify or change a user's account country, so do not promise testers a workaround; the practical fixes are to target their account country or to recruit testers whose accounts match your target markets.
How Google Play closed testing handles different countries
Production availability sets the default
Production country and region targeting defines where your released app is distributed. When you target a country in production, Google states that all current and future production releases include it.
Testing tracks sync with production by default
Testing track availability syncs with production by default. Any change to country targeting in production or pre-registration automatically applies to your testing releases. This is why a closed test can silently inherit a narrow country list you set months ago for a limited launch.
Unsync and its documented prerequisites
You can manage testing availability independently by clicking Unsync. Google documents prerequisites for customising a testing track's country targeting — either no app bundle is uploaded to production, or one is and at least one country is available there. Google also notes these options may be unavailable if your account lacks permission to manage releases, which explains why some developers never see the control.
After unsyncing, edit that track's country list directly. You can sync again when the track has no active releases, when production targets at least one country, or when pre-registration has started and targets at least one country excluding "Rest of World".
A practical example: production is live in the UK and Germany only, so your closed track inherits those two countries. Testers in India and the US cannot install until you unsync the track and add their account countries.
How to check country availability in Play Console
- Sign in to Play Console and select the app.
- Open Test and release > Testing > Closed testing.
- Click Manage track next to the track you are using.
- Open the Countries / regions tab.
- Review the selected countries and regions against your testers' account countries.
- Check whether the track is synced with production, since a synced track mirrors production changes.
- If independent targeting is required and the prerequisites are met, use Unsync, then Edit countries / regions to add or remove countries.
- Confirm your selection and save.
Verify the country list immediately before you send the opt-in link. Adding a country is a configuration change, and Google notes that additional changes can take several hours to become available.
Why an international tester may see "This item isn't available in your country"
The message is a symptom, not a diagnosis; several unrelated problems produce it. Check these in order.
- The tester's account country is not in the track's list. Compare the registered country with the Countries / regions tab — the most common cause for international testers.
- The tester is not on the list or in the group. With Google Groups, membership must be completed before opting in.
- The tester never completed the opt-in. Eligibility is not participation.
- The tester is signed into a different Google Account. The account that opts in must be used on the device.
- The release is not published to that track. The opt-in link only appears when the app's status is Published.
- Changes are still propagating. A first test link can take several hours to appear.
- The device is not compatible. Country targeting does not override compatibility; check the Device catalog under Monitor and improve > Reach and devices.
- The tester opted into a different track. A user on the internal test must opt out before receiving your closed test.
Work through the list rather than assuming a country block. Device-specific problems are covered in real device testing across different devices; tester-count issues are covered in why testers are not being counted.
Does internal testing allow testers from any country?
Yes, and this is the one place Google documents a country exception. Country and region targeting does not apply to the internal testing track. You can add users from any location, and an internal tester located where your production, open, or closed test is unavailable will still receive the internal test app.
That exception is scoped to internal testing only. Internal testing is a separate track for early checks and QA, and Google recommends it as a starting point before closed testing. Crucially, internal participation does not satisfy the closed-testing requirement: testers must be opted in to your closed test, and a user on the internal test is not eligible for the closed test until they opt out.
So internal testing is a sensible way to get early feedback from colleagues anywhere. It is not a way around country targeting for your 12 closed testers.
Can I recruit 12 testers from different countries?
Yes, subject to the same rules as any closed test. For personal developer accounts created after November 13, 2023, Google requires at least 12 testers opted in continuously for at least 14 days before production access can be requested. Google publishes no geographic distribution rule — neither same-country nor different-countries.
What you must control is eligibility: confirm the track's country list includes each tester's Google Play account country, that the tester is on the list or group, and that the release is published. Then verify they actually opted in.
Two points to keep straight: an email address on a list is not an opted-in tester, and a tester who opts out and rejoins must run 14 consecutive days again. The 12-testers and 14-day requirement guide covers the details.
Country diversity is not a documented advantage in the production access review. It can still surface locale, network, and device issues — recruit from the markets you intend to serve, as described in how to get 12 testers for closed testing.
Practical example: setting up an international closed test
Illustrative only — not a Google-prescribed country distribution. Suppose you have 12 testers: 4 in Bangladesh, 3 in India, 2 in the United States, and 3 elsewhere.
- List the countries involved: Bangladesh, India, the United States, and the remaining testers' account countries.
- Open the closed track's Countries / regions tab and compare it with that list.
- Check sync status. If the track mirrors a two-country production release, unsync (if prerequisites are met) or widen production targeting.
- Confirm the tester list or group includes all 12 addresses.
- Publish the release to that track and confirm it is live.
- Share the opt-in link only after it appears.
- Tell each tester which Google Account to use and ask them to confirm its registered country.
- Verify each opt-in, then monitor continuity and genuine feedback for 14 days.
International tester setup checklist
- Correct app and closed track selected.
- Intended countries reviewed against each tester's Google Play account country.
- Sync status checked — unsynced deliberately if independent targeting is needed.
- Tester list or Google Group configured; group memberships completed.
- Tester Google Accounts confirmed as the ones used on devices.
- Release published and the opt-in link visible.
- Each tester has completed opt-in.
- App installs from Google Play for every tester.
- Device compatibility checked in the Device catalog where a tester is blocked.
- Feedback channel shared and monitored.
- Continuous opt-in tracked for the qualifying window.
The 14-day closed testing checklist tracks the daily side of this once testing begins.
Frequently asked questions
Can I use testers from different countries for Google Play closed testing?
Yes. Google publishes no rule restricting testers by country. Your release must be available in the country each tester's Google Play account is registered to.
Does a tester's physical location determine availability?
No. Google states that country and region targeting is based on where the user's Google Play account is registered, not their physical location.
Is availability based on the tester's Google Play account country?
Yes. That account country is what the targeting setting is matched against.
Can I run a closed test in a different country from production?
You can customise testing track targeting, but it syncs with production by default. Independent targeting depends on Google's documented prerequisites and your release permissions.
Why does my tester see "This item isn't available in your country"?
Common causes are an account country outside the track's list, missing group membership or list entry, an unfinished opt-in, the wrong Google Account, an unpublished release, propagation delay, device incompatibility, or an internal-test conflict.
Can internal testing testers join from any country?
Yes. Country targeting does not apply to the internal testing track, and internal testers receive the build even where other versions are unavailable.
Does internal testing count toward the 12 testers / 14 days requirement?
No. The requirement concerns closed-test opt-ins. Internal test participation is separate and does not substitute for it.
Do all 12 testers need to be from the same country?
No. Google publishes no same-country rule.
Can all 12 testers come from different countries?
Yes, provided each is eligible for the track and opts in. Google publishes no requirement for geographic spread either.
Does adding a country automatically make every device eligible?
No. Country targeting and device compatibility are separate. Manifest declarations and console exclusions determine targeted devices.
How long can testing availability changes take to appear?
Google notes a first published test link can take several hours, and additional changes can also take several hours.
Does completing 14 days guarantee production access?
No. Meeting the requirement makes you eligible to apply; Google reviews each application.
Official Google resources
Policy statements here come from these pages. Where a page disagrees, the official page wins.
- Target app releases to specific countries and regions — account country rule, testing sync, Unsync prerequisites, internal testing exception
- Set up an open, closed, or internal test — tracks, tester access, opt-in links, internal test country notes
- App testing requirements for new personal developer accounts — 12 testers, 14 days, continuous opt-in
- Device compatibility and the device catalog — targeted devices, manifest declarations, console exclusions
Conclusion: check targeting, then check opt-ins
International testers are workable in almost every case. The failure mode is nearly always configuration: a track synced to a narrow production list, a tester's account country assumed rather than checked, or an opt-in that never happened.
Review the Countries / regions tab, confirm sync or unsync deliberately, verify each tester's Google Play account country, and make sure every person has genuinely opted in. For eligible accounts, the requirement that still decides your application is 12 testers continuously opted in for 14 days.
Need help organising an international closed test with documented opt-ins? Explore TestersHQ.
