Check your Play Console now: Google’s package-registration deadline of September 30, 2026 has passed. That does not mean every app was missed—Google says it attempts automatic registration—but developers should verify the account and every app’s status, then complete any outstanding steps shown in Console. Identity verification and package-name registration are separate requirements.
Start by checking what Google has already completed
- Review your developer account. Sign in to Play Console and check its verification state. Google says developers who have already completed successful identity verification do not need to repeat it. Notices may appear on the Play Console Home page. Google’s developer verification guidance.
- Check every app’s package status. Open the Android developer verification page in Play Console and inspect each package name. Do not infer that an app is registered because it is published, or assume that Google’s automatic process covered all apps. Google’s package-registration instructions.
- Follow the notice for the specific account or app. The legacy-account verification process has account-specific deadlines, a 60-day start window and a possible 90-day extension for accounts covered by that process. Those provisions should not be assumed to extend the separate package-registration deadline.
Prepare the right identity details for your account type
Google offers Personal and Organization developer accounts. The type affects the details and evidence requested, so confirm it before submitting documents. Google requires an Organization account for financial products and services, health apps, apps approved for VpnService, and government apps. See Google’s identity verification requirements and its Play Console account requirements.
| Preparation item | Personal account | Organization account |
|---|---|---|
| Linked payments profile | Make sure the legal name and address are accurate and current. | Make sure the profile reflects the organization’s real-world identity and matches its official records. |
| Identity evidence | If the payments profile is not already verified, Google may request an official government identity document. Accepted documents vary by country or region. | If the payments profile is not already verified, Google may request an authorized representative’s identity document and official organization proof. |
| Organization records | Not applicable. | Prepare the organization’s D-U-N-S number. Its registration name must match the Dun & Bradstreet profile. |
| Website association | Not listed as a requirement for personal accounts in the Android Developer Console identity guidance. | Verify website ownership through an association with Google Search Console. If another Google account manages the website, its owner may need to approve the association. |
| Mandatory account type for regulated categories | Not suitable for categories that Google requires to use an Organization account. | Required for financial services, health apps, apps approved for VpnService, and government apps. |
For Personal accounts
Check Google’s current country- and region-specific document list before submitting an identity document. Do not assume a particular document is accepted everywhere.
For Organization accounts
Confirm that your organization has the correct D-U-N-S record; a large organization may have more than one. Google says applying for a D-U-N-S number is free, and estimates the process may take up to 28 or 30 days in its guidance. Start early if you need one. Google warns that unsupported documents are the primary reason verification fails. Review the identity requirements and account setup guidance for the current evidence rules.
Recommended Free Tools
#1 Best Overall
Keep contact details and access ready
Make sure the contact email and phone number on the account are operational and accessible to the account owner or a shared team inbox. Google verifies these contact channels with one-time codes. For Android Developer Console organization accounts, make sure the organization website is associated through Google Search Console; arrange approval from the website’s managing account if it differs from the console account. See Google’s verification help.
Resolve package-name registration issues carefully
Google attempts to register existing and new Play app package names automatically according to signing-key install eligibility. The package key associated with more than 50% of known installs has priority for automatic registration. If no key exceeds half of installs, keys with at least 50 installs can be eligible; below that threshold, first-come, first-served applies when no key meets the threshold. These are Google’s registration rules, not a guarantee that every app has already been registered. Check each app’s status in Console and consult Google’s package registration help.
Rank #2
If Console says a package is not registered, follow its instructions. The manual process may allow you to add an eligible public certificate key, sign an APK containing a Google-provided snippet, and upload it. If the signing key is ineligible, you may need to request use of the package name. Do not change package names reflexively: package identity is consequential, and Google advises adopting a new name when there is no legitimate reason to share one.
Keep other Play submission requirements distinct
Identity verification and package registration do not replace ordinary app-submission obligations. Google’s Play requirements also call for accurate app information and metadata, a privacy policy, Data safety details, and working review access—such as demo-account credentials when reviewers need them. Check the current Play Console requirements alongside the account and package notices.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Do not confuse Play Console checks with Android-wide verification
The Play Console identity and package-registration tasks are distinct from Google’s broader Android developer verification rollout. Google’s Android overview describes verification affecting app installations on certified devices across Google Play and other listed app stores, including HONOR App Market, OPPO App Market, Samsung Galaxy Store, Transsion Palm Store, vivo V-Appstore, and Xiaomi GetApps. It describes an exemption for enterprise apps distributed only through an organization’s managed store to managed devices, while recommending registration if those apps could reach unmanaged devices or other channels. See Google’s Android developer verification overview.
Google’s published materials identify Indonesia, Singapore, Thailand, and Brazil as initial markets, but the Android overview contains an inconsistency: it says the first phase starts September 30, 2026 in three named countries and then refers to “these four countries.” A separate Google Play policy preview identifies Brazil as the fourth market and describes the rollout as late 2026. Check Google’s live guidance for the current country list and timeline rather than treating this rollout as the same deadline as Play package registration.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
