Google Play’s registration rules changed again

Did Google Play change developer account verification or Play Console registration rules

Yes. Google Play changed both the developer account verification flow and the Play Console registration requirements. New and existing developers now face identity verification, verified contact details, and package-name registration steps in Play Console. For personal accounts, Google also added a testing gate before production access.

The part people miss is that these are not one rule. Identity verification answers who owns the account, contact verification proves Google can reach that owner, and package registration identifies which apps belong to that account. Google separates those tasks in its help pages, and it says developers must complete both identity verification and package registration to comply with Android developer verification requirements.

For new Play Console accounts, Google says verified contact details are required, and the contact information must stay operational. For personal accounts, Google collects and verifies a contact email address and phone number plus developer information that can appear on Google Play. For organization accounts, Google collects the organization details and also verifies contact information.

Google also tightened the account-setup side of the process. Its current help says identity verification happens during account creation, and new personal accounts must verify access to a real Android device before they can make an app available on Google Play. That means registration is no longer just a form and a fee, it is a sequence of checks tied to the account owner.

The registration rule that catches teams off guard is package-name registration. Google says developers with a Play Console account must register their Play app package names, and it says this is part of the Android developer verification requirements. Google also says it will try to auto-register eligible apps, but not every app qualifies for auto-registration.

There is also a date that matters. Google’s package-registration page says that, effective September 30, 2026, all Play packages must be registered to meet Android developer verification requirements, and apps that are not registered by then will be removed from Play under the policy cited on that page. That is a hard deadline on the current help page, not a vague future change.

The inconvenient part is that a verified account can still be blocked from production. Google says developers with personal accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Google also says production and some other features stay disabled until those testing requirements are met.

People often repeat the old 20-tester rule, but Google’s current help and community guidance both state the updated requirement is 12 testers for 14 continuous days for the affected personal accounts. Internal testing does not count toward that closed-testing requirement, even though Google says internal testing can include up to 100 testers.

The other part people get wrong is assuming these steps are optional until launch day. Google’s help says failing to keep developer information accurate can affect developer presence and app availability, and it says unresolved verification problems can lead to removal and force re-verification before republishing. That makes account maintenance part of publishing, not a cleanup task after release.

For an individual developer, the practical sequence now looks like this: create the account, verify the identity and contact information, register the app package name, complete the required testing track if the account was created after November 13, 2023, then apply for production access. If any step fails, the next step stays blocked. Google’s own pages describe those steps as linked requirements, not independent choices.

For an organization account, the structure is similar but the identity data is different. Google says organization accounts provide organization name, address, phone number, website, and contact details, and those details are verified before publishing. The important point is that the verification burden moved earlier in the lifecycle, so a team needs correct legal and contact data before it expects a clean Play Console setup.

If you are deciding what to do next, the safest reading is simple: Google Play did change the rules, and the change is not just stricter verification. It is also more explicit registration of the app itself. If you are setting up a new account, read Google’s current help pages before you create the profile, because the account type and creation date now change the path you have to follow.

If you are building a test exchange, keep it on your own property and keep it reciprocal. DevConnect is one place to organize that kind of exchange, and its site describes the platform as free to use. The Google Play side still matters more than the matching tool, because Google’s verification and testing rules decide whether you can reach production. https://devconnectplatform.com

What changed, in plain terms

Google added more identity proof at account creation, not just at launch. It also expanded what has to be verified for new developers, including contact details and, for some account types, device access. On top of that, Play Console now treats package registration as part of Android developer verification, with a published deadline on the current help page.

What did not change

Google did not remove the basic structure of Play Console. You still create an account, configure an app, choose a testing track, and request production access. What changed is the number of gates in front of production, and the fact that account verification, package registration, and testing requirements now connect to each other more tightly.

Why this matters for a real release

A team can spend days preparing a release and still stall because one account detail is unverified or one app package was never registered. Google’s pages make clear that the account owner’s identity, contact status, and app registration all affect availability. That is why the best time to check the rules is before you invite testers or plan a launch window.

FAQ

Is the 12-tester rule for every Google Play account? No. Google says it applies to personal developer accounts created after November 13, 2023. Its help pages also distinguish between personal and organization accounts, so the testing gate is not universal.

Does internal testing count toward the closed-testing requirement? No. Google says internal testing can have up to 100 testers, but it does not count toward the closed-testing requirement for those personal accounts that must satisfy the 12-tester, 14-day rule.

What happens if app registration is missed? Google says packages must be registered to meet Android developer verification requirements, and its package-registration page states a September 30, 2026 deadline. The page also says apps not registered by then will be removed from Play under the cited policy.

Can a verified account still be blocked from publishing? Yes. Google says production and some related features stay disabled until the testing requirements are met for the affected personal accounts. Verification is necessary, but it is not the only gate.

Where should I check first if I am setting up a new app now? Check the current Play Console help pages for account verification, package registration, and personal account testing requirements before creating the release path. Google’s pages say those requirements can affect both account setup and production access.