Verify your site ownership

What is verification?

Verification is the procedure of proving that you ain the property that you merits to ain. Search Console needs to verify buying because verified owners have access to sensitive Google Search information for a site, and can affect a site'south presence and behavior on Google Search and other Google backdrop. A verified possessor tin can grant total or view access to other people.

VERIFY YOUR Holding

Verify a website property

  1. Either add a new property or choose an unverified property from your belongings selector.
  2. Choose one of the verification methods listed beneath and follow the instructions. The verification page will list which methods are available and recommended for your site.

Using multiple verification methods

You can add together multiple verification methods in your property'south verification settings folio. Y'all might want to add more one verification method in case ane of your existing verification methods fails (for case, if you verified using a Google Analytics tracking code, and someone changes a template on your website that omits the tag).

To add an additional verification method, visit the Settings folio for the holding and click Buying verification

Multiple people tin can verify ownership of the aforementioned website property, using the same or unlike verification methods. If y'all use the same verification method, just exist certain that y'all don't overwrite the verification tokens of whatever other owners.

Verifying child properties

Once you lot take verified a property, yous can create and verify kid properties very easily with the same verification method with little additional work. That is, if you have verified ownership of example.com using the HTML file upload method, any child properties that you create volition exist auto-verified using the same method.

How long does verification concluding?

Verification lasts as long as Search Panel can confirm the presence and validity of your verification token. Search Console periodically checks if your verification token is still nowadays and valid (for case, by checking if your HTML verification tag is notwithstanding present). If verification can no longer be confirmed, y'all will be notified. If the issue is not stock-still, your permissions on that property will expire subsequently a certain grace period.

If all verified owners lose admission to a property, all users with full view permissions volition then lose access to the Search Console belongings.

The user amanuensis that performs HTML tag verification has the user agent token Google-Site-Verification and the full user agent cord Mozilla/five.0 (compatible; Google-Site-Verification/1.0)

When will I start to see data?

Data is collected for a holding every bit shortly as anyone adds it in Search Console, fifty-fifty before verification occurs.

We lost our only verified site possessor!

If the just verified owner of your site leaves your team, you should verify buying to maintain (or regain) access to the holding.

If you lot are taking over a site from another owner, after you verify ownership yous can unverify previous owners by removing their verification token (for example, removing the HTML tag from the site, for HTML-tag-verified owners). See Add together or remove owners for more data.

Choosing a verification method

Search Panel supports several different verification methods. See the tabular array below to help cull a method that works best for y'all.

Method Notes
HTML file upload Relatively simple, but requires the power to upload a file and publish it on your site at a specific URL. Might not be possible on a site hosting platform.
HTML tag Relatively simple, only requires the ability to edit the HTML source code of your site'southward homepage. Might not exist possible on a site hosting platform.
Google Analytics tracking code Simple, if the page already has a Google Analytics tracking lawmaking for a Google Analytics account that yous can access. If the page does not have a tracking code, you lot must must add together one (which may require creating a Google Analytics account if y'all don't already have one).
Google Tag Director Unproblematic if the page already has a Google Tag Manager snippet for a Google Tag Managing director account that you can admission. If the page does not have a snippet, y'all must must add ane (which may crave creating a Tag Manager account if you don't already have one).
Google Sites, Blogger, or Domains account Employ the recommended method for each platform.
Domain name provider More circuitous, only is the only manner to verify a Domain property. If your domain provider is listed in the verification wizard, then this is a simple procedure. Domain backdrop are useful because they include data for all protocol (http/https) and subdomain variations of your belongings.

Verification method details

Sites that use a website hosting platform

If y'all use a website hosting platform like WordPress, Wix, or SquareSpace, you might exist express in which verification methods are available to you. Or, conversely, your platform might provide a special plugin or setting to verify your property on Search Panel.

If you lot're using a CMS, endeavour these steps earlier trying ane of the verification methods listed on this page:

  1. Search your site host's documentation for Search Panel verification information. For example: "Wix Search Console verification" or "Weebly Search Console verification".
  2. Search for plugins on your platform that can handle verification for you. For case, Site Kit for WordPress can handle verification for you, and also provide simplified views of your Search Console data. Note that Site Kit is the only plugin that is officially sponsored by Google, then do a little enquiry on any plugin earlier you install it.

