Providers / Google Search Console
SEO
Google Search Console domains, keys and logins
What every Google Search Console credential a founder holds does, whether it expires, and what tends to break. Each fact links to Google Search Console's own docs.
At a glance
| Credential | Expiry | Permissions |
|---|---|---|
| Google account (Search Console owner login) | Not documented | – |
| Site verification token (DNS TXT, HTML file, meta tag, Analytics or Tag Manager) | Not documented | Can be scoped |
| OAuth 2.0 client secret (Search Console API) | Not documented | Can be scoped |
Each credential
Google account (Search Console owner login)
- Not documented
Access is per Google account. Verified owners have the highest permission level; users have lower levels. A verified owner's loss of access expires their property permissions after a grace period if the verification is not fixed.
Site verification token (DNS TXT, HTML file, meta tag, Analytics or Tag Manager)
- Not documented
- Can be scoped
Verification lasts only as long as Search Console can confirm the token. Removing the HTML file or the meta tag causes loss of verification. For a Domain property (DNS only), do not remove the DNS record after verification. If all verified owners lose access, all users lose access to the property. Child properties inherit the parent's verification method. Verification token has no documented expiry period.
OAuth 2.0 client secret (Search Console API)
- Not documented
- Can be scoped
Created in the Google API Console when registering an OAuth client; Search Console API requires OAuth 2.0. Scopes: https://www.googleapis.com/auth/webmasters (read/write) and https://www.googleapis.com/auth/webmasters.readonly (read-only). Access tokens are described as short-lived with no duration given.
What usually goes wrong
- DNS verification TXT record removed from the DNS provider, causing loss of verified access
- HTML verification file or meta tag removed during a site redeploy
- Only verified owner leaves the Google account and no other owner remains
- OAuth consent or client secret rotated and the integration stops authenticating
- Domain registration lapses and DNS verification stops resolving
Renewals and billing
- Domain registration for a Domain property. A Domain property depends on the DNS verification record remaining in place, which depends on the domain staying registered.
Search Console is free. Search analytics data is available through the Search Console API; no billing or spend API applies.
What Google Search Console's docs don't say
We couldn't confirm these from official docs, so don't rely on them either way:
- Whether verification tokens or meta tags ever expire on their own
- Refresh token expiry and testing-mode limits for the OAuth client
- Whether service accounts can be added as users to a Search Console property
- Exact grace period before permissions expire when verification fails
- Domain registrar renewal terms
Rotating or replacing a Google Search Console key
The steps are the same for most providers: make the new key, deploy it everywhere the old one is used, check it works, then revoke the old one. Our guides walk through it:
Sources
- support.google.com/webmasters/answer/9008080
- developers.google.com/webmaster-tools/v1/how-tos/authorizing
Keep track of every Google Search Console key
StackHangar stores your Google Search Console keys in an encrypted vault, grouped by the product they belong to, warns you before they expire, and walks you through rotating them. We can't read your secrets.