What verification methods does Google Search Console offer?
Verification
It depends on the property type. A Domain property can only be verified with a DNS record at your domain name provider. A URL-prefix property can use that DNS record too, or an HTML file upload, an HTML tag, Google Analytics or Google Tag Manager. Sites built on Google Sites, and newer Blogger blogs, are verified automatically when you sign in with the account that manages them.
The methods compared
| Method | Property types | What you need | Keep in mind |
|---|---|---|---|
| DNS record | Domain and URL-prefix | Access to your domain's DNS settings | Some providers can add it for you; a manual record can take two or three days to work |
| HTML file | URL-prefix | Upload rights to the site's root folder | The file must stay unchanged, reachable without a login or a redirect |
| HTML tag | URL-prefix | Edit access to the homepage's <head> | It must sit within the first 2 MB of the page |
| Google Analytics | URL-prefix | Edit permission in Analytics, with gtag.js or analytics.js in the homepage <head> | Use the same Google account in both products |
| Google Tag Manager | URL-prefix | Publish or Admin permission on the container | The <noscript> part goes right after <body> |
| Google Sites or Blogger | Sites hosted by Google | Sign in with the account that manages the site | Older Blogger blogs use the HTML tag instead |
Source: Verify your site ownership. A DNS record that verifies a URL-prefix property also verifies the matching Domain property.
Which method to choose
- You control DNS: verify a Domain property with a TXT record. It covers every subdomain and both protocols, and it survives redesigns and CMS changes. See DNS verification.
- You can edit the site but not DNS: the HTML file or the HTML tag (HTML tag verification).
- Analytics or Tag Manager is already on the homepage and you have the permissions: those methods avoid touching the site at all.
- You work for a client: ask them to verify with a method they control and add you as a user, so access doesn't depend on your files or accounts.
Domain vs URL-prefix properties explains the property types themselves.
Staying verified
Verification lasts only while Search Console can still find your token, and it re-checks from time to time. If the token disappears, you are notified, and your permissions expire after a grace period. A few habits prevent that:
- Leave the file, tag or DNS record in place after verifying.
- Never overwrite another owner's token; several owners can each have their own on the same site.
- Add a second method as a backup, so a redesign that drops the tag doesn't lock you out.
If every verified owner loses verification, delegated owners and users lose access too. When something goes wrong, verification failed walks through each method's errors.
How AutoPSEO helps
Verification is the only step that touches your site. After it, connect your Google account: AutoPSEO lists every property the account can read as an owner, full user or restricted user, and leaves out properties that aren't verified.
Put your SEO content on autopilot
Connect Search Console and your site. AutoPSEO scans it and plans the first topics right away. No credit card needed.