Verify your site buying

What is verification?

Verification is the process of proving that yous own the property that you claim to own. Search Panel needs to verify ownership considering verified owners have access to sensitive Google Search information for a site, and can affect a site'southward presence and behavior on Google Search and other Google properties. A verified owner tin can grant full or view access to other people.

VERIFY YOUR Property

Verify a website holding

  1. Either add a new property or choose an unverified holding from your property selector.
  2. Choose ane of the verification methods listed below 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 multiple verification methods in your holding's verification settings folio. You might want to add more than than one verification method in instance ane of your existing verification methods fails (for example, if yous verified using a Google Analytics tracking lawmaking, and someone changes a template on your website that omits the tag).

To add an additional verification method, visit the Settings page for the property and click Ownership verification

Multiple people tin verify ownership of the same website belongings, using the same or different verification methods. If you use the same verification method, just be sure that you don't overwrite the verification tokens of any other owners.

Verifying child properties

Once yous have verified a holding, you can create and verify child backdrop very easily with the same verification method with little additional work. That is, if you have verified buying of instance.com using the HTML file upload method, whatsoever kid properties that you create will be motorcar-verified using the same method.

How long does verification last?

Verification lasts as long as Search Console can ostend the presence and validity of your verification token. Search Panel periodically checks if your verification token is even so present and valid (for example, past checking if your HTML verification tag is still present). If verification tin no longer exist confirmed, you will be notified. If the issue is not fixed, your permissions on that property volition expire after a sure grace menses.

If all verified owners lose access to a property, all users with full view permissions volition and so lose admission to the Search Panel property.

The user agent that performs HTML tag verification has the user agent token Google-Site-Verification and the total user agent string Mozilla/5.0 (compatible; Google-Site-Verification/1.0)

When will I commencement to see data?

Data is collected for a holding as soon equally anyone adds it in Search Console, even earlier verification occurs.

We lost our only verified site owner!

If the only verified owner of your site leaves your squad, or you're not sure who the verified owner is, yous (or someone you know) should verify ownership to maintain (or regain) access to the holding.

If yous are taking over a site from another owner, after you lot verify buying you lot can unverify previous owners by removing their verification token (for case, removing the HTML tag from the site, for HTML-tag-verified owners). Come across Add or remove owners for more information.

Choosing a verification method

