I operate a self-hosted application used exclusively by me to analyse Search Console data for my own website. It is not offered to other users. The application uses only https://www.googleapis.com/auth/webmasters.readonly for this integration; the site list and Search Analytics requests work.
The OAuth project has an External audience because I use a consumer Google account. Publishing status is Testing. I want to remove the Testing-specific seven-day authorization expiry while keeping the application private and complying with the personal-use exception.
Current configuration:
- App name, user-support email and developer-contact email are populated and saved.
- The exact webmasters.readonly scope is declared under Data Access.
- Existing OAuth client type: Web application, with an already registered loopback callback used successfully.
- No logo, homepage, privacy-policy URL or terms URL is configured. An existing authorized domain is retained for another existing client callback.
- Saving Branding again and fully reloading the page did not resolve the issue.
Audience shows a disabled Publish app button with: “To publish your app, you must complete your configuration on the Branding page.” Branding shows no specific missing-required-field error. Verification Center says verification is unnecessary because the app is in Testing.
The OAuth policy defines personal use and excludes it from the definition of a production app for those requirements. Other help pages describe information URLs as required for external production apps. Could Google clarify the supported configuration for this exclusively personal-use case?
- Can this project use In Production publishing status under the personal-use exception without public application-information pages?
- Which exact field or action is required to enable Publish app in the current console?
- If information URLs are required despite personal use, which URLs and domain-verification steps are mandatory?
- After the supported status change, is authorizing again with the same client and read-only scope sufficient to replace the Testing-limited refresh token?
I am not requesting a bypass of consent or security controls. I want a supported private setup without the Testing-specific seven-day expiry.
References:
No credentials, project identifiers, account email addresses or report contents are included in this question.