How to verify Search Console by DNS

Before you start

• Access to your domain’s DNS
• A Google account

The steps

1. 1

   Step 1: Add a Domain property

   In Search Console choose "Domain" rather than "URL prefix". It covers every subdomain and both protocols.

2. 2

   Step 2: Copy the TXT record

   Google shows a string beginning google-site-verification=.

3. 3

   Step 3: Open your DNS provider

   Wherever the nameservers point — your registrar, or a DNS host such as Cloudflare.

4. 4

   Step 4: Create the TXT record

   Host or name: @ (or blank, depending on the provider). Value: the string Google gave you.

5. 5

   Step 5: Wait for propagation

   Usually minutes, occasionally an hour. Save the record before verifying.

6. 6

   Step 6: Click Verify

   If it fails, wait and retry rather than creating a second record.

7. 7

   Step 7: Leave the record in place

   Removing it later un-verifies the property.

Why not the HTML file or meta tag

Both live in the site itself, so a redeploy, a redesign or a platform migration can remove them silently. Losing verification is discovered at the worst moment — usually when you urgently need the data during a traffic drop.

The ownership point

If a former developer verified the property and you cannot, you do not control your own search data. DNS verification is the route nobody else can revoke, which is why it is worth the extra ten minutes.

Add Bing at the same time

Bing Webmaster Tools imports your verified properties from Search Console in a single step, which takes about two minutes. Bing's index is what feeds Copilot and several other assistants, so it matters more now than its market share alone suggests. Doing it at the same sitting means you never have to remember the second half of the job.

The background behind this

Technical SEO, in the order the problems actually block you covers the reasoning in about 4 minutes — free, ungated, written from client work.

Who wrote this

Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada, Ireland and Pakistan. These procedures are the ones I run on client work, written down rather than invented — including the ones where the honest answer is that the fix is not available on your current hosting.