You open Events Manager to set up conversion tracking and hit a wall: “You need to verify your domain.” Or you try to edit the headline on a link preview and find the option greyed out. Or your conversion events simply refuse to configure, with no clear reason why.
Domain verification is the step almost nobody sets up until something forces them to. It takes about ten minutes when you know which method to use, and it can eat a whole afternoon when you don’t — usually because of one small detail that nobody mentions.
This guide covers what domain verification is, the three ways to do it, which one you should actually choose, and the mistakes that keep a domain stuck on “Unverified” no matter how many times you click the button.
Domain verification is not business verification
This trips up a lot of people, so it is worth settling first.
Business verification proves your company is real, using registration documents. If yours has been rejected, we covered that separately in why Meta business verification gets rejected.
Domain verification proves you control a website. No documents involved — you prove it by placing something on the domain that only its owner could place.
They are separate processes, in separate parts of the interface, and passing one does not grant the other. Most advertisers eventually need both.
What domain verification unlocks
- Configuring conversion events. Since Apple’s tracking changes, Meta limits you to eight prioritised conversion events per domain — and you cannot configure them at all until the domain is verified.
- Editing link previews. Changing the headline, description or image on a shared link requires verification.
- Protecting your domain. Verification claims the domain to your business portfolio so another business cannot use it in their ads.
- Cleaner attribution. Verified domains give Meta more confidence in the events you send, which matters for conversion campaigns.
If you run traffic to your own website and care about what happens after the click, this is not optional.
The three methods, and which to choose
Meta offers three ways to prove you own a domain. All three work. They differ in how likely you are to break something.
1. DNS TXT record — recommended
You add a text record to your domain’s DNS. It survives site redesigns, theme changes, plugin removals and migrations, because it lives with your domain rather than inside WordPress.
This is the method we use for clients, and the one we recommend. If you have ever added an SPF or DMARC record for email, this is the same job.
2. HTML file upload
You download a small file from Meta and upload it to your website’s root directory. Simple in principle, but it requires file access, and the file gets wiped surprisingly often — by migrations, security plugins, or a host restoring from backup.
3. Meta tag
You paste a tag into your site’s <head>. Easy on WordPress, but it disappears the moment you change themes or remove the plugin holding it. We see this one break most often.
Choose DNS if you have access to it. Choose the meta tag only if you cannot reach your DNS, and if you do, put the tag somewhere theme-independent.
Method 1: DNS TXT record (step by step)
- In your business portfolio settings, open Brand Safety and Suitability → Domains. Meta relocates this occasionally, so search the settings for “domains” if it isn’t where you expect.
- Click Add and type your domain without
https://and withoutwww— justyourbusiness.com. - Choose the DNS TXT record tab. Meta shows a verification string beginning
facebook-domain-verification=. - Log in to your hosting control panel and open the Zone Editor (cPanel) or your DNS provider’s dashboard.
- Add a record of type TXT. For the name or host, enter your root domain, or
@if your panel uses that convention. Paste Meta’s full string as the value. - Save, then wait. Changes are often visible within minutes but can take a few hours.
- Return to Meta and click Verify.
Two details that cause most DNS failures:
Do not create a subdomain by accident. Some panels append your domain automatically to whatever you type in the name field. If you type yourbusiness.com and the panel appends the domain again, you end up with a record on yourbusiness.com.yourbusiness.com, which verifies nothing. After saving, check what the panel actually stored.
Paste the whole value as one string. If your panel offers an “add another TXT string” option, ignore it. Splitting the value across two strings breaks it.
Method 2: HTML file upload
- Download the HTML file Meta provides.
- Upload it to your site’s root directory — the folder containing
wp-config.php, usuallypublic_html. Use cPanel’s File Manager or FTP. - Confirm it loads by visiting
yourbusiness.com/followed by the filename. You should see a line of text, not a 404. - Click Verify in Meta.
Do not rename the file, do not put it in a subfolder, and do not delete it afterwards — Meta rechecks periodically, and removing the file can un-verify your domain months later.
Method 3: Meta tag on WordPress
Meta gives you a tag that must appear in the <head> of your homepage.
The safe way to add it on WordPress is through a header-and-footer code plugin, or Yoast’s webmaster-tools section if you use Yoast. What you should not do is paste it directly into your theme’s header.php — the next theme update will overwrite it, and the next theme change will erase it entirely.
After adding it, view your homepage source and search for facebook-domain-verification. If it isn’t there, caching is the usual culprit — clear your cache before clicking Verify.
Why verification fails when you have done everything right
You verified the wrong version of the domain. Enter the root domain only. Not www., not https://, no trailing slash, no path. Verifying the root covers your subdomains; verifying www.yourbusiness.com as though it were separate causes confusion.
Caching is serving Meta an old page. If you used the meta tag method, your cache may be showing Meta a version of the homepage from before you added it. Clear every layer — site cache, and any CDN in front of it.
DNS has not propagated yet. Give it a few hours before deciding it failed. Repeatedly clicking Verify does not speed this up.
Another business portfolio already claimed the domain. A domain can only be verified in one portfolio at a time. If an agency or a former developer verified it under their own portfolio, you will need them to release it. This is worth checking early, because no amount of correct setup will get past it.
You are looking in the wrong portfolio. If you have access to several, confirm you are adding the domain to the one that actually owns your ad account and pixel.
After verification: prioritise your events
Verification is not the finish line. Once the domain shows as verified, open Events Manager and configure your Aggregated Event Measurement settings — the eight conversion events for that domain, ranked by importance.
Order matters. Meta reports the highest-priority event a user triggers, so your most valuable action belongs at the top. For most businesses that is a purchase or a completed lead, not a page view. If you are unclear on which events you should be sending, our guide to standard events and custom conversions covers how to choose them.
Frequently asked questions
Do I need domain verification if I only boost posts?
If you never send traffic to your own website and never track conversions on it, you can operate without it. The moment you run conversion campaigns to your site, you need it.
Can I verify a domain I do not own, like a Linktree or Shopify subdomain?
Only if the platform lets you add DNS records or files at that domain, which most shared platforms do not. On a subdomain of someone else’s domain, verification generally belongs to whoever controls the root.
How long does verification last?
Indefinitely, as long as the proof stays in place. Remove the DNS record, delete the file, or drop the plugin holding the meta tag, and the domain can revert to unverified.
Can two businesses verify the same domain?
No. One domain, one verified portfolio at a time.
I verified my business already. Why is my domain still unverified?
Because they are separate processes. Business verification checks your company documents; domain verification checks website control. Completing one never completes the other.
Does verification fix a restricted ad account?
No. Restrictions follow a different process entirely.
If it will not verify
Most domain verification problems come down to a record saved on the wrong hostname, a cache serving stale HTML, or another portfolio already holding the claim. All three are quick to identify once you know to look for them, and genuinely difficult to spot if you don’t.
If your domain has been sitting on “Unverified” and you have tried more than once, book a one-on-one session and we will check your DNS, your portfolio and your site together and find what is blocking it. We never ask for your Facebook password.
You may also find our guides on setting up a Business Portfolio and passing business verification useful, or take a look at our Facebook and Instagram Ads services if you would rather hand the whole setup to us.