Skip to main content
Question

OAuth branding verification keeps failing though home page HTML has app name & description (confirmed in Search Console)

  • July 27, 2026
  • 0 replies
  • 5 views

perfeclien.calender

I'm trying to verify the OAuth consent screen (branding) for my app and it keeps failing on the same two issues, even though my home page appears to meet the requirements.

App details:
- App name (consent screen): Perfect Lien Law
- Home page: https://perfectlien.com
- The app requests the Google Calendar sensitive scope (calendar deadline sync)
- Authorized domain ownership is verified in Google Search Console under the same account

The two errors branding verification returns:
1. "Your home page does not explain the purpose of your app."
2. "The app name 'Perfect Lien Law' configured for your OAuth consent screen does not match the app name on your home page."

Why I believe the home page already meets both requirements:
- The site was originally a client-side React app (empty #root in the HTML), so I added server-rendered content. The raw HTML of https://perfectlien.com now contains a <title>Perfect Lien Law...</title>, a <meta name="description"> describing the app, and an <h1>Perfect Lien Law</h1> plus a paragraph explaining that it's a Texas mechanics-lien platform where clients can sync filing deadlines to Google Calendar.
- I confirmed this in Search Console → URL Inspection → Test Live URL → "View Tested Page" → HTML: it returns HTTP 200 OK, content-type text/html, all resources loaded, no JS console errors, and the rendered HTML shows the app name and the description.
- View Source (Ctrl+U) on the live home page also shows the app name and description as real text.

Despite this, when I select "I have fixed the issues" and click Proceed in the Verification Center, the branding status still shows the same two errors.

My questions:
1. Which exact URL and HTML does the branding verification crawler fetch? (I want to check for a caching or www vs non-www mismatch versus what Search Console tested.)
2. Is there a known delay/queue between resubmitting and the branding check re-running, or should it be near-instant?
3. Is there anything else the crawler checks for the app name / purpose that I might be missing, given the above is confirmed present?

Any guidance on how to get the branding verification to re-evaluate the current page, or how to escalate to the verification team, would be appreciated. Thank you.