Google Search Console, Google Workspace, Microsoft 365, Facebook Business Manager — sooner or later almost every site owner gets asked to "verify domain ownership" by adding a TXT record. It sounds simple. In practice, we get a steady stream of tickets from customers who added the record exactly as instructed and the platform still says it can't find it. Here's what's actually going wrong and how to fix it on a SkyServer cPanel account.
Symptom: "We Couldn't Verify Your Domain" or "TXT Record Not Found"
You paste a string like google-site-verification=abc123XYZ or MS=ms12345678 into a TXT record, hit save, then click "Verify" on Google/Microsoft/Facebook's side. Instead of a green check, you get some version of:
- "We couldn't find the domain verification record."
- "This may take some time to update. Try again later."
- "No TXT records found for this domain."
The frustrating part is that if you run a DNS lookup yourself, the record is often right there. So why can't the platform see it?
The Usual Causes
1. You edited DNS in the wrong place
This is the number one cause. Your domain's DNS can live in one of two places: your domain registrar's DNS panel, or cPanel's Zone Editor (which only matters if SkyServer's nameservers are actually assigned to the domain at the registrar). If you added the TXT record in cPanel but the domain still points to your registrar's default nameservers — or the reverse — you edited a zone nobody is actually reading.
Check which nameservers are authoritative before touching anything:
dig NS yourdomain.com +shortIf that returns your registrar's nameservers (like ns1.godaddy.com) but you edited the zone in cPanel, that's your problem right there.
2. Record added to the wrong host
Verification TXT records almost always belong on the root/apex of the domain, not on www or any subdomain. In cPanel's Zone Editor, the "Name" or "Host Record" field should be your domain itself (or left blank / set to @, depending on the interface) — not www.yourdomain.com.
3. Extra quotes or whitespace in the value
Some registrar and cPanel interfaces auto-wrap TXT values in quotes; others expect you to type the quotes yourself. If you paste "google-site-verification=abc123" including the quote marks into a field that already adds its own quotes, you end up with a record whose value is literally ""google-site-verification=abc123"", which no longer matches what Google is looking for. Trailing spaces cause the same silent failure.
4. Old TTL still cached
DNS resolvers cache records for the length of the TTL (time-to-live). If the zone had a 24-hour TTL before you made the change, some resolvers — including the ones the verification service itself uses — may still be serving the stale (missing) answer for hours.
5. You clicked Verify before propagation finished
Even with a correct record, DNS changes don't apply everywhere instantly. Google, Microsoft, and Facebook usually retry automatically, but clicking "Verify" once and giving up when it fails is a very common false alarm.
6. Conflicting or duplicate TXT records
You can have multiple TXT records on the same host, but if a previous automated tool created a syntactically broken one, or your SPF record and the verification record got merged into a single line by mistake, some validators choke on it. Each value needs its own, separate TXT entry.
The Fix: Adding the Record Correctly in cPanel
- Log in to cPanel and open Domains → find your domain → click Manage, or go directly to Zone Editor under the Domains section.
- Next to the correct domain, click Manage, then Add Record and choose TXT.
- In the name/host field, enter your domain name or leave it as the default root value shown by cPanel — do not add
www. - Paste the verification string exactly as given by Google/Microsoft/Facebook, with no extra quote marks and no leading or trailing spaces.
- Set TTL to something short while you're testing, like 300 (5 minutes), so future edits propagate fast. You can raise it back to 14400 or higher once verification succeeds.
- Save the record.
Then confirm it's actually visible from the outside before clicking Verify on the platform:
dig TXT yourdomain.com +shortYou should see your new value in the output, quoted by dig itself (that's normal — those are output-formatting quotes, not part of the stored value). If nothing shows up after 10–15 minutes, re-check the nameserver question from cause #1 before doing anything else.
Quick Reference: Common Verification Providers
| Service | Typical TXT prefix | Host field |
|---|---|---|
| Google Search Console / Workspace | google-site-verification= | Root domain (@) |
| Microsoft 365 / Entra ID | MS=ms12345678 | Root domain (@) |
| Facebook Business Manager | facebook-domain-verification= | Root domain (@) |
| Adobe / other SaaS tools | Varies, always shown on-screen | Root domain (@) unless stated otherwise |
Always copy the exact string the platform shows you at that moment — verification tokens are unique per account and per attempt, and an old one from a previous signup attempt won't work.
Prevention
- Before adding any new DNS record, run
dig NS yourdomain.com +shortto confirm you're editing the zone that's actually live. - Keep a simple log (even a text file) of every verification TXT record you've added and what it's for — SPF, DKIM, Google, Microsoft, Facebook, Pinterest, whatever. It saves a lot of guesswork later when you're cleaning up DNS and wondering if a record is safe to delete.
- Don't remove a verification TXT record after the initial check passes — some services (Google Workspace especially) re-verify periodically, and removing the record can silently break your account access down the line.
- If you use Cloudflare or another DNS provider in front of SkyServer, make sure you're adding the record in the DNS panel that's actually authoritative, not in cPanel's Zone Editor which would be ignored in that setup.
- If DNSSEC is enabled on the domain, double-check the zone signs correctly after edits — a broken DNSSEC chain can cause some validators to reject the whole zone, not just the new record.
Frequently Asked Questions
Can I use cPanel's Zone Editor if my domain uses Cloudflare DNS?
No. If Cloudflare's nameservers are assigned at your registrar, Cloudflare's dashboard is the authoritative source, and cPanel's Zone Editor changes won't be seen by anyone outside your server. Add the TXT record in Cloudflare's DNS tab instead.
How long should I wait before trying "Verify" again?
Give it at least 15–30 minutes after saving the record, especially if the previous TTL on that zone was high. If it still fails after an hour, re-check the record's host field and value character-by-character rather than just waiting longer.
Can I delete old verification TXT records I no longer need?
Only if you're certain the service no longer checks for it. Google Search Console and Workspace can silently drop access if the record disappears and a periodic re-check fails. When in doubt, leave it.
Why does dig show my record but the platform still can't find it?
The most common reason is that the platform's verification service is hitting a different, cached answer than your terminal is. Try querying a public resolver directly, like dig @8.8.8.8 TXT yourdomain.com, to see what Google's own infrastructure sees.
Can I add more than one TXT record to the same domain?
Yes. TXT records are cumulative on a host — you can have SPF, Google verification, Microsoft verification, and Facebook verification all on the root domain at once, as separate entries. Just don't merge multiple values into a single TXT line.
