Verification errors
If you received an error while trying to verify your site, find the error in the list below to find out the possible causes and solutions.
If your site is verified but no longer appears to be verified, make sure that the HTML file, meta tag, or DNS record you used to verify the site is still in place. Removing any of these may cause your site to become unverified and you will need to perform the verification process again.
General verification errors
HTML validation file errors
Meta tag verification errors
DNS verification errors
General verification errors
Timeout occurred while connecting to your server.
We were unable to verify your file because we received a server timeout error. This may be because your server is down or busy and responds slowly. Make sure your server is responding and try again.
We encountered an error while looking up your site's domain name.
We tried to access your verification file, but we were unable to access your domain due to a DNS error. This may be because your server is down or there is a problem with DNS forwarding your domain. Make sure your domain is resolving correctly and try again.
The download request was redirected too many times.
Check the URL for potential problems like infinite loop.
Your server returned an invalid response.
This can happen if your site requires password authentication or if we cannot access your site for other reasons.
We were unable to contact your server.
Make sure your server is not disabled and your domain is resolving correctly and try again.
An internal error has occurred.
If the problem persists, check the Webmaster Central Help Forum for updates.
More about HTTP status codes
The download request was redirected too many times.
If your site redirects traffic to another site, we recommend using meta tag verification instead.
Your verification file redirects to a disallowed location.
Googlebot does not follow redirects for verification files. If your site directs all density to another site, we recommend using meta tag verification. Redirects within a single site (for example, http://example.com/ site http://www.example.com/ site) are allowed.
Meta tag verification errors
should be in.
If you see this error, check the following:
Is the meta tag on the correct page? We search for the meta tag on the homepage of your site. The home page is the page your server returns when someone requests your site (for example, http://www.example.com/). The name of this page is often index.html or index.htm, but a different name may be given depending on the configuration of your server.
Is the meta tag in the correct place on the page? We search the meta tag in the HEAD section of the page. Below is an example of the correct placement of the meta tag.
If you are using Web editor or WYSIWYG editor to edit your page, be sure to check the 'Edit HTML' option or edit the page's source code.
Your meta tag is wrong.
We found the verification meta tag, but the content was incorrect. Copy and paste the meta tag provided on the Verification page of Webmaster Tools to avoid errors.
Your homepage returns a XXX HTTP status code instead of 200 (Successful).
If your server returns an HTTP status code other than 200 (Successful) for your homepage, Webmaster Tools cannot verify that the file in question has the expected filename and content. Learn more about HTTP status codes.
DNS verification errors
DNS not found
Your verification TXT record was not found.
Your verification TXT record has the wrong content.
Webmaster Tools checks to see if your DNS record matches the record details provided on the Verification page. If it doesn't match, we can't verify that you own the site.
DNS incorrect TXT
Your verification DNS record has the wrong TXT. Show found TXT.
Permanent error in DNS resolution
We encountered a permanent error while searching for your verification DNS record.
DNS resolution error
We encountered an error while looking up your verification DNS record.
Source: Google
March 9, 2020, 2:34 p.m.