Troubleshooting DNS TXT Verification for Google Search Console

Waiting for DNS records to update can stall your entire setup process. When verifying domain ownership via your domain registrar’s DNS TXT records, propagation typically takes anywhere from a few minutes to a couple of hours. In rare cases, it can take up to 24 to 48 hours to fully propagate worldwide.

Before assuming you just need to wait it out, run a quick diagnostic check to ensure the record was configured properly in your domain provider’s dashboard.

Step 1: Check If the Record Is Publicly Visible

Repeatedly clicking Verify in Google Search Console can lead to cached results. Instead, verify whether the record is visible across global DNS servers:

1. Visit a public DNS lookup tool such as Google Admin Toolbox Dig or DNSChecker.org.
2. Enter your bare domain (e.g., yourdomain.com—do not include www or https://).
3. Select TXT and run the lookup.

• Result A: You see google-site-verification=.... The record has propagated. Return to Google Search Console and complete verification.
• Result B: The lookup returns empty or does not display the verification string. The record has either not propagated yet or was entered incorrectly.

Step 2: Common DNS Provider Pitfalls (and How to Fix Them)

If the record does not appear in global lookups, check for these three common configuration issues inside your domain registrar's control panel:

1. The Host Name Field

When adding a TXT record, the Host Name (or Name/Host) field should usually be left completely blank or set to the @ symbol, depending on your registrar's interface. If you accidentally typed your full domain (e.g., yourdomain.com) into that box, your DNS provider might append the domain automatically, creating an invalid record for yourdomain.com.yourdomain.com.

2. Stray Whitespace in the Value Field

Ensure the exact string from Google Search Console (google-site-verification=...) matches without extra characters. Accidental leading or trailing spaces during copy-pasting will invalidate the record.

3. Active Nameserver Mismatch

This is the most common reason records fail to update:

• If your domain is registered through one provider (e.g., your domain registrar) but your website is hosted elsewhere (e.g., Cloudflare, Hostinger, Bluehost, or WordPress), your DNS zone is managed by the active host, not the registrar.
• Check the Nameservers section in your domain registrar's dashboard. If the nameservers point elsewhere rather than your registrar’s default servers, adding records inside your registrar’s DNS manager will have no effect.
• Fix: Add the TXT verification record directly inside the DNS management area of the provider hosting your active nameservers.