HTML file upload

HTML file upload for site buying verification - Google Search Console Training

You can verify ownership of a site past uploading a special HTML file to a specific location on your site. This file is tied to a specific user. Follow the instructions on the verification details page. Removing this verification file from your site will crusade you to lose verification for the site.

⚠️ Requirements

  • The file cannot require hallmark. The directory where you lot upload your HTML file must be available to non-logged-in users. You tin test this by trying to visit your file in an incognito window in your browser.
  • You must be able to upload a file to the root directory of your website, where it volition be bachelor to web browsers. If you do non have permissions to do this, effort another verification method. If y'all are using a website hosting platform, you might need to search your service's aid pages to encounter if this is possible.
  • HTML file upload can be used for URL-prefix properties, but not Domain properties.

Steps

To verify ownership using an HTML file:

  1. If you are using a website hosting platform, search your service'southward help pages for custom instructions to verify your site on Search Console. If you lot don't observe any information, then go on on to the next steps.
  2. Read the requirements for this verification technique.
  3. Choose the HTML file upload method on the Ownership verification page for your holding.
  4. Download the provided verification file. This file is unique to you; it cannot exist used to identify anyone else, and is associated with your Gmail account.
  5. Upload the verification file to your website so that it will be exposed in the location that was specified in the verification details page. This is typically the root directory for your holding. (That is, if you lot defined your property as https://example.com, and the file provided is named 1234.txt, and so the file should be saved and browsable at https://example.com/1234.txt.) Search Console does not follow redirects when looking for this file. Y'all can add together newlines at the end of the file body, if required, just practise not otherwise modify the file proper noun or content.
  6. Confirm that you can see the file past visiting information technology in your browser in the location specified by the Search Console verification wizard. If the file isn't available to your browser at that URL, Google won't exist able to find for verification purposes.TIP: Utilize an incognito window in your browser to confirm that you don't demand to log in to access it.
  7. Complete verification by clicking Verify in the verification details page.
  8. If verification fails, see Potential errors beneath to troubleshoot the issue.

Potential errors

The post-obit errors can occur with HTML file upload verification:

  • Your verification file was not found.
    Delight download the verification file provided on the Verification page of Search Console, and upload it to the specified location without any modifications. If the file name or content does not match the HTML file provided, nosotros won't be able to verify your site ownership.
  • Your verification file has the wrong content.
    Search Console checks to come across if your verification file has the same filename and content equally the file provided on the Verification page. If the file name or content does not match the HTML file provided, we won't be able to verify your site ownership. Delight download the verification file provided on the Verification page of Search Console, and upload it to the specified location without any modifications.
  • Hacked verification file.
    Your verification endeavor failed in a style that indicates that your site might accept been hacked. Learn more than virtually detecting and fixing hacked sites.
  • Your verification file redirects to a disallowed location.
    Google will not follow redirects to another domain for verification files. Redirects within a single site—for case, from http://example.com/ to http://www.example.com/—are allowed. If your site redirects all traffic to some other site, nosotros recommend using HTML tag verification instead.
  • Additional mutual verification problems are listed below.

HTML tag

HTML tag for site buying verification - Google Search Panel Grooming

You can verify your ownership of a site by adding a <meta> tag to the HTML of a specified page. We'll verify that the meta tag exists in the correct location. If we can't find the tag, we'll give you information about the fault nosotros encountered. This tag is tied to a specific user. Search Console will periodically check for the presence of this tag.

⚠️ Requirements

  • Your homepage cannot require authentication. The site homepage must be available to non-logged-in users.
  • You must exist able to edit the HTML source code of the site's homepage directly. Specifically, you lot must be able to insert a tag into the <head> tag on your homepage. If you lot practise not have permissions to do this, attempt another verification method. If you are using a website hosting platform, yous might need to search your service'south help pages to see if this is possible.
  • Tin be used for URL-prefix properties, but non Domain properties.

Steps

To verify ownership using an HTML tag:

  1. If you are using a website hosting platform, search your service'south help pages for custom instructions to verify your site on Search Console. If you don't find any information, then proceed on to the next steps.
  2. Read the requirements for this verification technique.
  3. Choose the HTML tag method on the Ownership verification page for your belongings.
  4. Copy the tag from the Search Console verification wizard into the <head> section in the HTML of your site's non-logged-in abode page (see note). Example:
    <head>
    <title>Case.com homepage</championship>
    <meta name="google-site-verification" content="......." />
    </head>
    This tag is unique to you lot; it cannot be used to identify anyone else, and is associated with your Gmail account.
  5. Save your folio. Confirm that the tag is present in your live page by visiting the page and looking for the tag in the page source lawmaking. (PressCommand + F then search for "google-site-verification" in the folio source to find the tag.)
  6. Complete verification past clicking Verify in the verification details page.
  7. If verification fails, run into Potential errors below to troubleshoot the consequence.

Potential errors

The following verification errors can occur with HTML tag verification:

  • Meta tag not found/in the wrong location. The verification meta tag must be within the <head> section of the folio. If you see these errors, check the following:

    • Is the meta tag on the correct page? We look for it on your site's domicile page. This is the page that your server returns when someone requests your site (such every bit http://www.example.com/). This page is often named alphabetize.html or alphabetize.htm, but could be named differently, depending on your server'south configuration.

    • Is the meta tag in the correct place on the folio? We look for it in the page'south <head> department. An example of right placement is shown here: 
                                  <html>   <head>     <title>Your Page Title</title>     <meta name="google-site-verification" content="your verification string">   </caput> <torso> ...
    • If y'all're using a web editor or a WYSIWYG editor to edit your folio, make sure you lot're editing the HTML of the live folio, not just the local copy on your computer.
  • Your meta tag is wrong.
    We found the verification meta tag, merely the contents were wrong. To avoid errors, copy and paste the meta tag provided on the Verification page of Search Console. If another user'due south verification tag was already present in the page, you might get this error; confirm that the exact tag given to you in the Search Console verification wizard is present in the page HTML.
  • Additional mutual verification problems are listed below.

Domain proper noun provider

DNS tape for site buying verification - Google Search Console Training

Domain verification is required to verify a Domain property, but can also be used to verify a URL-prefix holding. This verification method involves submitting a tape into your domain proper name provider's record listing. This method may require you to be comfortable with a little bit of technical knowledge.

Yous can verify ownership of subdomains or root domains. Verifying ownership of a root domain verifies ownership of all subdomains, but verifying ownership of a subdomain does not verify ownership of a parent domain. For example: verifying ownership of m.example.com also verifies ownership of pets.m.example.com, but does not verify ownership of example.com.

⚠️ Requirements

  • You must accept a custom domain name, or control your domain name.
  • You must exist able to log into your domain proper noun provider.

Steps

To verify buying via your domain name provider (the company that you purchased your domain name from):

  1. If yous are using a website hosting platform, search your service's help pages for any custom instructions on verifying your site on Search Console. (Tips for finding your DNS provider, if you don't know who it is.) If you don't notice a custom solution on your provider's folio, then continue on to the next steps.
  2. Choose the Domain name provider method on the Ownership verification page for your property in Search Console. (This volition exist chosen automatically when you create a Domain property.)
  3. Run into if your Domain proper name provider is listed in the provider names dropdown list:
    1. If it is listed, choose your provider and click Start verification and follow the instructions provided in the dialog box. You lot will exist required to log in to your domain provider, after which verification should occur immediately.
    2. If it is not listed, cull Whatever DNS provider and follow the manual domain proper noun provider instructions beneath.

      Manual domain name provider instructions

      If your domain proper name provider is not listed in the Domain name verification dialog, you will need to manually add a DNS record. This DNS tape is a name/value pair provided by Search Console. Let'south become started:

      Decide which DNS record format to use. You must use either a TXT record or a CNAME tape, depending on how your site is configured. To decide which format y'all must use:

      1. Open up the Google Admin Toolboxin the CNAME tab
      2. Enter your holding's domain name. This is the part between "https://" and the path: For the property "https://world wide web.example.com/" the domain proper name would exist "world wide web.example.com".
      3. Look at the output:
        • [Most common example]If you run across " Tape not plant!" then follow the TXT record instructions.
        • If a CNAME record appears, and theTarget value is a parent domain of the domain that you entered, then you should follow the CNAME record instructions.
          Site with a CNAME record

      TXT DNS record instructions

      1. Generate a unique TXT verification record: When asked to verify your property in Search Console, cull the Domain name provider method and Search Console will give y'all a cord value TXT record to use in the adjacent stride.
      2. Add your DNS record to your domain provider:Add the TXT tape that Search Console gave you in the previous footstep to your domain provider's records by post-obit these steps:
        1. Notice the Google Workspace documentation for your provider.
        2. Ignore Google Workspace footstep 1 (Become your unique verification record) because y'all already generated your TXT tape in Search Console.
        3. Sign in to your domain host (typicallyGoogle Workspace Step 2 ).
        4. Add together your Search Console TXT tape to your domain'southward DNS records (typically Google Workspace Pace 3):
          • For theHost/Proper noun property,either exit this blank, or set up as "@", equally described in the documentation for your DNS provider.
          • For the Value holding, provide the Search Panel TXT record string that yous generated earlier.
        5. Ignore Google Workspace step 4 (the verification footstep) and continue with step 4 beneath.

      CNAME DNS tape instructions

      1. Generate a unique CNAME verification tape
        1. Open Webmaster Central. Don't use the TXT record from Search Console. You'll need to utilise Webmaster Central to generate a DNS record.
          • If your belongings is in the list on Webmaster Central:
            1. Select the property.
            2. ClickVerify using a unlike method
          • If the property is non in the list on Webmaster Central:
            1. Click Add a property in Webmaster Central, above the belongings list.
            2. Enter your blank host name (that is, example.com, non http://example.com).
            3. Click Go along.
            4. Select Alternate methods
        2. SelectDomain name provider.
        3. Choose your provider from the listing, or select Other.
        4. Click Add together a CNAME record to generate your DNS CNAME record.
      2. Add the DNS record to your domain provider:
        1. Find the Google Workspace documentation for your provider
        2. Ignore Google Workspace footstep one (Get your unique verification tape) because you already generated your CNAME record in Search Panel.
        3. Sign in to your domain host (typicallyGoogle Workspace Step 2 ).
        4. Add your CNAME verification record to your domain'south DNS records (typically Google Workspace Pace 3)using the tape you got from Webmaster Central. Provide both the record proper name and record value in the appropriate fields on your DNS provider's site. You tin use the default TTL value suggested by your provider.
        5. Ignore Google Workspace step 4 (the verification stride) and go along with footstep 4 below.
  4. Complete your ownership verification by clicking Verify in the Search Panel verification details page. Of import: For manually installed records, it can take upward to two or iii days for your provider to start serving the record. If you have followed the Manual domain proper noun provider instructions higher up and verification fails, wait a day or ii and try over again. See the Potential errors section for troubleshooting, or to acquire how to see whether your domain proper noun provider is serving your record yet.

Important: To stay verified, don't remove the DNS record from your provider, even after verification succeeds.

Troubleshooting and potential errors

To see which records are served by your domain proper name provider:

  1. Visit the Google Admin Toolbox
  2. Type your domain name into the box at the top, without the protocol or any slashes (that is, enter instance.com, not https://example.com).
  3. Click either TXT or CNAME, depending on what record type yous are using for verification. (Most sites use TXT records for domain verification.)
  4. All DNS records of the selected type constitute on your provider volition be shown at the lesser with a label describing the tape blazon (typically, either CNAME or TXT).
  5. Wait in the list of records for the DNS tape issued to you past Search Console.
    • For TXT records, a Search Console verification record looks something like google-site-verification=<<some number>> .
    • For CNAME records, the verification tape is a name/value pair where the name includes your holding domain, and the value includes dv.googlehosted.com.
    Your record should match exactly the verification record values given to you lot by Search Console. (You tin can wait up your Search Console DNS record values past following the transmission verification steps again to the step where you generate a verification record.)
  6. If you don't see your credentials listed, wait a day or two, and then try again.

To see your DNS record after you've verified your holding using the DNS method:

  1. Open Webmaster Central
  2. Click your property proper name in the listing of properties to encounter a list of verification methods for the holding.
  3. Next to either DNS TXT record  or DNS CNAME record, click Details to encounter your tape value.
  4. If you similar, y'all tin can besides see all records being served by your domain name provider using theGoogle Admin Toolboxas described above.

The post-obit verification errors can occur with DNS record verification:

  • Your verification DNS TXT record was not found
    Your verification TXT tape was non constitute. It tin can take a few minutes or even days later on posting the tape for it to exist visible to Google; wait a day or two so attempt once more.
  • Your verification record did non friction match
    No verification records on your DNS provider matched the value given to you past Search Panel. Be sure to use the record provided by the verification page. For a TXT record, you lot should leave the name/host field blank and utilise your TXT string in the DNS record'due south value field. For a CNAME tape, you are given a name/value pair to use in your DNS record'south name/value fields.
  • Additional common verification problems are listed below.

Google Analytics tracking code

Google Analytics for site buying verification - Google Search Panel Training

If you use Google Analytics to rail your site's traffic, you tin can verify your site using the Google Analytics tracking code used in your Search Panel property.

⚠️ Requirements

  • Your homepage cannot crave authentication. The site homepage must be bachelor to non-logged-in users for verification. Additionally, any pages that require hallmark to accomplish probably won't appear in Search often, so they won't accrue meaning Search information.
  • You must have "edit" rights for the Google Analytics business relationship used by that page. In Google Analytics iv, the verification code is associated with a Google Analytics stream. For earlier versions of Google Analytics, the verification code is associated with a Google Analytics Web Property.
  • You must use the same Google business relationship for both Search Panel and Google Analytics.
  • Your not-logged-in homepage (see notation) must contain either the analytics.js or gtag.js snippet. The tracking code must exist in the <head> department, not the <torso> section, of your page. To confirm the presence of this tag, visit the page in your browser, view the page source, and search for the snippet.
  • Utilise the lawmaking exactly as provided; practise not modify information technology. If you modify information technology, verification will fail.
  • Can be used for URL-prefix properties, just not Domain backdrop.

Steps

To verify ownership using a Google Analytics tag:

  1. Open Search Console using the same Google business relationship that has edit access in Google Analytics.
  2. Read the requirements for this verification technique.
  3. Choose Google Analytics in the verification details page for your site and click Verify.
  4. If verification fails, run acrossPotential errors beneath to troubleshoot the effect.

Note

  • The Google Analytics tracking lawmaking is used only to verify site buying. No Google Analytics data will be accessed.

Potential errors

The post-obit verification errors can occur with Google Analytics tracking code verification:

  • Snippet not constitute
    Did you put the snippet in the right location of the home page? Does the not-logged-in homepage incorporate your snippet?
  • Malformed snippet
    Be sure to apply the snippet exactly as provided.
  • Wrong snippet found (quondam Google Analytics snippet)
    Search Console supports only the latest version of the Google Analytics snippet.
  • Wrong snippet blazon (Tag manager/third-political party tag director)
    Be sure that you are using your Google Analytics snippet.
  • Snippet in wrong location
    The snippet must be in the <caput> section of your home folio.
  • You don't have a Google Analytics account / Insufficient permissions
    Y'all must accept a valid Google Analytics business relationship and you must have Edit permissions on that account.
  • Additional common verification problems are listed below.

Google Tag Manager container snippet

Google Tag Manager for site ownership verification - Google Search Console Preparation

If you lot have a Google Tag Manager account active on your site, yous tin can verify buying of your site using your Google Tag Director container snippet code.

⚠️ Requirements

  • Your homepage cannot require authentication. The site homepage must be available to non-logged-in users for verification. Additionally, whatever pages that require authentication to reach probably won't appear in Search oft, and then they won't accrue pregnant Search data.
  • You must take Publish permission for the Google Tag Manager container on the folio.
  • You must use the same Google business relationship for both Search Console and Google Tag Director.
  • Your not-logged-in homepage (see note) must comprise the correct tag in the correct location. The <noscript> portion of the Tag Manager lawmaking must be placed immediately after the opening <torso> tag of your page. If it is not, verification will neglect. Y'all cannot insert a information layer (or anything other than HTML comments) between the <torso> tag and the Tag Manager code. To ostend the presence of this tag, visit the page in your browser, view the page source, and search for the snippet.
  • Utilize the code exactly as provided; do not alter it. If you modify it, verification will fail.
  • Can exist used for URL-prefix backdrop, but non Domain backdrop.

Steps

To verify buying using a Google Tag Director tag:

  1. Open Search Console using the aforementioned Google account that has edit admission in Google Tag Manager.
  2. Read the requirements for this verification technique.
  3. Cull Google Tag Manager in the verification details folio for your site, and follow the instructions shown.
  4. If verification fails, seePotential errors below to troubleshoot the result.

Potential errors

The following verification errors tin can occur with Google Tag Managing director verification:

  • Snippet non establish
    Did yous put the snippet in the correct location of the home page? Does the non-logged-in homepage contain your snippet?
  • Insufficient permissions
    Yous need Publish permission on your Google Tag Manager container.
  • Incorrect tag
    Be sure that you are using the proper tag associated with the account used to sign in to Search Panel.
  • No tag manager container
    You haven't created any containers in your Tag Manager account.
  • Tag not found / wrong location
    Be sure to put the tag on the proper page and location, as described above.
  • Additional common verification problems are listed beneath.

Blogger

Blogger for site ownership verification - Google Search Console Training

New blogs that you lot create in Blogger should be added and verified automatically in your Search Panel account. If your blog doesn't appear automatically on the Search Console home page, add together the property and information technology should be verified automatically.

⚠️ Requirements

  • Older blogs are not automatically verified, and should be verified using the HTML tag method.
  • Be certain that you are logged in to Search Console with the aforementioned business relationship used to manage your blog.

Google Domains

If you've registered a domain with Google Domains, any belongings that you register on that domain should be verified automatically when you add it to Search Console.

Where should I put my verification tag?

If you are using a tag-based verification method (Google Analytics, Google Tag Manager, or the HTML <meta> tag methods), Search Console will wait for your verification tag in the page to which a non-logged-in user is redirected when visiting the URL that defines your belongings.

Example

If you define your property as https://example.com, and any non-logged in user who types that URL in their browser is redirected to https://example.com/home, then Search Console will look for your verification tag in the page https://example.com/home.

For other verification methods, such every bit the file upload method, redirects are not followed.

Common verification errors

In addition to any method-specific verification errors, the post-obit verification errors are possible in most verification methods:

  • Incorrect tag/snippet/file errors
    Be sure to use the exact tag, lawmaking snippet, or file provided to you when first verification.
  • The connexion to your server timed out.
    We were unable to verify your file because we received a server timeout. This could be because your server is down or is busy and responding slowly. Brand sure that your server is responding and try again.
  • We encountered an error looking up your site'southward domain proper noun.
    We tried to access your verification file, but were unable to access your domain due to a DNS error. This could exist because your server is down, or there is an issue with the DNS routing to your domain. Make sure that your domain is resolving correctly and try again.
  • The download request was redirected besides many times.
    Check the URL for potential issues, such as an infinite loop.
  • Your server returned an invalid response.
    This can happen if your site is requires countersign authentication, or if we cannot access it for other reasons.
  • Nosotros were unable to connect to your server.
    Make sure that your server is non downwardly, and that your domain is resolving correctly, and try again.
  • An internal error occurred.
    If this problem persists, check the Webmaster Primal Aid Forum for updates.
  • Timeout
    Either your site or the domain server stopped responding to our requests (depending on the verification method used). Confirm that your site is responding, and then endeavour once again.
  • Could not find your domain
    We tried to resolve the site URL that yous gave united states of america, but it is unknown to the DNS service. Check that you are providing the correct URL for your property.

Was this helpful?

How can we improve it?