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.

Last checked 2026-11-06 · search.google.com/search-console

At a glance

CredentialExpiryPermissions
Google account (Search Console owner login)Not documented–
Site verification token (DNS TXT, HTML file, meta tag, Analytics or Tag Manager)Not documentedCan be scoped
OAuth 2.0 client secret (Search Console API)Not documentedCan be scoped

Each credential

Google account (Search Console owner login)

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.

Google Search Console docs

Site verification token (DNS TXT, HTML file, meta tag, Analytics or Tag Manager)

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.

Google Search Console docs

OAuth 2.0 client secret (Search Console API)

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.

Google Search Console docs

What usually goes wrong

Renewals and billing

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:

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

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.