How do I verify Google Search Console with an HTML tag?
Verification
The HTML tag method proves you control a URL-prefix property by adding a google-site-verification meta tag to your homepage. Search Console generates the tag, you place it in the <head> of the page served at the property's address, publish, and click Verify. Leave the tag in place afterwards, because Search Console keeps checking for it. Domain properties can't use this method; they need a DNS record.
Step by step
- In Search Console, add a URL prefix property that matches your site exactly, for example
https://www.example.com/. The protocol and thewwwboth matter. - Choose HTML tag as the verification method and copy the tag Search Console shows. It looks like
<meta name="google-site-verification" content="...">, with a token tied to your account. - Paste it inside the
<head>section of your homepage. The tag must sit within the first 2 MB of the file, so keep it near the top. - Publish the change.
- Open the homepage while signed out (a private window works), view the source and search for
google-site-verification. If you can't find it there, Google can't either. - Return to Search Console and click Verify.
Where the tag goes on common setups
- Static or hand-built sites: the shared header template, or the homepage file itself if each page carries its own head.
- WordPress and other CMSs: many SEO plugins have a field for a Google verification code. Some want the whole tag and others only the token inside
content, so follow the plugin's instructions. See Search Console for WordPress. - Sites behind a cache or CDN: purge the cached homepage after publishing, or Google may still be served the old HTML.
Why HTML tag verification fails
Google's verification help names three failures for this method:
- Tag not found or in the wrong place. It went onto a different page, landed outside
<head>, or was added to a local copy that never got published. - Wrong tag content. A colleague's token, a token cut short while copying, or an old tag from another account.
- Syntax error. Broken quotes or a malformed element, often the result of pasting through an editor that turns straight quotes into curly ones.
The homepage must also load without a login. If none of these applies, compare the live source with the tag character by character, and see why verification fails for the other methods.
Keep the tag after verifying
Verification lasts only while Search Console can still find your token. It checks periodically; if the tag disappears, you are notified, and your permissions expire after a grace period. Redesigns and theme switches are how tags usually vanish, so add a second method, such as a DNS TXT record, as a fallback.
Several owners can each keep their own tag on the same page, so never overwrite someone else's token. Deleting a person's tag is also how you remove them as a verified owner, as explained in owners versus users.
How AutoPSEO helps
Verification is the only step that touches your site. After it, connect the Google account to AutoPSEO and every property the account can read appears automatically, with no further tag or code. Live properties read Search Console's last 16 months; full-storage properties also import their history and keep adding to it every day.
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.