App Homepage

General Guidance

As a reminder, your app homepage must meet the following requirements:

Accurately represent and identify you app or brand
Fully describe your apps functionality to users
Explain with transparency the purpose for which your app requests user data
Hosted on a verified domain you own
Your homepage and privacy policy should not be hosted on a third-party platform where you can't verify that you own your subdomain. For example: Google Sites, Facebook, Instagram, Twitter.
Include a link to your privacy policy (Note: this link should match the link you added on your consent screen configuration)
Visible to users without requiring them to log-in to your app

Important! Not meeting these requirements can slow down the verification process. Please make sure your homepage has met the above criteria before including it in your submission.

Examples of Common Issues

Need further guidance on your homepage submission? Navigate to the relevant finding for targeted remediation instructions.

You have provided us with an unresponsive homepage URL

Your home page submission must be easy to access, easy to understand, and relevant to the app you have submitted for verification.

If you have been flagged for an unresponsive homepage URL, follow these steps to update your Cloud Console submission with an accessible URL to your homepage:

Go to the OAuth consent screen page for your project. You can find it by updating the following URL with your project ID: https://console.cloud.google.com/apis/credentials/consent?project=[PROJECT_ID]
Update the required homepage URL field.
Once the URL is updated, click Prepare for verification at the bottom of the last page.
On the Prepare for verification screen, confirm that the information is correct, then click Submit for verification on the final page.

Helpful tip! This is also a great opportunity to make sure your homepage meets all other app homepage requirements. Doing so will help expedite the remainder of the verification process.

The website you provided as your homepage is not registered to you

We require that you verify the ownership of your application homepage. If you have been flagged for an unverified homepage domain, please proceed with the best option below for your project.

Option 1: Verify your existing app homepage

Follow these instructions to verify the submitted homepage belongs to you. Respond to the email you received to confirm that ownership has been verified.

Option 2: Submit another homepage for verification which has already been verified as registered to you

If you have an alternative home page for your app hosted on an existing domain that is registered to you, you can resubmit for verification with the verified domain.

Once you have resolved this and all other issues, resubmit your verification request in the Cloud Console with the verified homepage URL.

Important! Only resubmit your verification request once you have addressed all issues with your submission.

The provided homepage URL redirects to a different domain than the one listed on the OAuth consent screen

To avoid ambiguity for users, your app homepage URL must be static and cannot redirect to a different URL or domain. The homepage linked on your consent screen must match the link presented in-browser to a user.

If your homepage URL has been flagged for redirecting to a different domain, please follow the steps below.

Update your OAuth consent screen configuration to directly link to your homepage:

Go to the OAuth consent screen page for your project. You can find it by updating the following URL with your project ID: https://console.cloud.google.com/apis/credentials/consent?project=[PROJECT_ID]
Update the required homepage URL field with a static URL.
Once the URL is updated, click Prepare for verification at the bottom of the last page.
On the Prepare for verification screen, confirm that the information is correct, then click Submit for verification on the final page.

The provided homepage domain appears to be a shortened or condensed link

To avoid ambiguity for users, the homepage URL linked on your consent screen must match the link presented in-browser. If you provided us with a shortened or condensed link to your homepage, we ask that you update your OAuth consent screen configuration to provide the full domain. For example: https://www.google.com/about is a valid domain; https://www.g.co/about is an invalid domain.

Update your OAuth Consent screen configuration with a non-shortened URL for your app homepage:

Go to the OAuth consent screen page for your project. You can find it by updating the following URL with your project ID: https://console.cloud.google.com/apis/credentials/consent?project=[PROJECT_ID]
Update the required homepage URL field with a static URL.
Once the URL is updated, click Prepare for verification at the bottom of the last page.
On the Prepare for verification screen, confirm that the information is correct, then click Submit for verification on the final page.

Your homepage is behind a login page

Users should be able to easily understand the purpose of your application and why you require their Google user data.

This issue indicates your homepage requires user login to view any details about your application. Please proceed with the best option below for your project:

Option 1: Update your existing app homepage to allow users to view information about your app without needing to login

Update your homepage to describe the purpose of the application without requiring login.
Respond to the email you received to confirm that your app homepage has been updated.

Option 2: Update your consent screen with a different app homepage that is not behind a login page

Go to the OAuth consent screen page for your project. You can find it by updating the following URL with your project ID: https://console.cloud.google.com/apis/credentials/consent?project=[PROJECT_ID]
Update the required homepage URL field with a new homepage URL.
Once the URL is updated, click Prepare for verification at the bottom of the last page.
On the Prepare for verification screen, confirm that the information is correct, then click Submit for verification on the final page.

Helpful tip! This is also a great opportunity to make sure your homepage meets all other app homepage requirements. Doing so will help expedite the remainder of the verification process.

Your homepage URL does not display information about the application.

Users should be able to easily understand the purpose of your application and why you require their data. The homepage you submitted does not explain your application’s functionality or features. Please proceed with the best option below for your project:

Option 1: Update your existing app home page to explain the purpose of your app and how it uses Google user data you are requesting

Update your homepage to sufficiently explain your application’s purpose and features.
Respond to the email you received to confirm that your app homepage has been updated.

Option 2: Update your consent screen with a different homepage for your app that explains the purpose of your app and how it uses Google user data you are requesting

Go to the OAuth consent screen page for your project. You can find it by updating the following URL with your project ID: https://console.cloud.google.com/apis/credentials/consent?project=[PROJECT_ID]
Update the required homepage URL field with a link to a homepage that describes the purpose of your app.
Once the URL is updated, click Prepare for verification at the bottom of the last page.
On the Prepare for verification screen, confirm that the information is correct, then click Submit for verification on the final page.

Your homepage does not include an easily accessible link to your privacy policy.

Google's OAuth 2.0 policy states that every production application must have a homepage that includes a link to a privacy policy. The homepage you submitted does not include a reference to your privacy policy. Please choose one of the following options to proceed with your app's verification:

Option 1: Update your existing homepage to include a link to your privacy policy

Update your homepage to include a link to your privacy policy
Respond to the email you received to confirm that your app homepage has been updated

Note: You do not need to update your OAuth consent screen configuration if you choose this option.

Option 2: Update your consent screen with a different homepage for your app that includes a link to your privacy policy

Go to the OAuth consent screen page for your project. You can find it by updating the following URL with your project ID: https://console.cloud.google.com/apis/credentials/consent?project=[PROJECT_ID]
Update the required homepage URL field with a homepage that links to your privacy policy.
Once the URL is updated, click Prepare for verification at the bottom of the last page.
On the Prepare for verification screen, confirm that the information is correct, then click Submit for verification on the final page.

Was this helpful?

How can we improve it?