Google Site Verification: How to Check, Add and Fix It

How Google Site Verification Works

Search Console exposes sensitive material such as search queries, crawl errors and manual actions, so Google asks you to verify site ownership first, using a token tied to your Google account. The full list of methods sits in Google's help page, verify your site ownership.

The property type decides which methods you can use. A Domain property covers every protocol and subdomain at once and can only be verified through DNS. A URL prefix property covers one exact address, such as https://www.example.com/, and accepts every method.

The token has to stay where you put it, because Search Console rechecks it and lets the permission lapse after a grace period if it cannot confirm ownership. Each owner has a separate token, so never overwrite one that someone else relies on, and a verified owner can add a delegated owner who needs none. None of this touches rankings. The same google-site-verification= format also appears when you prove a domain to Google Workspace, but that is a separate token for a separate job.

How SEO Site Checker Tests Google Site Verification

Our report looks for two of the verification routes and says plainly that it cannot see the others.

Rule: the row passes when the google-site-verification meta tag is found with a value, or when a matching TXT record is found on the host you typed. It fails when neither is found, and that switches on the red How to Fix button.

When the tag is present, the report prints the token it read. The page is fetched by a generic automated client, so a firewall can answer with a 403 and hide a tag that real visitors see. A tag in the body passes here although Google expects it in the head. Google Analytics verification, Google Tag Manager verification and the HTML file are invisible to this check, so a verified site can still fail.

What a pass means

An automated visitor found a token, so the setup is probably intact. Confirm it under Ownership verification settings in Search Console.

What a fail means

Neither a tag nor a TXT record was visible on the tested host. You may still be verified by file, Analytics, Tag Manager or a record on the other hostname.

Google Site Verification Methods Compared

Pick the method that matches the access you have. The last column shows which ones our report can see.

For most sites the meta tag is quickest. Choose the TXT record for a Domain property, which survives theme changes. Google allows several methods at once, so add a backup. Our Google Analytics check shows if that snippet is still live.

How to Add the Google Site Verification Meta Tag

This meta tag verification takes about five minutes.

1. Add the property. In Search Console add a URL prefix property for the exact address, open Other verification methods, choose HTML tag and copy the tag.
2. Paste it into the head. Place it near the top of the head on the page a signed out visitor reaches at that address, allowing for redirects to www or a language folder. Google only reads the first 2 MB of the file.
3. Publish and purge. Save, then clear your page cache or CDN so the live HTML contains the tag.
4. Check and verify. Use view page source in a private window to find the token, then press Verify and leave the tag in place.

<head>
  <meta charset="utf-8">
  <meta name="google-site-verification" content="YOUR_TOKEN_HERE">
</head>

It is an ordinary name and content attribute pair, explained in the meta name attribute reference. See meta tags explained for the head section, and the Meta Tag Analyzer lists the tags a visitor receives.

WordPress

Yoast SEO has a Google verification code field in its Webmaster tools tab, called Site connections in newer releases, and Rank Math has a Search Console box under Webmaster Tools. Site Kit by Google can also verify for you. Paste the content value or whole tag, as the field asks. Without a plugin, use your child theme's header.php.

Shopify

Open Online Store, then Themes, then Edit code. In layout/theme.liquid, paste the tag just before the closing head tag and save. Repeat this if you switch themes, because the tag lives in the theme.

Wix and other site builders

Wix keeps this in its Search Console connection settings and may require a connected domain. Webflow and Squarespace offer a custom code box for the head.

How to Add a Google Site Verification TXT Record

1. Get the value. Choose a Domain property in Search Console and copy the TXT record value, which starts with google-site-verification=.
2. Open your DNS panel. That is wherever your nameservers point, such as your domain registrar, Cloudflare DNS or the cPanel zone editor.
3. Add a new TXT record. Set the host name to @ for the apex domain, or leave it blank on some hosts, and paste the whole value.
4. Wait for DNS propagation. Google says some providers need two or three days, though it is often quicker. Then press Verify.

Type:  TXT
Name:  @
Value: google-site-verification=YOUR_TOKEN_HERE

To confirm the record is live, run dig on macOS or Linux, or nslookup on Windows.

dig TXT example.com +short
nslookup -type=TXT example.com

Either should print your token. Add it as a new record and leave your SPF record alone, since a domain can carry many TXT records, as our SPF record guide shows. The Cloudflare TXT record reference notes that you can paste TXT content without quotation marks and Cloudflare adds them for you. To see what is live, use the DNS Record Lookup or read how to find DNS records. If the record sits on the root domain, test it without www.

Why the Report Says Not Found When Your Site Is Verified

A red result beside a working property usually means the token lives somewhere we do not look. The causes below also explain a verification failed message in Search Console.

• A method we cannot see. You verified by HTML file, Google Analytics or Tag Manager, and we read only the tag and the TXT record.
• The wrong hostname. The record is on the root domain but you tested the www subdomain, or the other way round.
• A malformed tag. The name has a capital letter, the content is empty, or stray quotes and spaces came along with the token.
• A page we could not read. Your homepage may be blocked by bot protection, redirect to a login page or answer slower than about 3 seconds.
• A tag added by JavaScript. We read raw HTML, not the page after scripts run.
• Stale copies. A page cache, a CDN or unfinished propagation can hide your change.

How to Keep Google Site Verification From Breaking

Verification usually breaks when a theme swap drops the head tag, a host or CMS move rebuilds the templates, or a DNS change leaves the TXT records behind.

• Keep it permanently. Copy the tag or record across whenever you change theme, CMS or host.
• Add a backup method. A DNS record beside the meta tag means one template change cannot cut you off.
• List every owner. If all verified owners lose access, every user of the property loses it too.
• Submit your sitemap. Verified access is what lets you submit a sitemap and see how Google reads it.
• Test after changes. Run a fresh report after every migration.