How to Verify Your Site in Google Search Console: DNS, HTML File, Meta Tag and Every Other Method

What Is Search Console Ownership Verification?

Ownership verification is the process of proving to Google Search Console that you control a website, by placing a token unique to your Google account where only a site owner could put it.

Google defines it as “proving to Search Console that you own a specific website” and says a verified owner “has the highest degree of permissions in Search Console” (Verify your site ownership). The check exists because owners see sensitive Search data and can take actions that affect how the site appears on Google. Each token is tied to one person: Google says the HTML file and meta tag are “unique to you” and associated with your Google account. Google uses a user agent called Google Site Verifier to perform the check.

Verification does not affect rankings. Google says adding a property “does not affect your website or platform property on Google Search, it only enables you to track your site's performance on Google” (Add a website property). Once verified, you can use the Sitemaps report and URL Inspection, which are covered in how to submit a sitemap to Google and Bing and how to check if a page is indexed by Google.

How to Verify a Site in Search Console at a Glance

Time: minutes for file, tag, Analytics or Tag Manager methods; DNS can take up to two or three days to propagate per Google (the rest is our estimate). Tools: a Google account, a web browser, and access to your DNS provider, site files, CMS, Google Analytics or Google Tag Manager. Cost: none beyond your time. Skill level: beginner for file, tag and analytics methods; intermediate for DNS.

What You Need Before Starting

• A Google account you intend to keep. Tokens are tied to the account that generated them, so use a company-controlled account rather than a personal one that may leave with an employee.
• For a Domain property: a login to the company you bought the domain from or that hosts your DNS (Google calls this your “domain name provider”).
• For a URL-prefix property, one of: the ability to upload a file to the site root, the ability to edit the homepage <head>, edit rights in the site's Google Analytics account, or Publish or Admin permission in its Google Tag Manager container.
• A homepage that loads for non-logged-in visitors. Google says the tag, Analytics and Tag Manager methods require a homepage that does not require authentication.
• If your site runs on a hosting platform such as WordPress, Wix, Shopify or Squarespace, its help pages. Google says to check them first, because the platform may offer a built-in setting or plugin; Google names Site Kit for WordPress as “the only plugin that is officially sponsored by Google” (Verify your site ownership).

Step 1: Choose a Domain Property or a URL-Prefix Property

Decide which property type to create before you start, because it determines which verification methods are available.

Why it matters: Google's example is that the URL-prefix property http://example.com/ does not include https://example.com/dresses/1234 or http://www.example.com/dresses/1234, while the Domain property example.com includes both (Add a website property). If you enter www.example.com as a Domain property, Google creates it as example.com and includes both versions.

Expected result: one chosen property type. How to verify the choice: check the address bar on your live homepage; a URL-prefix property must match its protocol and hostname exactly. Common mistake: creating http://example.com/ when the site serves https://www.example.com/. Google lists “you specified http instead of https” as a reason a property shows no data. If you can edit DNS, a Domain property avoids the problem entirely; you can add URL-prefix properties later for sections you want to report on separately.

Step 2: Add the Property in Search Console

Open the property selector dropdown on any Search Console page and select + Add property, then choose the property type and enter the domain or URL prefix (Add a website property).

What happens next: Search Console asks you to choose a verification method and shows the steps for it. Google says the verification page “will list which methods are available and recommended for your site”. You can finish immediately and click Verify, or click Verify later to save your place and come back by selecting the unverified property in the property selector.

Limits: Google allows up to 1,000 properties per Search Console account. If someone else already owns the property and you cannot verify it yourself, Google says to ask a current owner to grant you access instead (Step 6).

Expected result: the verification dialog for your property. How to verify: the property appears in the selector, marked as unverified until you finish. Common mistake: assuming data will be missing for the days before verification. Google says data is collected for a property “as soon as anyone adds it in Search Console, even before verification occurs”, though it takes a few days for data to appear.

Step 3: Verify a Domain Property With a DNS TXT or CNAME Record

Add the DNS record Search Console gives you at your domain name provider, then click Verify. This is the only way to verify a Domain property, unless the site is on a Google product such as Blogger or Google Sites (Add a website property).

Process (Verify your site ownership, “Domain name provider”):

1. When you create a Domain property, the Domain name provider method is chosen automatically.
2. If Search Console lists your provider, choose it and click Start verification. You log in to the provider and, Google says, “verification should occur immediately.”
3. If the provider shown is not yours, choose Any DNS provider and add the record by hand.
4. For a manual record, pick TXT or CNAME under Select record type. Google says to use TXT in the most common case, and CNAME only if a lookup in the Google Admin Toolbox finds an existing CNAME whose target is a parent domain of yours.
5. TXT: leave the host or name field blank or set it to @ (as your provider documents), and paste the string into the value field. It looks like google-site-verification=….
6. CNAME: Search Console gives you two values, a name (or label or host) and a destination (or target) containing dv.googlehosted.com. Enter both and keep the default TTL.
7. Click Verify.

