Yes, new Play Console accounts face extra checks

Are new Play Console accounts now required to complete additional developer identity checks before publishing

Yes. New Play Console accounts must complete developer identity verification before publishing, and some new personal accounts also need device verification before their app can be made available on Google Play. Google documents both checks in Play Console Help.

The part people get wrong is treating every new account the same. Google separates account type and review step. Identity verification applies to new developer accounts, while device verification is called out for new personal accounts. A new organization account follows a different verification path than a new personal account.

For a personal account, Google says you must provide legal name, legal address, contact email, contact phone number, and developer email address. Google also says the legal name and address come from the linked Google Payments profile, and that these identity details must be verified before publishing.

For an organization account, Google requires organization details such as organization name, address, website, contact name, contact email, contact phone number, developer email address, and developer phone number. Google says those organization identity details must be verified before publishing, and the public profile can display some of them on Google Play.

The inconvenient part is that verification is not just a one-time checkbox at signup. Google says developers must keep account information accurate, and if Google cannot verify the developer identity details or contact information, the developer presence and apps may be removed until the information is re-verified. That means a launch can stall even after the app is built and uploaded.

The other part people mix up is testing requirements. The extra identity checks are separate from Google Play’s closed testing rules for new personal accounts. Google says new personal accounts created after 13 November 2023 need 12 opted-in closed testers for 14 continuous days before production access, while internal testing does not count toward that requirement.

That means a developer can finish identity verification and still not be ready to publish. The account can be valid, the app can be ready, and production access can still wait on testing requirements. Buying testers or installs is not a legitimate shortcut, because Google says inauthentic engagement can trigger enforcement and account suspension.

If you are setting up a new account now, the practical order is simple: create the account, complete identity verification, complete any required device verification if you have a new personal account, then satisfy the closed testing requirement before asking for production access. Google says developers can complete verification in Play Console before their deadline, and the Help Center task list shows where these steps live.

The safest way to read Google’s current rule set is this: new Play Console accounts do face additional checks before publishing, but the exact checks depend on whether the account is personal or organizational. Identity verification is part of account setup, and newer personal accounts can also face device verification plus the closed testing gate.

If you are planning testers, use real people who actually opt in and stay opted in. If you are organizing that work through DevConnect, the platform is free to use, and the exchange is simple: you test someone else’s app, they test yours. That avoids the policy risk that comes with paid tester services.

A good mental model is that Google Play now checks three different things for many new accounts: who you are, whether you can access a real device, and whether your app has passed the closed test requirement. Missing any one of those can stop publishing, even when the app itself is finished.

For the exact steps and current wording, start with Google’s Play Console Help articles on developer identity, device verification, publishing status, and new account requirements. Those pages are the current source of truth, and they are the ones Google updates when the onboarding flow changes.

FAQ

Do all new Play Console accounts need device verification

No. Google specifically says new personal accounts must verify access to a real Android mobile device before the app can be made available on Google Play. The Help Center pages do not describe that step as applying to every account type in the same way.

Is identity verification the same thing as closed testing

No. Identity verification is about the developer account and contact details. Closed testing is a separate production-access requirement for eligible personal accounts, and Google says internal testing does not count toward it.

Can I skip verification if my app is already uploaded

No. Google says developer identity details and contact information must be verified, and if Google cannot verify them, your developer presence and apps may be removed until you re-verify. Uploading the app does not replace account verification.

What should I do before I invite testers

Verify the account first, then check whether your account type needs device verification or the closed testing gate. After that, invite real testers who can opt in and stay opted in for the full required period.

Where does Google explain the current rules

Google explains them in Play Console Help, including the pages for required account information, developer identity verification, device verification, and publishing status. Those pages are the current references for onboarding and publishing rules.