How to Verify Your Google Apps Domain: A Step-By-Step Guide
If you haven’t verified your Google Apps domain yet, then this article is for you. Here, we will guide you through the process of verifying your Google Apps domain. In this article, we’ll be able using two domain verification methods — via the TXT record and HTML file.
Why You Should Verify Your Google Apps Domain
A domain name is an essential element of a website for a reason. Similar to your home address, a domain name allows web browsers to direct visitors to your site. Due to this fact, all domain names must be unique.
In that regard, Google Apps requires domain verification to clarify that you’re the sole owner of your domain name. Verifying your Google Apps domain allows you to access Google’s services such as G Suite, Drive Enterprise, and Cloud Identity.
2 Ways to Verify Google Apps Domain
You can easily verify your Google Apps domain by adding a TXT record to your Domain Name System (DNS) records or uploading the HTML verification file to your website. Feel free to check out both verification methods and go with the one that best suits your preference.
1.Verifying Domain via TXT Record
This method works best if your web hosting service has a DNS Zone Editor. If you use Hostinger web hosting service, you can find the DNS Zone Editor in the Advanced section of your hPanel dashboard.
Here’s how to verify your Google Apps domain via TXT record:
Navigate to the DNS Zone Editor from your hosting account.
Locate the TXT (Text) section, then click Add New.
You’ll need to add some information to the appointed space. See the following explanation to know what information each field requires. Once you’re done, click Create.
Host – in most cases, you can fill this field with the at-sign (@) or leave it blank. However, some web hosting providers require you to enter your domain URL.
TXT value – this field requires your Google Apps domain’s security token, which is a 68-character string that begins with google-site-verification. You can find the security token in your Google Apps Admin console.
TTL – the Time To Live field lets you determine how fast the system should transmit the new DNS record across the world. The default duration of the TTL is 14400 seconds (4 hours).
That’s it! If the process was successful, the new TXT record should appear in the TXT section. Google Apps domain changes usually take up a few hours to take effect.
2. Verifying Domain by Uploading an HTML File via File Manager
If you’re a webmaster and only have access to an FTP or File Manager, you might want to use this method. In Hostinger, you can easily find the File Manager in the Files section of your hPanel dashboard.
Here’s how to verify your Google Apps domain by uploading an HTML file via the File Manager:
Navigate to the File Manager from your hosting account.
Open the public_html directory, then locate your .htaccess file. If you’re using cPanel and can’t find this file, refer to this tutorial instead.
Rename the .htaccess file to .oldhtaccess by right-clicking the file and selecting Rename.
Navigate back to the public_html directory, then hit the Upload button.
Upload your HTML verification file to the public_html directory. You can download this file from your Google Apps Admin console.
Once you’ve uploaded the HTML verification file, open it in a web browser by entering its directory path — yourdomain.com/htmlfilename.html. If you’ve uploaded the file correctly, you should see the google-site-verification text followed by the code in your HTML filename.
Return to your Google Apps Admin console and proceed with verification by clicking the Verify button. The verification process can take up to an hour to complete.
Once you’ve verified your domain, be sure to rename the .oldhtaccess file back to .htaccess.
Before you get to use Google’s services, you must verify your Google Apps domain. There are two ways to do this:
Adding a TXT record to your domain’s DNS records.
Uploading the HTML verification file to your website.
Did you find this tutorial useful? Let us know in the comments section below!