How to set up Google Search Console
Verifying a site takes minutes. Here is the fastest verification method for your setup and what to look at once you are in.
Search Console is the closest thing to a direct line to Google that a site owner gets, and it is free. It reports which of your pages are indexed, which search queries actually bring people to the site, whether Google has flagged anything as broken, and it lets you ask directly for a page to be crawled. Skipping it means finding all of that out the hard way, or not at all.
Choosing a property type
Google offers two ways to add a site, and the choice affects what the tool will show you.
| Property type | Covers | Verification method |
|---|---|---|
| Domain | Every subdomain, and both HTTP and HTTPS, in one combined view | DNS TXT record only |
| URL-prefix | Exactly the address you enter, and nothing else | HTML file upload, DNS, HTML tag, Google Analytics, or Google Tag Manager |
If you can edit your domain's DNS records, the Domain property is worth the extra step, because it saves you from separately verifying https://yourdomain.com and https://www.yourdomain.com as though they were different sites — which, technically, to a crawler, they are.
Verifying with a DNS TXT record
This is the method Domain properties require, and it is straightforward if you already know where your domain's DNS is managed.
-
Start the Domain property setup
In Search Console, choose Add Property, select Domain, and enter your domain name without
http://orwww. -
Copy the TXT record Google shows you
It will look something like
google-site-verification=long-random-string. Copy it exactly. -
Add it as a TXT record at the root of your domain
In your control panel's DNS section (or wherever your domain's DNS is managed), add a new TXT record with the host set to
@and the value set to the string Google gave you. -
Return to Search Console and verify
DNS changes are not always instant — see how long DNS propagation takes if verification fails immediately. It usually succeeds within minutes, but occasionally needs a longer wait.
Verifying with an HTML file instead
If you would rather not touch DNS, or you only need to verify one exact URL, choose a URL-prefix property and pick the HTML file method. Google gives you a small file with a specific name; upload it, unedited, to the root folder of your site through your control panel's file manager so that it is reachable at yourdomain.com/that-filename.html, then click verify. Do not move or rename it afterwards — Google periodically rechecks it is still there.
What to look at once you are verified
The dashboard has a lot in it. In the first week, three reports matter more than the rest:
- Coverage (sometimes labelled Pages). Lists every URL Google knows about and states why each one is or is not indexed. This is where a blocked or noindexed page you did not mean to exclude will show up.
- Performance. Shows the actual search queries bringing people to your site, and how often the site appeared versus how often it was clicked. This is real data about your site, not an estimate.
- Sitemaps. Confirms your submitted sitemap was read correctly and shows how many of its URLs were indexed. See creating and submitting a sitemap if you have not done this step.
If you verify with URL-prefix instead of Domain, remember that https://yourdomain.com and https://www.yourdomain.com are two separate properties to Search Console. Verify whichever one visitors actually land on after your redirect is applied — see 301 vs 302 redirects if you are not sure your www and non-www versions redirect to a single one.
If verification will not go through
- DNS TXT record not found yet. Give it longer than your first attempt — a newly added record can take a while to be visible everywhere, and Search Console checks from Google's own resolvers, not yours.
- The TXT value was copied with extra characters. A trailing space or a stray quotation mark added when pasting into your DNS panel is enough to break the match. Re-copy it directly from Search Console rather than retyping it.
- The HTML file was uploaded to the wrong folder. It has to sit at the root of the site, reachable at exactly the address Search Console shows before you upload it — inside a subfolder does not count.
- You verified the wrong version of the domain. A certificate or redirect issue on
wwwversus non-wwwcan make an HTML file verification fail even though the file itself is fine. This is one more reason the Domain property, which does not care which version answers, is the less fragile choice.
Leave the alerts on
Search Console emails the address on the Google account you used to verify when it detects something worth flagging — a manual action, a sudden jump in crawl errors, or a security issue such as detected malware. These notifications are the earliest warning most site owners get of a real problem, often before a human visitor would notice anything wrong. There is no reason to turn them off.
Setting this up is a once-only task. After verification, Search Console keeps collecting data in the background with nothing further required from you beyond checking back periodically.
Frequently asked questions
Is Google Search Console free?
Yes. There is no paid tier, no usage limit that matters for a normal website, and no reason not to set it up for any site you intend to keep.
Domain property or URL-prefix — which should I choose?
A Domain property covers the whole domain, including www and non-www, HTTP and HTTPS, and every subdomain, all in one view. It needs a DNS TXT record to verify. A URL-prefix property covers exactly one address and can be verified several ways, including an HTML file upload. If you can access your domain's DNS, the Domain property is less to maintain in the long run.
Related reading
A new site is invisible until Google has crawled and indexed it. Here is how to remove the obstacles and ask directly.
How to create and submit a sitemapWhat a sitemap actually does, how to build a valid one, and where to submit it once it exists.
How to set up website analyticsAdding the tracking code is the easy part. Here is what to decide first and how to check it is actually working.
How to check Google can crawl your siteBeing online and being crawlable are not the same thing. Here is how to check the difference directly rather than assume it.