Type:  TXT
Host:  @            (or blank, depending on your provider)
Value: google-site-verification=YOUR_TOKEN_FROM_SEARCH_CONSOLE

Expected result: verification succeeds. Google warns that a manually added record can take “up to two or three days” to be served; if verification fails, wait a day or two and try again. How to verify: look up your domain's TXT or CNAME records in the Google Admin Toolbox, as Google suggests, and check that the record matches exactly. Coverage: verifying a root domain verifies all its subdomains, but verifying m.example.com does not verify example.com. Using DNS on a URL-prefix property also auto-verifies you for the Domain property. Common mistake: deleting the record after success. Google says, “To stay verified, don't remove the DNS record from your provider, even after verification succeeds.”

Step 4: Or Verify a URL-Prefix Property With an HTML File or HTML Tag

Upload the HTML file or paste the meta tag that Search Console generates for you, confirm it is live, then click Verify. Neither method works for Domain properties (Verify your site ownership).

HTML file upload

1. Choose HTML file upload and download the file. Do not rename it or change its contents (Google allows only added newlines at the end).
2. Upload it so it loads at the address Search Console shows, usually the root of the property, for example https://example.com/ plus the file name.
3. Open that address in an incognito window to confirm it loads without a login, then click Verify.

Google's help is not consistent on redirects for this method: its steps say Search Console “does not follow redirects when looking for this file”, while its troubleshooting notes say it follows redirects within the same domain (for example http to https, or non-www to www) but not to another domain. The safest setup is a file that loads at the exact address shown, with no redirect. If your site redirects everything to a different domain, Google recommends the HTML tag method.

HTML tag

1. Choose HTML tag and copy the meta tag.
2. Paste it inside the <head> of the homepage that non-logged-in visitors see, then publish.
3. View the live page source, search for google-site-verification, then click Verify.

<head>
  <title>Example.com homepage</title>
  <meta name="google-site-verification" content="YOUR_TOKEN" />
</head>

The tag must appear within the first 2MB of the file. For tag-based methods, Google checks the page a non-logged-in visitor is redirected to: if https://example.com redirects to https://example.com/home, Google looks for the tag on /home.

Expected result: verification succeeds. How to verify: the file loads in an incognito window, or the tag appears in the live page source. Common mistake: editing a local or staging copy. Google notes that with a web editor you must change the HTML of the live page, and that the tag must sit in <head>, not <body>.

Step 5: Or Verify With Google Analytics or Google Tag Manager

Choose Google Analytics or Google Tag Manager on the verification page and click Verify, if your homepage already carries a snippet from an account you manage. Nothing on the site needs to change.

• Google Analytics: you need “edit” rights in the Analytics account, the same Google account for both products, and the gtag.js or analytics.js snippet in the homepage <head>, unmodified. Google says that in Google Analytics 4 the verification code is associated with a data stream. If you also want to see visits from AI assistants in the same account, see how to track AI referral traffic in GA4.
• Google Tag Manager: you need Publish or Admin permission for the container, the same Google account for both products, and the <noscript> part of the container code placed “immediately after the opening <body> tag”, with nothing but HTML comments between them.
• Google Sites and Blogger: Google says new Blogger blogs are added and verified automatically, while older blogs use the HTML tag method. A new-style Google Site without a custom domain uses the Google Analytics method; classic Sites or a Site with a custom domain use the HTML tag.

Expected result: verification succeeds without a site edit. How to verify: Settings > Ownership verification lists the method used. Common mistake: verifying through Google Analytics with an account that has view-only access, or while a Tag Manager snippet (not an Analytics snippet) is the only tag on the page. Google lists both as specific errors.

Step 6: Add a Backup Method, Then Add Other Owners and Users

Add a second verification method and grant access to colleagues, so the property does not depend on one token or one person.

Backup method: Google recommends adding more than one method “in case one of your existing verification methods fails”, giving the example of a template change that drops an Analytics tag. Add it under Settings > Ownership verification.

Roles (Google, Managing owners, users, and permissions):

To add someone: Settings > Users and permissions > Add user, enter their Google Account email and choose a permission. Email groups cannot be added. To make someone a verified owner: have them start verification to generate their own token, place it on the site (for example, upload their HTML file), then have them click Verify. Multiple verified owners: Google allows several people to verify with the same or different methods, but warns not to overwrite each other's tokens, so add a second meta tag or DNS record rather than replacing the first. Limits: up to 100 non-owners per property, and delegated owners only until the property has 500 verified plus delegated owners; verified owners have no maximum.

Expected result: at least two owners and two verification methods. How to verify: Users and permissions shows “Owner” plus “Verified” for verified owners, and “Owner” alone for delegated owners. Common mistake: making an agency the only verified owner. If it leaves, someone in your organisation must verify again to regain access.

Step 7: Import the Verified Site Into Bing Webmaster Tools

