When Google keeps saying it cannot verify your domain, the record is almost never wrong in some mysterious way. It is usually in a place Google does not look. Here is how to find the right place and prove the record is there before you try again.
Facts checked
Google Workspace domain verification usually fails because the TXT record was added somewhere that does not answer for your domain. Google reads your public DNS, and that DNS is answered by whoever your nameservers point to. That is often your web host or Cloudflare, not the company you bought the domain from. Add the record at the registrar while the host answers, and Google never sees it, however many times you click Verify.
The fix is to look up your nameservers, add the record at that provider, and confirm it shows up publicly before you retry. Adding the record does not change where your email goes, so it is safe to do while your current email keeps working.
Most failed verifications are fixed at step one. The rest are a typing or host field problem caught at step four.
Run your domain through our free DNS lookup and read the nameserver lines. Names like ns1.yourhost.com point to a web host; names ending in cloudflare.com mean Cloudflare. That company is where the record has to go, whoever you bought the domain from.
Open the DNS settings there, sometimes called DNS zone, DNS records or Advanced DNS. If the nameservers point at your registrar, the registrar is the right place after all.
Type TXT. In the host or name field, use @ or leave it blank, whichever the panel asks for; some panels add your domain name to whatever you type, so never type the full domain there. Paste the value starting with google-site-verification= with no extra spaces or quote marks. Leave every existing record alone.
Run the DNS lookup again. When the Google value appears under TXT, Google can see it too. If it does not appear, the record went to the wrong provider or the host field changed it.
If the lookup shows the record and Google still says no, it has not caught up yet. Give it time and try again rather than adding more records.
Verification only proves you own the domain. Moving your email to Google is a separate step, done when the mailboxes are ready, so nothing goes missing in between.
The message on screen narrows the problem down quickly.
By far the most common case. Run the lookup: if the record is missing, it is in the wrong place or the host field changed it; if it is there, Google needs more time. Either way, adding the same record again in more places makes things harder to untangle later, so fix it in one place.
This is a different problem. The domain is already attached to another Google account, often an old trial someone started years ago, or a Google account set up by a past employee or web person. Google has a recovery process for this, and it also starts with proving you own the domain through DNS, so the same nameserver lookup is still the first step.
That is expected. Verification does not move email; the MX records do. Until they change, mail keeps going to your current provider, which is what you want while the new mailboxes are being set up.
Google also lists other ways to verify, such as a CNAME record. They all depend on the same thing: changing records at the provider that answers your DNS. If the TXT record failed because it went to the wrong place, another method will fail for the same reason.
Verification is usually a short job once someone can see where the DNS is answered. The longer part is often getting back into an account nobody has used in years.
No. The verification record is a TXT record, and TXT records only state facts about your domain. Where your email goes is decided by a different kind of record, the MX records, and verification does not touch them. You can verify the domain today and keep using your current email until you choose to switch.
The switch itself is a separate, planned step: the MX records change once the new mailboxes are ready. Doing that in the right order is what keeps mail from going missing, and it is written up in how long email migration takes.
No, add a new one beside it. A domain can hold several TXT records at the same name, and most business domains already have at least one, usually the SPF record that lists which servers may send your email. Google's verification record sits next to it as its own entry.
The mistake to avoid is pasting the Google value into the existing SPF record. Verification may still fail, and the SPF record is now broken, which can push your outgoing mail toward spam. If that has already happened, our free SPF checker will show it.
Check before you wait. If our DNS lookup already shows the Google value in your TXT records, the record is right and Google will see it soon; waiting and trying again is the whole fix. Google's guide to verifying your domain for Google Workspace covers how long that can take.
If the lookup does not show the value, waiting will not help. The record is in the wrong place or was typed differently, and the steps above find which.
Then that is the real problem, and it is a common one. The nameservers often point at a web host or a Cloudflare account set up by a past web designer or IT person, and the login left with them. Nothing can be verified until someone can edit those records.
The nameserver lookup tells you which company to contact, and the domain registrar can confirm who owns the domain. Getting access back is usually paperwork, not technology, and it is the first thing we sort out when we take on a setup like this.
Business email, files and calendars on your own domain.
Check your mail servers, SPF and DMARC in seconds, explained in plain English.
See if your approved-sender list exists, is valid and protects your domain.
Plain definitions for the records and terms you get asked about.
The safe order for the move, and the traps that cost businesses their email.
Move mailboxes to a new provider without losing mail, with a rollback plan in place.
Tell us what you need and we will map out the simplest path.
Tell us your domain and what Google says. We look up where your DNS is answered, put the record in the right place, and finish the Workspace setup from there.