Yes, Google Play added registration and verification steps

Has Google Play added new app registration or developer verification requirements for Play Console accounts

Yes. Google Play now requires developers to complete Play Console requirements, register apps and package names, and verify developer identity information before publishing. New personal accounts also face extra device verification and app testing steps before public release.

The part people get wrong is treating these as one checkbox. They are separate requirements. One set covers the developer account, another covers the app, and a third can apply to new personal accounts. If any one of them is missing, the app can be blocked from distribution or removed from Google Play.

For new developer accounts, Google asks for verified contact details and verified identity information during setup. Personal accounts must provide the legal name, legal address, contact email, contact phone number, and developer email address. Organization accounts must provide more fields, including organization details and, in many cases, a D-U-N-S number.

Google also requires some new personal accounts to verify access to a real Android device through the Play Console mobile app before they can make an app available on Google Play. Google says this is part of the onboarding flow for new personal accounts, and it applies before public release, not after the app is already live.

Google Play has also added app registration requirements. The Play Console Requirements article says developers must register their Play apps in Play Console to meet Android developer verification requirements, and it warns that unregistered apps may be removed from Google Play. Another help page says developers must complete two tasks to comply with Android developer verification requirements, including registering package names.

The inconvenient part is that this is not a one-time form with no follow-up. Google says verified developer information must stay accurate, and if it changes, the account owner has to update it or risk restriction and app removal. That matters for legal names, addresses, phone numbers, and other account data that can drift over time.

For new personal accounts, Google also requires app testing before public availability. The testing page says personal developer accounts created after November 13, 2023 must test their apps before those apps are eligible for distribution, and the app-testing article explains the minimum testing requirements. Internal testing does not count toward the closed-testing requirement.

People also get tripped up by the closed-test requirement itself. For personal accounts created after November 13, 2023, Google currently requires 12 opted-in testers for 14 continuous days before production access can be requested. Buying testers or installs is not a valid shortcut, because Google says inauthentic engagement can lead to enforcement.

That is the practical answer: yes, Google added more registration and verification steps, and the requirements are broader than many developers expect. The safe path is to complete account verification, register every app that needs to stay distributed, keep profile data current, and satisfy the testing rules for the account type you are using. If you want a separate workflow for finding real testers without violating policy, use an exchange model on your own property, not paid shortcuts or automation on other platforms. For that, DevConnect describes a free testing exchange at https://devconnectplatform.com.

What changed for Play Console accounts

Google expanded the onboarding and verification flow. New accounts now need verified contact details, verified developer identity information, and in some cases device verification. For many developers, app registration and package-name registration are now part of the same compliance path.

What should a developer check first

Check the Play Console Home page for any warnings about account verification, app registration, or package-name registration. Then confirm that the account owner has completed identity verification, the app is registered, and the app has passed the testing requirements that apply to that account type.

What happens if a developer ignores the new requirements

Google says apps can be removed from Google Play if Play Console requirements are not met, and account information that is not kept current can lead to restriction. For a release workflow, that means a missing verification step can stop publication even when the APK or bundle is ready.

Why do developers confuse registration with verification

The wording overlaps in Google’s help pages, so it is easy to miss that identity verification, app registration, device verification, and testing are separate gates. A developer can finish one gate and still fail another, which is why checking only the account profile is not enough.