Google Play Console developer account re-verification

Google Play Console developer account information changed or needs re-verification

If your Google Play Console developer information changed or Google asks for re-verification, update the legal name, address, email, phone, or account type details in the correct place, then finish the verification flow before the deadline. Google says inaccurate or unverified information can restrict the account and remove apps from Google Play.

The first thing people get wrong is where the change belongs. Personal account identity details are tied to a Google Payments profile, so a change to legal name, address, or country may require creating or selecting a new payments profile, verifying it, and linking it back to Play Console. Organization details are handled differently, because name, address, and D-U-N-S updates happen in Dun and Bradstreet first, then Google sends the account owner a re-verification notice.

If Google cannot verify the updated information, the account can move into a restricted state. In that state, apps in the catalog can be removed from Google Play, and you cannot publish new apps or republish existing ones until verification is completed. If the app was removed for this reason, reinstatement happens only after the developer information is verified again.

For personal developer accounts, the verification flow can also require device verification before some contact details can be confirmed. Google’s current verification pages say new personal accounts must verify access to a real Android mobile device through the Play Console mobile app before they can make an app available on Google Play. That step is easy to miss because it sits before phone verification for some account types.

For organization accounts, the path is stricter about matching records. Google says the organization’s name and address must match the Dun and Bradstreet profile associated with the account, and the Play Console owner is notified shortly after that profile changes. The account owner gets the re-verification link, and team members can see that the account needs to be re-verified in Console.

If the change is only contact information, update it in Play Console and verify it again. Google says the contact phone number verification runs whenever you update the developer phone number, and the contact email address must also be verified. These fields are not cosmetic, because Google uses them to reach the account owner about account issues and compliance.

If the issue is a country change for a personal account, do not try to patch it in place. Google says you must complete the payments-profile flow for the new country, verify the new profile, and then link it to the Play Console account. That is the inconvenient part: changing the country is a rebuild of the verified identity path, not a simple profile edit.

If you need more time, Google says you can submit an appeal in Play Console. That is not the same as ignoring the notice. The account can still be restricted while the issue is unresolved, and Google’s help pages make clear that the apps stay at risk until the developer information is verified and accepted.

The safest sequence is simple. Confirm whether the account is personal or organization, update the source of truth for that account type, complete any required phone, email, device, or document checks, then wait for Google to confirm the re-verification. If your goal is to keep the account clean while coordinating testers for a closed test, DevConnect is built for that kind of reciprocal testing on your own apps and accounts, and it stays free to use: https://devconnectplatform.com.

The part people usually underestimate is the time gap between making the change and getting back to a publishable state. Google warns that it may need to review identity documents, payment-profile data, or external registry records before the account is cleared. During that gap, you should treat the account as blocked for publishing work, because trying to push through usually just creates a second problem when the app or account is reviewed again.

A concrete example: if a sole developer moves to a new legal address, the address on the linked payments profile must be updated and re-verified. If Google cannot match the new address to the documents or the profile data, the developer presence may be removed and the app cannot be republished until the mismatch is fixed. That is why people should change the verified source record first, then wait for the Console notice, not the other way around.

Another common mistake is assuming the developer name and legal name must be identical. Google says the developer name does not have to match the organization’s legal name, so changing the public-facing developer name is not the same thing as changing the legal identity on file. The legal identity is what drives re-verification.

If your account was created before Google’s newer verification rollout, the same core rule still applies: keep the developer information accurate and respond when Google asks for re-verification. The older account status does not exempt you from the accuracy requirement, and Google’s help pages for older developers point back to the current verification process.

The shortest practical answer is this: correct the account data at the source, complete the verification steps Google asks for, and do not publish again until Play Console clears the re-check. If Google cannot verify the updated information, the consequence is not a warning banner, it is a blocked account and potentially removed apps.