What is changing
Android is adding developer verification and package registration as an ecosystem-level security measure. For Google Play developers, many identity steps may already be complete, but app registration status still needs attention.
Two core steps
The current Android guidance separates identity verification from app/package registration. Organizations may need a D‑U‑N‑S number and website verification, while app ownership can require proof tied to the signing key.
What Play developers should do
Open the relevant verification area in Play Console, confirm account identity status and check whether any package names remain unregistered. Do not assume every historical or externally distributed package is covered automatically.
Why this matters now
Regional enforcement starts in select markets in September 2026. Developers with multiple apps, old packages or outside-Play distribution should create a package inventory now instead of waiting for a blocking warning.
Avoid risky shortcuts
Verification should use the real developer or organization identity and the correct signing ownership. Using unrelated business records creates long-term account risk.
Official sources
Policies and platform requirements can change. Check the linked official documentation for the latest wording before acting on a time-sensitive case.
Need case-specific help?
If your situation includes a specific warning, rejection or account state, send the exact notice rather than applying generic steps blindly.
Request assessment