Search Console supports several different verification methods. Run into the tabular array below to help choose 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 information technology on your site at a specific URL. Might non be possible on a site hosting platform.
HTML tag Relatively simple, merely requires the ability to edit the HTML source code of your site's homepage. Might non be possible on a site hosting platform.
Google Analytics tracking lawmaking Simple, if the folio already has a Google Analytics tracking code for a Google Analytics account that y'all can access. If the page does not have a tracking code, y'all must must add together one (which may require creating a Google Analytics account if you don't already accept one).
Google Tag Director Uncomplicated if the page already has a Google Tag Manager snippet for a Google Tag Director account that you can access. If the folio does not accept a snippet, you must must add together one (which may require creating a Tag Manager account if yous don't already take one).
Google Sites, Blogger, or Domains account Use the recommended method for each platform.
Domain proper noun provider More complex, only is the merely style to verify a Domain property. If your domain provider is listed in the verification wizard, then this is a simple process. Domain backdrop are useful because they include information for all protocol (http/https) and subdomain variations of your property.

Verification method details

Sites that use a website hosting platform

If you lot utilise a website hosting platform similar WordPress, Wix, or SquareSpace, you might be limited in which verification methods are available to yous. Or, conversely, your platform might provide a special plugin or setting to verify your property on Search Console.

If you're using a CMS, attempt these steps before trying one of the verification methods listed on this page:

  1. Search your site host'due south documentation for Search Panel verification information. For instance: "Wix Search Panel verification" or "Weebly Search Console verification".
  2. Search for plugins on your platform that tin handle verification for you. For example, Site Kit for WordPress tin handle verification for you, and also provide simplified views of your Search Console information. Note that Site Kit is the only plugin that is officially sponsored by Google, so exercise a little enquiry on any plugin before you install it.

HTML file upload

HTML file upload for site ownership verification - Google Search Console Grooming

You tin verify ownership of a site by 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 cause you to lose verification for the site.

⚠️ Requirements

  • The file cannot crave authentication. The directory where y'all upload your HTML file must be available to non-logged-in users. You can test this by trying to visit your file in an incognito window in your browser.
  • You lot must be able to upload a file to the root directory of your website, where it will exist bachelor to web browsers. If you exercise not have permissions to do this, attempt another verification method. If y'all are using a website hosting platform, you lot might need to search your service's help pages to come across 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 lot are using a website hosting platform, search your service's help pages for custom instructions to verify your site on Search Console. If yous don't find any data, then continue on to the side by side steps.
  2. Read the requirements for this verification technique.
  3. Choose the HTML file upload method on the Ownership verification page for your property.
  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 property. (That is, if you defined your holding as https://example.com, and the file provided is named 1234.txt, then the file should be saved and browsable at https://example.com/1234.txt.) Search Console does non follow redirects when looking for this file. Yous can add newlines at the stop of the file body, if required, but practise not otherwise change the file name or content.
  6. Confirm that you can see the file by visiting information technology in your browser in the location specified past the Search Console verification wizard. If the file isn't available to your browser at that URL, Google won't be able to find for verification purposes.TIP: Utilise an incognito window in your browser to ostend that y'all don't need to log in to access it.
  7. Complete verification by clicking Verify in the verification details folio.
  8. If verification fails, see Potential errors beneath to troubleshoot the issue.

Potential errors

The following errors can occur with HTML file upload verification:

  • Your verification file was non constitute.
    Please 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 proper noun or content does non match the HTML file provided, we won't be able to verify your site ownership.
  • Your verification file has the incorrect content.
    Search Console checks to see if your verification file has the same filename and content as the file provided on the Verification page. If the file name or content does not match the HTML file provided, we won't exist able to verify your site buying. Please 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 attempt failed in a way that indicates that your site might take been hacked. Learn more 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 unmarried site—for example, from http://example.com/ to http://www.example.com/—are allowed. If your site redirects all traffic to some other site, we recommend using HTML tag verification instead.
  • Boosted common verification problems are listed below.

HTML tag

HTML tag for site buying verification - Google Search Console Training

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 tin't discover the tag, nosotros'll give you information about the error we encountered. This tag is tied to a specific user. Search Console volition periodically check for the presence of this tag.

⚠️ Requirements

  • Your homepage cannot require hallmark. The site homepage must be available to not-logged-in users.
  • You must be able to edit the HTML source code of the site'south homepage directly. Specifically, you lot must be able to insert a tag into the <caput> tag on your homepage. If you do not take permissions to practice this, try another verification method. If you are using a website hosting platform, yous might demand to search your service'south help pages to see if this is possible.
  • Can be used for URL-prefix properties, but not 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 continue on to the next steps.
  2. Read the requirements for this verification technique.
  3. Cull the HTML tag method on the Buying verification page for your holding.
  4. Re-create the tag from the Search Console verification magician into the <head> section in the HTML of your site's non-logged-in domicile page (see note). Example:
    <head>
    <title>Example.com homepage</title>
    <meta name="google-site-verification" content="......." />
    </caput>
    This tag is unique to y'all; it cannot be used to identify anyone else, and is associated with your Gmail business relationship.
  5. Save your page. Confirm that the tag is present in your alive page by visiting the folio and looking for the tag in the folio source lawmaking. (PressControl + F then search for "google-site-verification" in the folio source to find the tag.)
  6. Complete verification by clicking Verify in the verification details page.
  7. If verification fails, run into Potential errors below to troubleshoot the issue.

Potential errors

The post-obit verification errors can occur with HTML tag verification:

  • Meta tag non found/in the wrong location. The verification meta tag must be within the <head> section of the page. If y'all meet these errors, cheque the following:

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

    • Is the meta tag in the right identify on the folio? Nosotros wait for it in the page's <caput> section. An example of correct placement is shown here: 
                                  <html>   <head>     <championship>Your Page Title</title>     <meta name="google-site-verification" content="your verification string">   </head> <body> ...
    • If yous're using a spider web editor or a WYSIWYG editor to edit your page, brand sure you lot're editing the HTML of the live page, non merely the local re-create on your calculator.
  • Your meta tag is incorrect.
    We establish the verification meta tag, simply the contents were wrong. To avoid errors, copy and paste the meta tag provided on the Verification page of Search Console. If another user'southward verification tag was already present in the folio, you might become this error; confirm that the exact tag given to you lot in the Search Panel verification sorcerer is present in the page HTML.
  • Additional common verification problems are listed below.

Domain name provider

DNS record for site ownership verification - Google Search Console Training

Domain verification is required to verify a Domain belongings, but tin too be used to verify a URL-prefix property. This verification method involves submitting a record into your domain proper name provider's record list. This method may require you to be comfy with a little bit of technical noesis.

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

⚠️ Requirements

  • You must have a custom domain proper noun, or command your domain proper name.
  • You must be able to log into your domain name provider.

Steps

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

  1. If you are using a website hosting platform, search your service's aid pages for any custom instructions on verifying your site on Search Console. (Tips for finding your DNS provider, if y'all don't know who it is.) If y'all don't detect a custom solution on your provider's page, and so continue on to the next steps.
  2. Choose the Domain name provider method on the Ownership verification page for your property in Search Panel. (This will exist called automatically when you create a Domain belongings.)
  3. Run across if your Domain 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 will be required to log in to your domain provider, after which verification should occur immediately.
    2. If it is not listed, choose Any DNS provider and follow the transmission domain name provider instructions below.

      Manual domain name provider instructions

      If your domain name provider is not listed in the Domain proper noun verification dialog, you volition need to manually add a DNS record. This DNS record is a proper noun/value pair provided by Search Console. Allow's go started:

      Determine which DNS tape format to use. You must use either a TXT tape or a CNAME record, depending on how your site is configured. To make up one's mind which format you lot must use:

      1. Open the Google Admin Toolboxin the CNAME tab
      2. Enter your property's domain name. This is the office between "https://" and the path: For the property "https://world wide web.example.com/" the domain name would be "www.example.com".
      3. Wait at the output:
        • [Nearly common case]If you see " Record not plant!" and then follow the TXT tape 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.
          Test results for a domain with no value after the phrase "IN CNAME". Use TXT record instructions

      TXT DNS tape instructions

      1. Generate a unique TXT verification record: When asked to verify your property in Search Console, choose the Domain proper noun provider method and Search Console will give you lot a string value TXT record to apply in the adjacent step.
      2. Add your DNS tape to your domain provider:Add the TXT record that Search Panel gave y'all in the previous step to your domain provider'south records by post-obit these steps:
        1. Find the Google Workspace documentation for your provider.
        2. Ignore Google Workspace step one (Become your unique verification tape) considering you lot already generated your TXT record in Search Console.
        3. Sign in to your domain host (typicallyGoogle Workspace Stride ii ).
        4. Add your Search Panel TXT record to your domain's DNS records (typically Google Workspace Footstep three):
          • For theHost/Name belongings,either get out this bare, or set as "@", as described in the documentation for your DNS provider.
          • For the Value property, provide the Search Console TXT record cord that you generated earlier.
        5. Ignore Google Workspace step 4 (the verification step) and continue with step 4 below.

      CNAME DNS record instructions

      1. Generate a unique CNAME verification record
        1. Open Webmaster Fundamental. Don't apply the TXT record from Search Console. You'll need to use Webmaster Cardinal to generate a DNS record.
          • If your holding is in the list on Webmaster Central:
            1. Select the property.
            2. ClickVerify using a different method
          • If the property is not in the list on Webmaster Key:
            1. Click Add a belongings in Webmaster Central, higher up the belongings list.
            2. Enter your bare host proper name (that is, example.com, non http://instance.com).
            3. Click Continue.
            4. Select Alternate methods
        2. SelectDomain name provider.
        3. Choose your provider from the list, or select Other.
        4. Click Add a CNAME tape to generate your DNS CNAME record.
      2. Add the DNS tape to your domain provider:
        1. Find the Google Workspace documentation for your provider
        2. Ignore Google Workspace step i (Get your unique verification tape) because you lot already generated your CNAME record in Search Console.
        3. Sign in to your domain host (typicallyGoogle Workspace Step 2 ).
        4. Add together your CNAME verification record to your domain's DNS records (typically Google Workspace Step 3)using the record you got from Webmaster Central. Provide both the tape name and record value in the appropriate fields on your DNS provider'south site. You tin can use the default TTL value suggested by your provider.
        5. Ignore Google Workspace step 4 (the verification footstep) and keep with step 4 beneath.
  4. Complete your buying verification by clicking Verify in the Search Panel verification details page. Of import: For manually installed records, it tin can take up to two or 3 days for your provider to start serving the record. If you take followed the Transmission domain proper noun provider instructions higher up and verification fails, wait a day or two and try over again. Run across the Potential errors section for troubleshooting, or to larn how to meet whether your domain name provider is serving your record still.

Important: To stay verified, don't remove the DNS tape from your provider, even later 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 proper name into the box at the top, without the protocol or any slashes (that is, enter example.com, not https://example.com).
  3. Click either TXT or CNAME, depending on what record type yous are using for verification. (About sites use TXT records for domain verification.)
  4. All DNS records of the selected type constitute on your provider volition exist shown at the bottom with a label describing the record type (typically, either CNAME or TXT).
  5. Await in the list of records for the DNS record issued to you by 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 belongings domain, and the value includes dv.googlehosted.com.
    Your record should match exactly the verification record values given to you by Search Panel. (You can look upwards your Search Console DNS record values by following the manual verification steps over again to the step where yous generate a verification record.)
  6. If yous don't run across your credentials listed, wait a day or two, then try again.

To meet your DNS tape subsequently you've verified your property using the DNS method:

  1. Open Webmaster Central
  2. Click your belongings proper noun in the list of properties to see a list of verification methods for the property.
  3. Next to either DNS TXT record  or DNS CNAME record, click Details to come across your tape value.
  4. If you like, you can likewise run into all records existence 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 record was not plant. It can take a few minutes or even days subsequently posting the record for it to exist visible to Google; wait a twenty-four hour period or two then endeavour again.
  • Your verification tape did not match
    No verification records on your DNS provider matched the value given to y'all by Search Console. Exist certain to use the record provided by the verification folio. For a TXT tape, you should leave the name/host field blank and use your TXT string in the DNS tape'southward value field. For a CNAME record, you lot are given a name/value pair to utilise in your DNS record's proper noun/value fields.
  • Additional common verification bug are listed below.

Google Analytics tracking lawmaking

Google Analytics for site ownership verification - Google Search Panel Training

If yous use Google Analytics to track your site'due south traffic, you can verify your site using the Google Analytics tracking code used in your Search Console property.

⚠️ Requirements

  • Your homepage cannot require authentication. The site homepage must be available to non-logged-in users for verification. Additionally, whatsoever pages that require authentication to reach probably won't appear in Search often, and so they won't accumulate significant Search information.
  • You must take "edit" rights for the Google Analytics account 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 Spider web Property.
  • Yous must employ the same Google account for both Search Console and Google Analytics.
  • Your not-logged-in homepage (see note) must comprise either the analytics.js or gtag.js snippet. The tracking code must be in the <caput> department, not the <body> department, of your folio. To confirm the presence of this tag, visit the page in your browser, view the page source, and search for the snippet.
  • Use the code exactly as provided; do not change information technology. If you lot change it, verification volition fail.
  • Can be used for URL-prefix properties, but not Domain properties.

Steps

To verify ownership using a Google Analytics tag:

  1. Open Search Console using the same Google account that has edit admission in Google Analytics.
  2. Read the requirements for this verification technique.
  3. Choose Google Analytics in the verification details folio for your site and click Verify.
  4. If verification fails, seePotential errors below to troubleshoot the issue.

Notation

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

Potential errors

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

  • Snippet not plant
    Did you put the snippet in the right location of the abode folio? Does the non-logged-in homepage contain your snippet?
  • Malformed snippet
    Exist sure to apply the snippet exactly as provided.
  • Wrong snippet plant (quondam Google Analytics snippet)
    Search Console supports only the latest version of the Google Analytics snippet.
  • Wrong snippet type (Tag manager/third-political party tag manager)
    Be certain that you are using your Google Analytics snippet.
  • Snippet in wrong location
    The snippet must be in the <head> department of your home folio.
  • You don't have a Google Analytics account / Insufficient permissions
    You must have a valid Google Analytics account and yous 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 Training

If yous take a Google Tag Manager account active on your site, y'all can verify ownership of your site using your Google Tag Managing 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 and then they won't accrue significant Search information.
  • Yous must take Publish permission for the Google Tag Manager container on the page.
  • You must use the same Google business relationship for both Search Console and Google Tag Managing director.
  • Your not-logged-in homepage (see annotation) must contain the correct tag in the correct location. The <noscript> portion of the Tag Director code must exist placed immediately after the opening <body> tag of your page. If it is not, verification will neglect. You cannot insert a data layer (or anything other than HTML comments) between the <body> tag and the Tag Manager lawmaking. To ostend the presence of this tag, visit the page in your browser, view the folio source, and search for the snippet.
  • Utilise the code exactly as provided; do not change information technology. If y'all change it, verification will fail.
  • Can be used for URL-prefix properties, simply not Domain properties.

Steps

To verify buying using a Google Tag Managing director tag:

  1. Open Search Panel using the aforementioned Google business relationship that has edit access in Google Tag Director.
  2. Read the requirements for this verification technique.
  3. Choose Google Tag Managing director in the verification details page for your site, and follow the instructions shown.
  4. If verification fails, seePotential errors below to troubleshoot the issue.

Potential errors

The following verification errors can occur with Google Tag Manager verification:

  • Snippet not found
    Did you put the snippet in the right location of the home folio? Does the non-logged-in homepage contain your snippet?
  • Insufficient permissions
    Y'all need Publish permission on your Google Tag Manager container.
  • Wrong tag
    Be certain that yous are using the proper tag associated with the business relationship used to sign in to Search Console.
  • No tag manager container
    You oasis't created any containers in your Tag Managing director business relationship.
  • Tag not plant / wrong location
    Exist sure to put the tag on the proper page and location, as described to a higher place.
  • Additional common verification issues are listed below.

Blogger

Blogger for site ownership verification - Google Search Console Training

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

⚠️ Requirements

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

Google Domains

If you've registered a domain with Google Domains, any property that you register on that domain should be verified automatically when you add information technology to Search Panel.

Where should I put my verification tag?

If you lot are using a tag-based verification method (Google Analytics, Google Tag Manager, or the HTML <meta> tag methods), Search Console volition await for your verification tag in the folio to which a not-logged-in user is redirected when visiting the URL that defines your holding.

Example

If you define your property every bit 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 await for your verification tag in the page https://case.com/abode.

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

Common verification errors

In addition to any method-specific verification errors, the following 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 beginning verification.
  • The connectedness to your server timed out.
    Nosotros 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. Make sure that your server is responding and try once again.
  • We encountered an error looking up your site'southward domain name.
    We tried to access your verification file, but were unable to access your domain due to a DNS fault. This could be because your server is downward, or there is an upshot with the DNS routing to your domain. Make sure that your domain is resolving correctly and effort once again.
  • The download request was redirected too many times.
    Check the URL for potential issues, such as an infinite loop.
  • Your server returned an invalid response.
    This tin happen if your site is requires countersign hallmark, or if we cannot admission it for other reasons.
  • We were unable to connect to your server.
    Make certain that your server is not down, and that your domain is resolving correctly, and try once more.
  • An internal error occurred.
    If this trouble persists, check the Webmaster Primal Help 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 try again.
  • Could not find your domain
    We tried to resolve the site URL that you gave us, simply it is unknown to the DNS service. Check that yous are providing the correct URL for your belongings.

Was this helpful?

How can we improve it?