Google OAuth demo video rejected — how to fix it
The demo video trips people on details, not effort. Reviewers need to see the full grant flow, in English, with the OAuth client ID visible — and every sensitive scope demonstrated.
A sensitive-scope submission needs a video that proves the consent experience and shows each scope actually being used. The most-missed detail is the OAuth client ID in the browser's address bar during the consent screen — reviewers look for it to confirm the video matches the app under review. Wrong visibility on YouTube, a flow that isn't in English, or a scope you never demonstrate are the other common misses.
Each fix below traces to a requirement Google publishes.
Nothing here is our opinion. Every requirement links to Google’s own page — open it and verify the fix yourself before you resubmit.
“The video must show the full OAuth grant flow, in English.”
“The consent screen in the video must show the correct app name, and the OAuth client ID must be visible in the address bar.”
“Demonstrate the functionality of each requested sensitive scope — one scene per scope, none left out.”
“Upload the demo video to YouTube as Unlisted and paste that link into the console field.”
Do these in order.
- 01
Record the full OAuth grant flow, in English
Show the app from the 'Sign in with Google' click through the consent screen to the granted state — the complete flow, narrated or captioned in English.
- 02
Show the client ID in the address bar
During the consent screen, make sure the URL — including the OAuth client ID — is visible and readable. Hold or zoom on it. This is the detail almost everyone forgets.
- 03
Demonstrate each sensitive scope
One scene per requested sensitive scope, showing the feature that uses it. Don't leave a scope undemonstrated.
- 04
Upload Unlisted and paste the link
Upload to YouTube as Unlisted (not Private, not Public) and paste that link into the console's video field.
See exactly what Google’s crawler sees — free.
Paste your URL and scopes. The pre-check fetches your homepage the way Google does, finds your privacy-policy link, and flags the blockers this rejection is about — in seconds, no signup.
Straight answers.
What's the detail people most often miss in the demo video?
The OAuth client ID visible in the address bar during the consent screen. Reviewers use it to confirm the video is really your app under review.
Does the video have to be in English?
Yes. Record the full grant flow in English, and demonstrate each requested sensitive scope on screen.