Google recommends that when you verify a site in Google Search Console, that you verify with two different methods. That way, if one is removed, such as we sometimes see when a site is hacked, then there is still a backup method that keeps a verification for your account intact.
Google also recommends that the two methods be unrelated to each other, again for security reasons. The two examples they give are verification through both the verification file and through DNS.
Make sure you are using two or more unrelated verification methods so that if one of them fails, the other one will definitely still be there.
So common possibility would be to use DNS and file verification, so that if DNS fails, then obviously your website won’t be available. But the file based verification, if your server kind of loses that files, if you drop out, if the server is returning errors for some reason, then the other one will be able to back you up.
There are actually five ways to verify your Google Search Console account – HTML file upload, domain name provier, HTML tag, Google Analytics tracking code and Google Tag Manager.
So it might be a good idea to add a second verification method to your Google Search Console account, before you might have a situation where you wish you had it done.
Jennifer Slegg
Latest posts by Jennifer Slegg (see all)
- 2022 Update for Google Quality Rater Guidelines – Big YMYL Updates - August 1, 2022
- Google Quality Rater Guidelines: The Low Quality 2021 Update - October 19, 2021
- Rethinking Affiliate Sites With Google’s Product Review Update - April 23, 2021
- New Google Quality Rater Guidelines, Update Adds Emphasis on Needs Met - October 16, 2020
- Google Updates Experiment Statistics for Quality Raters - October 6, 2020