Ad review, policies and account issues

Why is Facebook domain verification not working?

Six error messages explain nearly every failed domain verification, and one failure comes with no message at all. Here is how to find and fix each one.

Published

Domain verification usually fails for one of six reasons Meta names in its own error messages, and the message tells you which. A seventh failure comes with no message at all: a tag that exists in the browser but not in the HTML Meta’s crawler reads. Read the error, fix that one thing, and retry the same method rather than switching methods at random.

Start with the exact error

Open the business portfolio settings, then Brand safety and Domains, and read the status next to the domain rather than the general message in the notification. Meta’s troubleshooting article maps its errors to causes, and the mapping is narrow enough to act on:

What Meta saysUsual causeFix
Invalid domaina subdomain, a path, https:// or a trailing slash in the fieldenter the root domain only, such as example.com
Domain has already been verified by another businessa previous owner or an agency verified it in their own portfolioask that portfolio to share the domain with yours
No DNS entries were found, or the TXT record does not matchthe record is missing, has not propagated, or its value was alteredcheck it with a DNS TXT lookup and copy the value exactly
Verification file was not foundthe file is not at the root of the domainupload it to the root directory, unchanged
Verification file was invalidly directeda redirect sends Meta’s crawler somewhere elseremove the redirect, or keep it to root to www or http to https
Verification code does not matchthe file was edited or wrapped in other markup, or the tag content changeddownload the file again and paste the tag exactly as given

Two of these are worth slowing down for. A DNS record that has not propagated looks identical to one that was never added, so give it time and confirm with a lookup tool before changing anything. And a value copied through a chat window or a screenshot is a frequent source of the mismatch error, because the string is long and case sensitive.

The failure with no message

Meta’s crawler does not use JavaScript. A tag injected by a tag manager, or rendered by a JavaScript framework in the browser, is invisible to it, even though the page source in your browser shows it. That single fact explains most of the reports where the tag is visibly present and verification still fails.

To check what Meta sees, put the domain into Meta’s Sharing Debugger, open the scraped URL and search the result for facebook-domain-verification. If it is not in that output, Meta cannot see it either. Expired certificates that block the crawler also appear there, among the warnings.

Method by method

One method is enough, and each has one requirement people miss:

Meta tag. It goes in the <head> of the homepage of the root domain, in static HTML. Not in the footer, not on a landing page, not inside a client-side render.

HTML file. It goes in the root directory, so that example.com/<file>.html resolves, and the file must be untouched. Meta allows only two kinds of redirect for this method: root to www, and between http and https.

DNS TXT record. The value goes at your DNS host, with @ in the Host field if the host asks for it. It is the method that survives a redesign, a CMS change and a homepage that serves nothing, which is common when a domain exists only to host campaign landing pages.

Keep the record, file or tag in place after verifying. Meta’s Help Center says removing it does not affect the status, while its developer documentation says the marker may be checked periodically. A TXT record costs nothing, so leaving it avoids the argument.

When the domain sits in the wrong portfolio

A verified domain becomes an asset of one business portfolio. If another portfolio already holds it, the button to look for is not Create a domain but request access, and the owner has to grant it. This is where agencies create their own problem: verifying a client’s domain inside the agency portfolio leaves the already verified error for the client and for whoever comes next.

The correct order is the reverse. The client verifies the domain in the portfolio that owns the brand, then shares it from Brand safety and Domains with the agency portfolio, choosing Partial access or Full control. Only verified domains can be shared, and the portfolio that verified it keeps the allow and deny lists for who may edit the link previews.

If the domain is shared with you, two things follow. You cannot set those lists. And if the owner picks an allow list, the advertisers on it need the domain shared with them as well, which Meta recommends for publishing without issues. Changes to the lists can take up to 24 hours.

What verification does not fix

It does not approve an ad. Meta’s documentation does not list ad approval or delivery as a reason to verify, so a verified domain will not rescue a rejected ad; the landing page still has to pass review, and the reasons are in Facebook ad rejected.

It also no longer affects event setup. Meta’s Aggregated Event Measurement article says you are not required to verify your domains for event configuration, the tab for prioritizing events has been removed, and you no longer pick a conversion domain when creating a campaign. Guides that tell you to verify before optimizing for leads are out of date. What is left is link editing and domain sharing, which matter the day an affiliate, a reseller or a former agency runs ads to your landing pages.

Checklist before you retry

  • Is the domain in the field a root domain, with no subdomain, path or scheme?
  • Does the error name a different portfolio as the owner?
  • Is the marker in the static HTML or in DNS, not injected by a script?
  • Has the record propagated, and does the value match character by character?
  • Is there a redirect in front of the file, beyond root to www or http to https?
  • Did you retry the same method, rather than switching three times?

Domain verification is free, and it takes one record. Where the landing pages live decides what you verify: a subdomain of your domain is covered by the root, a separate domain needs its own verification, and a subdomain on a builder’s domain cannot be verified at all. That last case is worth a structural fix rather than a workaround, which is why a tracking domain you own is the setup described in Facebook domain verification. DropCPL serves the landing page from the same domain that logs the click, so no redirect domain sits between the ad and the domain you verify.

The remaining account problems that stop a campaign are in ad review, policies and account issues, and a verified ad that still will not spend is covered in Facebook ads not delivering.

Questions on this topic

All questions on this topic →

FAQ

Why does Meta say my domain is invalid?+

The field takes a root domain and nothing else. A subdomain, a path, https:// in front or a trailing slash all produce the invalid domain error. Enter example.com, and rely on the fact that verifying a root domain also covers its subdomains.

Why is my meta tag there but still not detected?+

Because Meta's crawler does not run JavaScript. A tag injected by a tag manager, or rendered by a JavaScript framework on the client, is invisible to it even though you can see it in the browser. It has to be in the static HTML of the homepage, in the head.

How long should I wait after adding a DNS TXT record?+

Meta says propagation is usually minutes and up to 72 hours in some cases. Check the record with a DNS TXT lookup before retrying, and compare the value character by character, because an altered or truncated value produces the same not found error as a missing record.

Can I verify a domain someone else already verified?+

Not directly. The domain belongs to the portfolio that verified it, so the owner has to share it with your portfolio, with Partial access or Full control. That also means an agency should never verify a client domain in its own portfolio.

Does verifying my domain help a rejected ad?+

No. Meta does not list ad approval or delivery among the reasons to verify, and a rejected ad is about the ad, the targeting or the landing page content. Verification controls who can edit the link previews for that domain.

Ready to find out what
converts, for real?

Free to start.

Start free →