\n Webmaster Tools<\/a>,
\n you’re probably familiar with verifying ownership of your sites. Simply add a specific
meta<\/code> tag
\n or file to your site, click a button, and you’re a verified owner. We’ve recently made a few small
\n improvements to the process that we think will make it easier and more reliable for you.\n<\/p>\n\n The first change is an improvement to the meta<\/code> tag verification method. In the past, your
\n verification meta<\/code> tag was partially based on the email address of your Google Account. That meant
\n that if you changed the email address in your account settings, your meta<\/code> tags would also change
\n (and you’d become unverified for any sites you had used the old tag on). We’ve created a new
\n version of the verification meta<\/code> tag which is unrelated to your email address. Once you verify
\n with a new meta<\/code> tag, you’ll never become unverified by changing your email address.\n<\/p>\n\n We’ve also revamped the way we do verification by HTML file. Previously, if your website returned
\n an HTTP status code other than 404<\/code> for non-existent URLs, you would be unable to use
\n the file verification method. A properly configured web server will return 404<\/code> for
\n non-existent URLs, but it turns out that a lot of sites have problems with this requirement. We’ve
\n simplified the file verification process to eliminate the checks for non-existent URLs. Now, you
\n just download the HTML file we provide and upload it to your site without modification. We’ll
\n check the contents of the file, and if they’re correct, you’re done.\n<\/p>\n![\"the](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-411c84258432.png\")
<\/p>\n
\n We hope these changes will make verification a little bit more pleasant. If you’ve already
\n verified using the old methods, don’t worry! Your existing verifications will continue to work.
\n These changes only affect new verifications.\n<\/p>\n