Google Search Console verification is how you prove to Google that you own or manage a website, so that Search Console shows you the site's data and lets you use its tools. You add the site as a property, Search Console gives you a unique token, you put the token where Google can find it, and you click Verify. A Domain property is verified with a DNS record. A URL-prefix property can also be verified with an HTML tag, an HTML file, Google Analytics or Google Tag Manager. Keep the token in place afterward: if it disappears, you lose access.
For what the tool does once you are in, see what Google Search Console is and what each report shows. Below: every method step by step, platform steps, fixes for the common errors, and which property type 871 verified sites use.
How to verify your website on Google Search Console
- Open Google Search Console and sign in with the Google account that should own the site.
- In the property selector at the top left, click Add property.
- Choose Website property (a Platform property is for an Instagram, TikTok, X or YouTube account). Then choose Domain and enter the bare domain (
example.com), or choose URL prefix and enter the full address your site uses (https://www.example.com/). - Pick a verification method. Search Console lists the methods that work for that property type and recommends one. Copy the token and add it to your DNS settings or your site.
- Click Verify. If the token is not live yet, click Verify later and finish from the property selector.
Search Console starts collecting data as soon as a property is added, even before verification, and reports usually fill in within a few days. Next, submit your sitemap to Google. If you are launching a new site, verification is step 3 of getting your website on Google.
Domain or URL-prefix property: which should you verify?
Verify a Domain property if you can edit your domain's DNS: one property covers every subdomain (www, m, blog, shop) and both http and https. Choose a URL-prefix property if you cannot edit DNS, or if you want data for one section only, such as https://example.com/blog/.
| Domain property | URL-prefix property | |
|---|---|---|
| What you enter | The bare domain, such as example.com | The full address with its protocol, such as https://www.example.com/ |
| What it covers | Every subdomain, and both http and https | Only URLs that start with that exact address |
| How you verify | DNS record only (TXT or CNAME) | DNS record, HTML file, HTML tag, Google Analytics or Google Tag Manager |
| Needs access to DNS | Yes | No |
| Best for | Most sites: one property shows everything | Sites where you cannot edit DNS, or one section of a large site |
| Watch out for | A new DNS record can take up to two or three days to be seen | http and https, and www and non-www, are separate properties |
Three rules from Google's help on adding a property and verifying it save time:
- Verification flows down, not up. Verifying
example.comverifies all of its subdomains; verifyingm.example.comdoes not verifyexample.com. Properties you add under a verified parent are verified automatically. - DNS verification counts twice. Verify a URL-prefix property with the domain name provider method and you are verified for the matching Domain property as well.
- The type changes what you see, not how Google treats the site. Google says adding a property does not affect your website on Google Search. You can keep both types for the same site, and one account holds up to 1,000 properties.
Every Search Console verification method compared
Each method places a token that Google can check:
| Method | Property type | What you need | Choose it when |
|---|---|---|---|
| DNS record (TXT or CNAME) | Domain or URL-prefix | Access to your domain's DNS settings | You want a Domain property, or your site builder has no place for code |
| HTML file upload | URL-prefix | A way to upload a file to your site's root folder | You have FTP, a file manager or a hosting control panel |
| HTML tag | URL-prefix | A way to add a meta tag to your homepage's head section | Your CMS or site builder has a verification or header code field |
| Google Analytics | URL-prefix | The Analytics tag on your homepage and Edit permission on the Analytics property | Google Analytics already runs on the site |
| Google Tag Manager | URL-prefix | The container snippet on your site and Publish or Admin permission on the container | Tag Manager already runs on the site |
Blogger and Google Sites have their own rules: new Blogger blogs are added and verified automatically in their owner's Search Console (older blogs use the HTML tag), and a Google Site is verified with Google Analytics on its default address, or with the HTML tag on a custom domain.
How to verify a domain in Google Search Console (DNS verification)
To verify a domain, add one TXT record where your domain's DNS is managed (wherever your nameservers point), then click Verify. For a URL-prefix property, the same method is listed as Domain name provider.
- Add a Domain property. Search Console opens Verify domain ownership via DNS record.
- If your DNS provider is in the list, select it, click Start verification and sign in to the provider; Google says listed providers can often verify you directly. Otherwise keep Any DNS provider.
- Copy the TXT value. It starts with
google-site-verification=. - At your DNS provider, add a TXT record with the host set to
@(or left blank) and the copied value. Keep the default TTL. - Back in Search Console, click Verify.
Google says a manually added record can take up to two or three days to be served, so if Verify fails at once, wait a day and try again. Google's Admin Toolbox Dig shows whether your TXT record is visible yet. Most domains use TXT. Google's rule: use the CNAME record Search Console offers only if your domain already has a CNAME that points to a parent domain; otherwise, TXT.
Cloudflare
Select your account and domain, open DNS, then Records, and click Add record. Set Type to TXT and Name to @, paste the value into Content and click Save. These are the steps in Cloudflare's docs for Google's TXT verification records.
Namecheap
Open Domain List, click Manage next to the domain and go to Advanced DNS. Click Add new record, choose TXT Record, enter @ as the Host, paste the value and click Save all changes. Namecheap says a new record takes effect in about 30 minutes. This applies to BasicDNS, PremiumDNS and FreeDNS; with Namecheap web hosting DNS, add the record in cPanel.
How to verify with an HTML tag or HTML file
Choose HTML tag or HTML file when you verify a URL-prefix property, put the tag in your homepage's <head> or the file in your site's root folder, publish, and click Verify. Both need the homepage or the file to load without a login.
HTML tag: choose HTML tag and copy the whole tag, which looks like <meta name="google-site-verification" content="..." />. Paste it inside the <head> section of your homepage, or into your platform's verification field (steps below). Publish, view the logged-out page source, search for google-site-verification to confirm the tag is there, then click Verify. Google reads the tag only inside <head> and within the first 2MB of the page's HTML.
HTML file: choose HTML file, download it and upload it unchanged, name included, to your site's root folder. Open your address plus the file name in a private window and check that it loads directly, with no redirect: Google's steps say Search Console does not follow redirects when it looks for the file, and a redirect to another domain always fails. The free redirect checker shows every hop and the final status code of the file's URL. Then click Verify. Delete the file later and you lose verification.
How to verify with Google Analytics or Google Tag Manager
If the site already runs Google Analytics or Google Tag Manager, Search Console can use that code as your token, for URL-prefix properties:
- Google Analytics: your Google account needs Edit permission on the Analytics property, and the homepage, as a logged-out visitor sees it, must load the gtag.js (or older analytics.js) snippet in
<head>, unchanged. - Google Tag Manager: your account needs Publish or Admin permission on the container, and its
<noscript>part must come right after the opening<body>tag, with nothing but HTML comments in between.
Choose the method in Search Console and click Verify. The catch: the tracking code is now also your proof of ownership. If a redesign removes it, your verification goes with it, so add a second method under Settings, Ownership verification as a backup.
Where to find your Google Search Console verification code
You find the code in Search Console, on your property's verification screen. For a URL-prefix property, expand HTML tag under Other verification methods and copy the meta tag; for a Domain property, copy the TXT value shown in Verify domain ownership via DNS record. For a property you already have, open Settings, then Ownership verification, and pick the method there.
The code itself is the content value of the meta tag named google-site-verification, or the TXT value that starts with google-site-verification=. That shared name is what people mean by Google site verification. Wix wants the whole meta tag, WordPress.com accepts the tag or only the code, and when a field asks for the code alone (Rank Math's does), paste the part between the quotes after content=. To see the tokens you already use, open Settings, Users and permissions, click the menu next to your name and choose Ownership verification details.
Search Console verification on Wix, Squarespace, Shopify, Weebly and WordPress
Most site builders either connect Search Console for you or give you a field for the HTML tag. These steps come from each platform's own help pages, checked in November 2026.
Wix Search Console verification
You need an upgraded (Premium) site with a connected domain, published, with Let search engines index your site on and no password on the homepage. The quick route is the SEO Setup Checklist: complete Step 1 and click Connect to Google. Wix allows that once; after that, verify manually. The manual route: add a URL prefix property for your full https://www address and copy the HTML tag. In your Wix dashboard, open SEO & GEO, scroll to Tools and settings, select Site Verification, expand Google Search Console, paste the tag and click Save. Then click Verify in Search Console.
Squarespace
Open Analytics, click Search keywords, then Connect, sign in to Google and click Allow. Squarespace verifies your primary domain; data takes up to 72 hours. Trial sites cannot be verified, any site-wide or homepage password must come off, and after connecting a custom domain Squarespace suggests waiting 48 hours. There is no file upload method; use a TXT record instead.
Shopify
Turn off your online store's private mode while you verify; you can turn it back on afterward. Add a URL prefix property for https:// plus your domain and copy the HTML tag, angle brackets included. In Shopify admin, go to Online Store, open your theme's actions menu, click Edit code and open theme.liquid under Layout. Paste the tag on a blank line directly below the opening <head> tag, click Save, then click Verify. If it fails, Shopify says to wait 15 minutes and try again. With international domains, repeat this for each domain, one tag per line. For a domain bought from Shopify, add a TXT record under Settings, Domains: click the domain, then Manage in DNS settings and Add custom record. Changes can take up to 24 hours.
Weebly Search Console verification
On your own domain, verify a Domain property with a TXT record at your domain registrar, as in the DNS steps above. On a free weebly.com or square.site address, add a URL prefix property, expand HTML tag under Other verification methods and copy the code. In the Weebly editor, open Settings, then SEO, paste it into Header Code, then save, publish the site and click Verify in Search Console. If it fails, Weebly says to check that the site is published and try again.
WordPress
- Site Kit by Google (self-hosted): install and activate it from Plugins, Add New, then in Site Kit, Dashboard, click Sign In with Google and Verify ownership. Site Kit places the token for you and adds the site as a URL-prefix property if it is not in Search Console yet.
- Yoast SEO (self-hosted): in Yoast SEO, Settings, Site connections, paste the HTML tag under Google, click Save changes, then click Verify in Search Console.
- Rank Math (self-hosted): in Rank Math SEO, General Settings, Webmaster Tools, paste only the code from the tag into Google Search Console and click Save Changes, then click Verify in Search Console. If it fails, Rank Math says to clear your site's cache and try again.
- WordPress.com: under Jetpack, SEO, Settings, Site verification, paste the tag or the code into Google verification code; it saves when you click outside the field. Business and Commerce plans get a Verify with Google button instead. For a Domain property, add the TXT record under the domain's Settings, DNS records; WordPress.com says verification can take up to 72 hours.
On any other builder, put the HTML tag in its site verification or header code field, or verify a Domain property at your domain provider.
Why Search Console verification fails, and how to fix it
Verification fails when Google cannot find your exact token where it looks. Search Console names the reason; these are the common ones and their fixes:
| Error in Search Console | What it means | Fix |
|---|---|---|
| Your verification DNS TXT record was not found | Google does not see the record yet | Check that it is on the root domain (host @ or blank) at your nameservers' provider, wait a day and retry |
| Your verification record did not match | The record's value is not your token | Copy the value again, with no extra spaces or quotes |
| Your verification file was not found in the required location | The file is not at the root, or its URL returns an error | Upload it to the root folder and open it while logged out |
| Your verification file redirects to a disallowed location | The file's URL redirects to another domain | Serve it at its exact address with no redirect, or use the HTML tag |
| Meta tag not found/in the wrong location | No tag in the head section of the live homepage | Move it into the head section, publish, and clear any page or CDN cache |
| Your meta tag is incorrect | The page holds a different token | Copy the exact tag for this property and account |
| Insufficient permission | No Edit right in Analytics, or no Publish or Admin right in Tag Manager | Get the permission, or sign in with the account that has it |
| Your server returned an invalid response | Often a password in front of the site | Remove the password while you verify |
Two causes come without a clear message:
- You verified a different address. A URL-prefix property for
https://example.com/does not coverhttps://www.example.com/: verification succeeds, but the reports stay empty. Add the address your site really serves, or a Domain property. - Bot protection blocks the check. It comes from Google Site Verifier, with
Google-Site-Verificationin its user agent. Let it through for good, since Search Console checks the token again from time to time.
What happens if you remove the verification token?
You lose verification. Search Console checks periodically that your token is still there. If it cannot confirm it, you are notified, and if you do not fix it, your permissions expire after a grace period. When the last verified owner loses verification, everyone else on the property loses access too, although Google keeps collecting data until someone verifies again. Theme switches, site rebuilds and DNS moves can all drop a token, so keep a second method as a backup.
It works the other way too. To shut out a previous owner, Google says to remove them in Users and permissions and delete their token from the site or DNS, or they can verify again. Unused ownership tokens on the same page shows leftovers.
Owners and users: who needs to verify?
Only owners need a token. A verified owner placed their own token; a delegated owner was added by an owner and has the same rights without one. Several people can verify the same property, as long as nobody overwrites another owner's token. Everyone else is a user: an owner opens Settings, Users and permissions, clicks Add user and picks Full or Restricted. Full users see all data and get the full URL Inspection tool, including Request indexing and its daily quota; restricted users mostly view data. A property can have up to 100 users who are not owners. If you work on a client's site, ask to be added as a full user or a delegated owner instead of sharing the client's password.
What we found across 871 verified sites
We looked at the 871 verified sites connected to IndexMachine by accounts opened between June 2 and November 11, 2026, each with at least one sitemap URL and its index status from Search Console: 510,251 sitemap URLs in all, as of November 11, 2026. A site counts as covered by a Domain property when the same account had a Domain property for its domain or a parent domain; the rest had only a URL-prefix property. Thirteen sites were connected by two accounts and count once in each. Aggregate counts only, with no site or account named.
| Sites in the account | Sites | Covered by a Domain property | With sitemap URLs Google has not indexed |
|---|---|---|---|
| 1 to 5 | 151 | 126 (83.4%) | 142 (94.0%) |
| 6 to 20 | 274 | 166 (60.6%) | 254 (92.7%) |
| 21 or more | 446 | 46 (10.3%) | 422 (94.6%) |
| All accounts | 871 | 338 (38.8%) | 818 (93.9%) |
What stands out:
- Accounts with a few sites mostly use a Domain property. In accounts with 1 to 5 sites, 83.4% of the sites were covered by one.
- Large portfolios mostly do not. In accounts with 21 or more sites, only 10.3% were, which is why sites with only a URL-prefix property are the majority when you count sites (61.2%). If you run many sites this way, make sure each property matches the address the site really serves.
- Verified does not mean indexed. In every group, 92.7% to 94.6% of the sites had at least one sitemap URL that Google had not indexed, and the median site had 33.3% of its sitemap URLs indexed. On most of these sites IndexMachine had not requested any page yet, so these numbers mostly show where sites stand before indexing is turned on.
After verification: get your pages on Google
Verification gets you Google's data, not indexed pages. Search Console shows which pages are missing and why, and asking Google to crawl them is one URL at a time in URL Inspection, with a daily quota; our URL Inspection tool guide walks through that screen.
A verified site is also all IndexMachine needs. Sign in with Google and every property you verified comes in at once, each with the pages from its sitemap and a list of the ones Google has not indexed yet. Turn indexing on and the IndexMachine Chrome extension presses the same Request indexing button you would press by hand, every day. That is Google's own Request Indexing in your Search Console, on autopilot, and it spends your full daily Google quota on every site on pages Google has not indexed. Pages Google already shows as indexed are skipped, so no quota is wasted. Bing, Yandex, Seznam and Naver get unlimited IndexNow, each requested page is tracked until it is on Google, and 404 alerts and a weekly email report tell you what changed. Of 1,841 pages requested, 1,418 (77%) were on Google, typically in about 3 days by our first check. The free account shows you the gap; pay once for lifetime access or subscribe to turn indexing on.
Verified your site? Now get its pages on Google
One Google sign-in brings every property you have verified into IndexMachine, along with the pages Google has not indexed yet. When you are ready, switch on Google's own Request Indexing in your Search Console, on autopilot, and unlimited IndexNow for Bing and the rest.
FAQs
How long does Google Search Console verification take?
The check takes seconds once the token is live. An HTML tag, HTML file, Analytics or Tag Manager token is live once your published page or file serves it; if a cache plugin or CDN sits in front of the site, clear the cache before you click Verify. A DNS record can take longer: Google says a manually added record can take up to two or three days to be served, though many providers are faster. Reports then fill in within a few days.
Can I verify Google Search Console without DNS access?
Yes. Add a URL-prefix property and verify it with an HTML tag, an HTML file, Google Analytics or Google Tag Manager. Only a Domain property requires a DNS record.
Why won't Google Search Console verify my site?
Usually because Google cannot find your exact token where it looks. The DNS record is not served yet (that can take up to two or three days), the tag is missing from the live homepage's <head> (a cached copy is a common cause), the page holds another account's token, the file redirects, or a password or bot protection blocks Google Site Verifier. Search Console names the reason when verification fails, and the error table above gives the fix for each one.
Do I need to verify www and non-www separately?
With URL-prefix properties, yes: https://example.com/ and https://www.example.com/ are separate properties, and so are their http versions. A Domain property for example.com covers all of them and every subdomain with one DNS record, and URL-prefix properties you add under it later are verified automatically.
What is the Google site verification TXT record in my DNS?
It is a Google site verification token: a record someone added to prove to Google that they own the domain. Usually that was for Search Console, but Google Workspace uses the same google-site-verification= format, and Google says one token can be reused across services such as Search Console, Merchant Center and Google Workspace. If it is a Search Console token, deleting it removes that owner's verification after a grace period. Check who relies on it before you remove it.