OAuth Verification - Homepage requirement clarification needed

Google Cloud Apigee
1

Hi everyone,

The Problem:
My homepage was behind a login page, so Google rejected my OAuth verification with “Homepage does not explain the purpose of your app” error. I fixed this by creating a public homepage that explains my app, but Google’s system seems to still show the old cached version.

What I Did:

  • Created public homepage explaining app purpose
  • Added Privacy Policy and Terms of Service (linked in footer)
  • Added logo and app description
  • Submitted for re-verification

Current Homepage: https://srv1163862.hstgr.cloud/

Tracking Number: c3392606046122555

App Details:

  • App: SPITI365 (internal real estate management)
  • Scopes: Google Calendar API (calendar, calendar.events)
  • Users: Internal employees only

My Questions:

  1. How long does it take for Google to see the updated homepage (not cached)?
  2. Has anyone experienced this caching issue?
  3. Is there a way to request a fresh review?

Thanks for any help!

image
image942×934 78.3 KB

2

Hey @stylkonst! Thanks for reaching out to the Apigee forum :slight_smile:

Just curious to confirm if your query relates specifically to Apigee? If so, please elaborate on how you are using Apigee in this flow so the community can properly share guidance on your issue.

Otherwise, I advise reviewing other community forums to get more tailored answers, such as:

Thanks, and happy new year!

3

Thank you @AlexET for the tips, those forums would be better places to ask this since it’s not apigee related.. But from my experience it can take 1-5 days to get validated, depending on how your web app is structured. What has helped for me in the past is to make sure that Terms of Service and Privacy policies are clearly linked from the web app, and that the name is the same as the OAuth name, then the auto-validation should be fast (for me took a couple of hours sometimes when it’s very clearly structured).

1 Like