Official statement
Other statements from this video 1 ▾
Google now allows automatic verification of classic Google sites (Sites, Blogger, etc.) in Search Console, provided you use the same account for both services. This simplification eliminates tedious manual validation steps via HTML tag or DNS. Specifically, you just need to select the 'URL prefix' option when adding a property to trigger the automatic account recognition.
What you need to understand
Which Google Sites are affected by this automatic verification?
The statement targets “classic Google sites”, a deliberately vague term. In practice, this primarily covers Google Sites (the website creation tool) and Blogger (the blogging platform).
These properties share a common characteristic: they are hosted on Google's infrastructure and linked to a single Google account. It is this direct connection between the site owner's account and the Search Console account that enables automatic verification, bypassing traditional methods.
How is this method different from other types of verification?
Traditionally, Search Console offers several verification methods: HTML tag in the <head>, HTML file upload, DNS record, Google Analytics, or Google Tag Manager. Each requires a manual technical action.
Here, the automatic verification circumvents all that. Google detects that you already control the site through your Google account and applies an implicit validation. No copying and pasting code, no FTP access, no DNS changes — just identity recognition between two Google services.
Why doesn't Google apply this method to all sites?
Because the majority of websites are not hosted by Google. A self-hosted WordPress, a Shopify site, a custom website — none have a direct link to a verifiable owner Google account.
Automatic verification relies on the fact that Google controls both the site and the verification tool. It's a niche use case: how many professional SEOs still manage live Google Sites? The statement thus targets a very small audience — likely non-technical users or internal projects.
- Automatic verification: reserved for sites hosted on Google's infrastructure (Sites, Blogger)
- Mandatory prerequisite: use the same Google account to manage both the site AND Search Console
- Option to select: “URL prefix” when adding a property (not “Domain property”)
- Practical limitation: only works if you are already logged in with the correct account at the time of addition
- No technical action required: no HTML tag, no DNS, instant validation
SEO Expert opinion
Is this statement consistent with observed practices in the field?
Yes, but it concerns a ultra-minority segment of the market. Professional SEOs rarely work on live Google Sites — these platforms are technically limited, offer little control over crawling, and lack flexibility for advanced optimizations.
Automatic verification has existed for these properties for years, but Google is formalizing it here as if it were a novelty. [To be verified]: the exact timeline of the rollout of this feature is unclear in the statement. There is a lack of concrete data on adoption rates and actual use cases.
What limitations are not mentioned by Google?
First point: this method works only for “URL prefix” properties, not for “Domain” type properties. If you want to aggregate data from multiple subdomains or protocols (http/https), you will need to go through a traditional DNS verification.
Second point: automatic verification does not guarantee access to historical data. If the site existed before its addition in Search Console, you will only see data from the date of addition. And third point — and this is rarely mentioned — if you lose access to the site’s owner Google account, you also lose verification in Search Console. No recovery is possible without a complete reset.
In what cases does this method pose governance issues?
Imagine a multi-site agency or company context. If an employee creates a Google Site with their personal account, then adds it to Search Console with the same account, what happens when they leave the company? You lose access to the site AND the console.
This is a risk of ambiguous ownership. Unlike a DNS verification or HTML tag — which can be transferred or replicated — automatic verification ties ownership to an individual account. Google does not specify anywhere how to manage ownership transfers in this case. [To be verified]: is there an official process for transferring automatic verification without reverting to a manual method?
Practical impact and recommendations
What should you do if you're managing a classic Google site?
First step: make sure you are logged in with the correct Google account before opening Search Console. If you juggle between multiple accounts (personal, professional, client), open a private browsing window and explicitly log in with the site owner account.
Then, go to Search Console, click 'Add a property', select “URL prefix” (not “Domain”), enter the full URL of the site (with https://), and click 'Continue'. If everything is configured correctly, Google will instantly display a successful verification message — without asking for a tag or file.
What errors should you avoid during this process?
Classic mistake: choosing the “Domain” option instead of “URL prefix”. The Domain option requires DNS verification — it does not trigger automatic verification, even for a Google Site. You will end up facing a pointless DNS configuration screen.
Another trap: being logged in with a different account from the one that manages the site. Google cannot link the two services, and the verification fails. Result: you either have to log back in with the correct account or switch to a manual method — nullifying all the interest.
How can you ensure that verification remains active over time?
Automatic verification is permanent as long as the owner account remains active. However, if you transfer the site to another Google account (change of ownership), the Search Console verification does not automatically follow.
You must either add the new owner as a user in Search Console before the transfer or the new owner must reverify with their own account. Always document access in a centralized manager — do not rely on institutional memory.
- Log in explicitly with the site owner's Google account before opening Search Console
- Select the “URL prefix” option, never “Domain”, to trigger automatic verification
- Enter the full URL with
https://— do not let Google guess the protocol - Immediately check that the property appears in your list of verified sites
- Document the account used for verification in a shared access manager (1Password, Dashlane, etc.)
- If the site needs to be transferred, first add the new owner as a user before removing the old one
Automatic verification simplifies the addition of Google Sites and Blogger in Search Console, but it also creates a strong dependence on the owner account. For professional use, this method remains fragile — a DNS verification or HTML tag offers more control and longevity.
If you manage several Google properties or if your SEO infrastructure relies on critical Search Console data, establishing rigorous access governance can quickly become complex. In this context, working with a specialized SEO agency allows you to structure these processes, anticipate ownership transfers, and avoid data loss during transitions.
❓ Frequently Asked Questions
La vérification automatique fonctionne-t-elle pour tous les types de propriétés Search Console ?
Que se passe-t-il si je change le propriétaire d'un Google Site déjà vérifié dans Search Console ?
Puis-je utiliser la vérification automatique si je gère le site avec un compte Google Workspace ?
La vérification automatique donne-t-elle accès aux données historiques du site ?
Peut-on combiner vérification automatique et vérification manuelle sur le même site ?
🎥 From the same video 1
Other SEO insights extracted from this same Google Search Central video · duration 0 min · published on 11/12/2019
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.