← Back to the full checklist

Verifying a Search Console domain property without handing Google your DNS

DISCOVERY · Search Console

Adding a Domain property in Search Console requires DNS verification. If your nameservers are on Cloudflare, Google offers a convenient one click path: authorize Google to access your DNS account and it writes the record for you.

Read that offer carefully before accepting it. It is an OAuth grant covering your DNS account, not just this one record and not just this one zone. If you manage more than one domain there, you are granting access far beyond the thing you are trying to do.

The manual route, which is not harder

In the verification dialog, change Instructions for from your provider name to Any DNS provider. Search Console then shows you a TXT record value instead of a button. Copy it.

Create the record yourself:

curl -X POST "https://api.cloudflare.com/client/v4/zones/$ZONE/dns_records" \
  -H "Authorization: Bearer $CF_TOKEN" -H "Content-Type: application/json" \
  -d '{"type":"TXT","name":"yourdomain.com",
       "content":"google-site-verification=YOUR_VALUE_HERE","ttl":1}'

Confirm it is live before clicking Verify, otherwise you will be told it failed and left wondering which half went wrong:

curl -s -H "accept: application/dns-json" \
  "https://cloudflare-dns.com/dns-query?name=yourdomain.com&type=TXT"

Propagation is usually seconds, not the day the dialog warns about. Once the record resolves, click Verify.

Do not delete the record afterwards

Verification is continuous, not a one time check. Google re-reads that TXT record periodically, and removing it un-verifies the property, which silently cuts off your data and any linked products. Label it clearly if your DNS panel supports comments, and leave it alone during cleanups.

Domain property or URL prefix

Prefer the Domain property. It covers every subdomain and both protocols in one place, so www, apex, http and https all report together instead of fragmenting your data across several properties. The only cost is that it requires DNS verification, which you have just done.

A general habit worth keeping: when a setup flow offers a convenient integration, check what permission it is actually asking for. Convenience that costs write access to your DNS is not convenience. It is a standing risk in exchange for saving one command.

Related