Websites and developer verification
Choose a company website, host app support and privacy pages, and understand which Google verification you need.
A company website, an app’s support pages and Google Sign-In verification serve different purposes. Start with the task named in your provider account, then follow the matching steps below.
You can keep several apps under one company. Each app should have clearly named support and privacy pages that describe its own behavior.
On this page
Which website is this asking for?
Completing one check does not complete the others. A working privacy-page link is not proof of company ownership or OAuth approval.
| Task | Website to provide |
|---|---|
Play organization verification | Your organization’s main website, associated with the developer account through Search Console. |
App store support and privacy | Public pages identifying the app, its developer, contact information and actual data practices. |
Google OAuth verification | The app homepage and privacy policy, with the domain ownership and Google Cloud project relationship required by the OAuth review. |
Do I need to buy a separate domain for each app?
No. One company website can introduce the business and link to separate pages for each product. Use the organization that actually owns the apps; access to someone else’s website is not proof that it belongs to your company.
For store support and privacy pages, a suitable free host can work. The pages must be publicly accessible and contain real app information. A hosting choice alone does not establish compliance.
GitHub Pages can host an informational company or project site. Follow its usage terms: it is not intended to operate an e-commerce business or commercial SaaS. Keep app databases, sign-in and payments in appropriate services.
Can I use GitHub Pages or Google Sites?
Both can serve public informational pages. For Play website verification, check the ownership method Search Console offers for your exact address. GitHub Pages lets you place a verification tag or file in your own published site. Modern Google Sites without a custom domain has different verification methods; do not assume you can upload an HTML verification file there.
In our tested GitHub Pages flow, URL-prefix verification using an HTML tag succeeded, followed by Play’s website association. That result applies to the Play process, not to OAuth domain verification.
Keep existing working app-policy links when adding a company homepage. You do not need to move every app page just to create the company site.
Verify a GitHub Pages company site for Google Play
Publish the company site
Include the legal company identity, a short explanation of its products or services and a working contact method. Check the public HTTPS page and its links while signed out.
Add the exact website to Search Console
Check existing properties first. For a project address, choose URL prefix and include the full published path. Use an account authorized to manage the company site.
Use an offered ownership method
For HTML-tag verification, copy Google’s tag into the homepage head and publish the change. Check the live page contains it, then select Verify. Keep the tag after success.
Complete the Play association
Save the organization website in Play Console’s Account details and send its verification request. The same verified-owner Google account can approve automatically; a different owner must approve the request.
Check the result
Confirm Website verified in Play Console. Search Console ownership and a successful website deployment are earlier steps.
Actual Search Console form, October 2026. The displayed Sites address illustrates URL entry, not a successful verification. For GitHub Pages, enter your own full published address.
Google Search Console ownership methods- For the Play hosted-website process, choose the property matching your exact published URL and path.
- Complete an offered ownership method, then the separate Play association.
- OAuth domain verification has different DNS-level requirements.
Is this the same as my old Google OAuth review?
No. Play verifies the developer account and its website association. OAuth review concerns an app’s Google identity and requested access to Google user data.
Google’s current OAuth domain troubleshooting guidance requires DNS-level Domain verification and the correct Google Cloud project owner relationship. An HTML tag on a free hosted URL is not equivalent. Follow the current review instructions for your project rather than relying on an older approval email.
One owned domain can serve several apps, each with clear branding and policy links. A free host with a custom domain can be an option when you control the DNS. Email/password sign-in by itself does not create a Google OAuth review requirement.
Which name and email should I use?
A D-U-N-S number identifies the organization, not an app or email address. Check for the organization’s existing number before requesting another. Changing the sign-in email does not create a new legal company.
| Field | What belongs there |
|---|---|
Public developer name | The developer brand shown to customers; it can differ from the legal company name. |
Legal organization name | The company name matching its legal records and the relevant payments/D-U-N-S details. |
Person verifying identity | The representative’s legal name, matching their ID. |
Account owner | The Google account authorized to manage the developer account. It can manage more than one product or website. |
Contact details for Google | Working details Google can use to contact the account owner or representative. |
Public developer and app support details | Contact methods you intend customers to use. Read which fields Google will display publicly. |
Why are documents or phone numbers requested twice?
Read each task heading. A representative’s identity and the organization’s existence are separate checks. If company evidence is requested again, use the accepted-document list for that exact task and country; do not assume you must find a different document.
A document upload or registration receipt is not approval. Follow the remaining tasks on Play Console Home. Phone verification may stay unavailable until the required identity, organization and website checks are approved.
The private contact number and public developer number have separate verification controls, even when you use the same number. Enter SMS or call codes directly in Google. If an old prerequisite warning remains after the required tasks are confirmed complete, refresh once and check again.
What happens after verification?
Return to the same app’s publishing conversation. Tell the agent which provider task is complete, and continue from the saved work. Account verification does not create your app record, connect an API credential, upload a build or release an app.
Ask the agent to check the next supported step. Keep private sign-in, identity documents, verification codes, payments and agreements in the provider’s own forms. Never paste credentials into chat.