Sign in to Bing Webmaster Tools and choose the option to import your sites from Google Search Console. This reuses the verification you just completed (Bing, Add and verify site).

How Bing describes the import: you give Bing Webmaster Tools permission to access your Search Console account; it lists your verified sites “along with the Sitemaps and their corresponding role in each site”; you select sites and click Import; and the selected sites are added and “get automatically verified”. Bing revalidates ownership through Search Console periodically, importing any new sitemaps it finds. Up to 100 sites can be imported at once, with a limit of 1,000 sites per Bing account. You can stop the connection with the Disconnect option in Bing's Profile section.

Manual alternative: add the site by URL and verify with a BingSiteAuth.xml file in the site root, a meta tag in the homepage <head>, a CNAME record in DNS, or automatic DNS verification where your DNS provider supports the Domain Connect standard.

Expected result: the site appears in Bing Webmaster Tools without a verification prompt. Bing says it “usually takes 48 hours” to generate data for a new site. How to verify: select the site in Bing's site list. Common mistake: expecting every Search Console property to appear. Bing says sites already in your Bing account and URLs it normalises together can reduce the number shown. For how the two tools differ after setup, see Google Search Console vs Bing Webmaster Tools.

How to Verify It Worked

• Search Console: the property opens without a verification prompt, and Settings shows an Ownership verification row; owners can click it to see the method used (Managing owners, users, and permissions).
• Your role: Users and permissions lists you as “Owner” and “Verified”.
• Token still live: the DNS record appears in a DNS lookup, the HTML file loads in an incognito window, or the meta tag appears in the live page source.
• Data: reports begin filling within a few days. Google says if there is still no data several days after verification, the site may not have been seen in Google Search or the property URL may be wrong.
• Bing: the imported site is listed in Bing Webmaster Tools with no verification step pending.

How to Choose a Verification Method

What to Do If You Lose Verification

Restore the token or add a new one, because Search Console keeps checking. Google says it “periodically checks if your verification token is still present and valid”; if it cannot confirm it, you are notified, and “your permissions on that property will expire after a certain grace period” (Verify your site ownership). Google does not publish the length of that grace period.

• A redesign removed your tag or file: put the same token back, or verify again with another method.
• The only verified owner left: Google says to verify ownership yourself to keep or regain access. If all verified owners lose access, all users lose access to the property. Data continues to be collected and becomes visible again once someone verifies.
• You took over the site from a previous owner: after verifying, remove the previous owner in Users and permissions, then delete their tokens. Google says removed owners can re-verify for as long as their token stays on the site; the Unused ownership tokens list shows which to remove.
• You see an owner you do not recognise: Google says “you might have been hacked” and that a hacker can probably re-add a removed token, so secure the site first.
• History: Users and permissions > Ownership history lists owners added and removed, verification attempts, and removed tokens.

Before deleting any token, check where else it is used. Google warns that the same token can verify ownership for other services such as Merchant Center or Google Workspace.

Common Problems and Fixes

Error wording in the first column is quoted from Google's Verify your site ownership and Managing owners, users, and permissions pages, read October 7, 2026.

What Not to Do

• Do not remove the token after verifying. Consequence: access ends after the grace period. Correction: leave the DNS record, file or tag in place permanently.
• Do not overwrite another owner's token. Consequence: they lose verification. Correction: add your own TXT record or meta tag alongside theirs.
• Do not verify with a personal account only. Consequence: access walks out with the person. Correction: verify with a company-controlled account and add delegated owners.
• Do not create only an http:// or non-www URL-prefix property for an https://www site. Consequence: empty or partial reports. Correction: use a Domain property, or match the live prefix exactly.
• Do not remove a former owner without deleting their tokens. Consequence: Google says they can re-verify. Correction: check Unused ownership tokens and remove each one.
• Do not treat verification as an SEO action. Consequence: misplaced expectations. Correction: verification gives you data and tools; it does not change how Google ranks the site.

Frequently Asked Questions

Sources and Methodology

This guide is built from Google Search Console Help and Bing Webmaster Tools Help pages. The Google pages were read on October 7, 2026; the Bing page, which loads with JavaScript, was read from a browser copy taken on October 6, 2026. Interface labels in bold are quoted from those pages; where the documentation did not confirm a label, we describe the control instead. We did not verify a property for this guide and did not test how long DNS records take to propagate. The time estimates outside Google's stated DNS delay are ours. Google does not publish the length of the grace period after verification fails.

1. official Google Search Console Help, Verify your site ownership. Methods, requirements, errors, grace period. Read October 7, 2026.
2. official Google Search Console Help, Add a website or platform property to Search Console. Property types, syntax, 1,000-property limit. Read October 7, 2026.
3. official Google Search Console Help, Managing owners, users, and permissions. Roles, limits, unused tokens, ownership history. Read October 7, 2026.
4. official Bing Webmaster Tools Help, Add and Verify site. Import from Search Console, manual methods. Read October 6, 2026.