One TXT record verifies your whole domain — every subdomain, every protocol — instead of registering http, https, www, and apex as four separate properties.
Published July 12, 2026 · ~3 min read
The process
The full path from an unverified domain to indexed pages reporting in one property. Each crumb is a Directions step below.
Directions
1Add a Domain property, not a URL prefix
Go to search.google.com/search-console and click Add property. Google offers two types: Domain and URL prefix. Choose Domain and enter the bare domain (example.com, no https://, no www). A domain property automatically covers every subdomain and both protocols, so you never end up with traffic split across four half-empty properties.
URL-prefix properties still have one use — they support more verification methods (HTML file, meta tag) for cases where you can't touch DNS. If you control DNS, the domain property is strictly better.
2Copy the verification TXT record
Google shows a TXT value starting with google-site-verification=. Copy the whole string. The record goes at the root of the zone — host @ or blank depending on your DNS panel — not at a subdomain.
Leave this record in place permanently. Google re-checks it periodically, and if it disappears your verification (and everyone you granted access through it) eventually lapses.
Add the TXT record in your DNS provider. It coexists fine with SPF and any other TXT records at the root — multiple TXT records at the same host are normal, it's only SPF that has a one-record rule.
If your registrar hosts your DNS and offers a "verify with Google" one-click flow, that works too; it just creates this same record for you.
4Click Verify
Back in Search Console click Verify. New TXT records usually propagate within minutes, but Google's resolvers can cache a miss, so if it fails immediately, wait ten minutes and retry rather than re-adding the record. Once verified you land in a property with no data — reports start filling in within a couple of days.
5Submit your sitemap
Open Sitemaps in the left rail and submit the full URL of your sitemap (most generators publish /sitemap.xml or /sitemap-index.xml). This is the single highest-leverage action in Search Console: it tells Google every URL you consider canonical and gets new pages discovered in hours instead of weeks.
While you're here, check Settings → Users and permissions and add a second owner. DNS-verified ownership is tied to that TXT record; a second owner keeps access alive if the record ever gets cleaned up by mistake.
Common issues & fixes
Verification fails even though the TXT record is live.
Check it's at the root (@), not www, and that you copied the entire google-site-verification string. Use a DNS lookup tool to confirm, then retry — Google caches failed lookups for a few minutes.
Property verified but shows no data for days.
Normal for a new property. Performance data starts from the verification date and takes 2–3 days to appear; it is not retroactive, which is a good reason to verify early.
Sitemap shows 'Couldn't fetch'.
The status is often stale. Confirm the sitemap URL returns 200 with content-type XML, resubmit, and check back the next day before assuming a real fetch problem.
You lost access after a DNS migration.
The TXT record didn't survive the move to the new DNS host. Re-add the same google-site-verification value — the token doesn't change — and ownership comes back.
Subdomain traffic isn't visible separately.
A domain property aggregates everything. Use the page filter (page contains subdomain.example.com) or add the subdomain as an additional URL-prefix property for a dedicated view.
Honesty note: articles are drafted with AI assistance, then a human
checks each one against the vendor's current setup flow before it
publishes — nothing goes live unreviewed. Vendor interfaces still
change; if a step looks different, the underlying record is what
matters.