← All posts business

Google Play 12-Tester Rule: How an Organization Account Skips It

G
Gary Vincent
2026-11-093 min read
Google Play 12-Tester Rule: How an Organization Account Skips It

If you have published a new app on Google Play recently, you have met the rule: before production access, a new app has to run a closed test with at least 12 testers, opted in continuously, for 14 days.

I met it with several apps. It held two of my Android launches for months while the same apps were already live on the App Store. Here is what I learned, and how I got out of it.

The rule, and who it applies to

The 12-testers-for-14-days requirement applies to personal developer accounts. In my experience, an organization account does not have to do it. I converted my developer account from individual to organization, and the next day two apps went straight to production with no closed-testing round at all.

Google changes its policies, so check the current Play Console help before you plan around this. But for me, the account type was the whole story.

Why it matters more than it looks

Recruiting 12 testers is not hard on paper. In practice, you have to find 12 real people, get them to opt in, keep them opted in for 14 continuous days, and have an app good enough that they do not drop out. If people drop out, you can fall below the requirement and have to recruit again. For a solo developer launching more than one app, it is the single biggest non-engineering blocker.

I do not recommend shortcuts like fake or paid testers. They are against the spirit of the rule, and clearing it only buys you a review anyway, not a successful launch.

How I got an organization account

You need a registered business identity. Mine is a business registered under an assumed name, so you do not necessarily need a corporation. I had:

  • A D-U-N-S number
  • A federal tax ID (EIN)
  • A business certificate

The name and address you give Google have to match the D-U-N-S record exactly, including how a DBA is spelled.

The trap nobody warns you about

The "Change account type" option was greyed out, and Play does not tell you why. The reason: your developer website must be verified first, and Play delegates that to Google Search Console. Entering a website URL in Play does nothing by itself.

You have to prove you own the domain in Search Console, using the same Google account as your Play developer account. For me that meant adding a DNS TXT record at my domain registrar. The key detail is that my website is hosted in one place but my DNS lives at my registrar, so the record had to go to the registrar. I also keep that TXT record permanently, because Google rechecks and the domain silently unverifies if it disappears.

That sat for two weeks because nothing showed an error. Do this first.

Two limits to know before you start

  • It is one-way. You cannot go back from organization to individual without a new account and transferring your apps.
  • There is a 72-hour wait. After the change, you cannot submit a new app or update for 72 hours. Do not overlap it with a release window.

What I would tell a new developer

If you can, set up an organization account before your first launch, not after your third. If you cannot, you will have to run the closed test. In that case, start recruiting early, keep testers engaged, and build something worth a tester's time.

Questions about the process? Ask in the comments.

Related reading

Tagged: business · google play · closed testing · app publishing · indie developer · play console

Discussion

No comments yet. Be the first.