If you need Search Console data for a domain you control, this step-by-step guide shows exactly how to verify a website in Search Console with a DNS record, in the right order, with no steps skipped. The method asks you, the site owner, to place a code Google gives you into your domain's DNS settings, which proves control of the domain itself. You will learn what each step does, why DNS proof is stronger than file uploads, when to expect the check to pass, where each setting lives, and how to fix the errors that stop most first attempts.
People usually land here at a specific moment: a site has launched, an agency has handed over a project, or a marketing hire needs data before planning any work. In all of those cases, verification is the gate. Until it is done, there are no queries, no coverage reports, and no way to ask Google to recrawl important pages. Ten careful minutes now unlocks all of it.
This guide assumes no coding knowledge. If you can log in where you bought your domain and copy and paste accurately, you can finish. Where providers differ in wording, the guide names the concept to look for.
Work through the steps in order, and do not skip the preparation in step one. Most failures trace back to being logged into the wrong Google account or editing DNS in the wrong place, not to anything Google did. Keep both tabs open until the success message appears.
The Domain property is the correct choice here, and the only one that uses DNS. It covers every subdomain and both protocols in one property. A URL prefix property, by contrast, verifies one exact address version using a file or tag. Google's help explains the difference in its documentation on adding a website property in Search Console, and picking the wrong type is the most common reason the DNS option never appears.
The record must be added wherever your domain's nameservers point, which is not always where you bought the domain. If you registered the domain with one company, host the site with another, and moved DNS to a third service, only the third panel matters. Check the nameserver values at your registrar first; they tell you whose panel actually controls your records.
Inside the correct panel, look for a section labelled DNS, DNS records, or Zone editor. You are adding a record to the zone for the root domain. Leave the host field empty, or enter the @ symbol, depending on the provider's convention. Never type the full domain into that field unless the provider demands it, or you may create a record Google will never find.
After saving, the waiting begins. DNS changes spread from server to server, and Google checks from its own resolvers. Many verifications pass within the hour; some providers take a full day. Pressing Verify repeatedly does not speed anything up, but trying every few hours is harmless.
If verification fails, diagnose in a fixed order. First, use a public DNS lookup to confirm the TXT value is visible on the root domain. Second, compare the visible value character by character with the one in Search Console. Third, confirm you are checking the same property and the same Google account that generated the code. Only after those three checks should you delete and re-add the record, and when you do, generate a fresh value rather than reusing a stale one.
While you wait, confirm the site itself is healthy, since verification only helps if crawlers can reach you afterwards. Once ownership is confirmed, the Seovaro blog has practical walkthroughs for reading your first coverage and performance reports, so the new data turns into decisions, not just charts.
One last check completes the setup nicely. Run your homepage through the free website links count checker to see how your internal and external links are distributed, so the property you just verified starts with a clear picture of your site's structure. Try it now, before the first data even arrives.
The DNS option appears only for Domain properties, not for URL prefix properties. If you added your site as a URL prefix, remove it or simply add a second property using the Domain option and your bare domain name. Both properties can exist, but the domain one is the one worth keeping.
Only someone with access to your DNS can add the required record, so protect your registrar account with a strong password and two-step verification. Review the owners and users list regularly and remove people who no longer need access.
No. One TXT record on the root domain verifies the entire domain property, including www, every other subdomain, and both http and https versions. That single-record coverage is precisely why the DNS method is recommended over per-address alternatives.
Enter the @ symbol, which most providers use to mean the root domain. If @ is rejected, check the provider's help pages, since a few panels expect the full domain name instead.