Facebook domain verification is how a business portfolio proves to Meta that it controls a website domain. You add a meta tag to the homepage, upload an HTML file or create a DNS TXT record, then click Verify in Meta Business Suite. Once it’s verified, you decide who can edit the link previews in ads pointing to that domain.
Older guides give a different reason to verify: ranking 8 conversion events per domain for iOS measurement. That reason has gone. Meta’s Aggregated Event Measurement article now says you don’t need to prioritize 8 events per domain, and that you aren’t required to verify your domains for event configuration. Verification still has work to do, and in lead gen the question that catches people out is which domain to verify when the landing pages don’t live on the main site.
What is Facebook domain verification?
Meta describes it as a way for businesses to claim ownership of their domains in Meta Business Suite without editing Open Graph tags on their websites, and to manage editing permissions over their links and content “in order to help prevent misuse of your domain”. That covers organic and paid content. It’s free, and the verified domain becomes an asset of one business portfolio, which can then share it with partners.
Three Meta features carry the word verification, and they get mixed up all the time:
| What it confirms | How you get it | Verified badge | |
|---|---|---|---|
| Domain verification | that your business portfolio controls a domain | a meta tag, an HTML file or a DNS TXT record | no |
| Business verification | that you’re connected to your business | a code by phone or business email, or domain verification | no |
| Meta Verified for businesses | nothing about domains: it’s a paid subscription with brand protection features | subscribing | yes |
Meta spells out the difference: verifying your business in Meta Business Suite “won’t give you a verified badge”.
Why verify your domain for Facebook ads in 2026?
Event configuration no longer needs it
Meta’s Aggregated Event Measurement article lists these changes to website conversion campaigns:
- you no longer need to prioritize 8 conversion events per domain;
- the Aggregated Event Measurement tab in Events Manager has been removed, because web events no longer need configuring;
- you “aren’t required to verify your website domains for purposes related to event configuration”;
- you don’t select a conversion domain when you create a campaign in Ads Manager.
Meta presents these as changes you’ll see “when you have access”, so an older account can lag behind for a while. The direction is clear, though. A checklist that tells you to verify the domain before you can optimize for leads is out of date: your event setup now comes down to the Meta Pixel and the server, covered in Meta Pixel setup and in custom conversions vs standard events.
What domain verification still controls
Meta’s article on when to use domain verification lists most of the cases, and domain sharing adds one more. Sorted by how much they matter to a lead gen advertiser:
| Use | What verification gives you | For lead gen |
|---|---|---|
| Ad link editing | the list of Facebook Pages running ads that link to your domain, and allow or deny lists for who can edit those link previews | matters as soon as anyone else advertises your landing pages: affiliates, resellers, a former agency |
| Sharing with partners | Partial access or Full control of the domain for a partner’s business portfolio; only verified domains can be shared | the clean way for an agency to work on a client’s domain |
| Business verification | domain verification as proof when you have no business phone number, or your email domain doesn’t match your website | occasionally |
| Organic link editing | editing the previews of organic posts that link to your domain, and letting partners do the same | rarely |
| Webmaster tool | crawl and share counts for your domain, and an allow list of domains that may use your URLs as their canonical URL | rarely |
| Facebook commerce, news Page index | verification is part of onboarding | not relevant |
Link editing is the one to understand. Meta’s developer docs explain that anyone with a Facebook Page can create an ad that links to your domain and, by default, edit the title, description or image shown with the link. Verification is what lets you narrow that down.
What verification doesn’t do matters as much. Meta’s domain verification documentation doesn’t list ad approval or delivery among the reasons to verify, so a verified domain won’t rescue a rejected ad: the landing page still has to pass review, as the guide to a Facebook ad rejected explains.
Verify anyway. It’s free and it takes one DNS record, and the day an affiliate or a former agency runs ads to your landing pages under a preview you didn’t write, the controls are already in place.
How to verify your domain in Business Manager
Business Manager now lives inside Meta Business Suite, and domains sit in the business portfolio’s settings. Meta’s verification steps require a business portfolio, full control of it, and admin or developer access to the domain.
- In Meta Business Suite, open Settings, then Brand safety > Domains.
- Click + Add, then Create a domain. If another portfolio already holds it, choose Request access to a domain instead.
- Enter the root domain with no prefix:
example.com, notwww.example.comorhttps://example.com. - Pick one verification method from the table below and apply it. One is enough.
- Click Verify domain.
| Method | What you do | Where it has to be | Watch out for |
|---|---|---|---|
| DNS TXT record | add the TXT value Meta shows you at your DNS host, with @ in the Host field if your host asks for it | your domain’s DNS records | propagation: usually minutes, up to 72 hours in some cases, according to Meta |
| HTML file upload | download Meta’s verification file and upload it unchanged | the root directory, as example.com/<file>.html | Meta allows only two kinds of redirect: root to www, and between http and https |
| Meta tag | paste <meta name="facebook-domain-verification" content="…" /> into the <head> | the homepage of the root domain, in static HTML | Meta’s crawler doesn’t run JavaScript |
Use the DNS TXT record. It doesn’t depend on a homepage template, a CMS plugin or the next redesign, and it still works when the domain serves landing pages and has nothing on its homepage.
Should you remove the record after verifying?
Meta gives two answers. The Help Center says that once the domain is verified you can remove the meta tag, TXT record or HTML file “and it won’t impact your verification status”. The developer documentation says to leave each of them in place because it “may be checked periodically for verification purposes”. Leave it. A TXT record costs nothing, and the stricter reading can’t hurt you.
Why Facebook domain verification fails
Meta’s troubleshooting article covers the error messages:
| Error | Usual cause | Fix |
|---|---|---|
| Invalid domain | a subdomain, a path, https:// or a trailing slash in the field | enter the root domain only, such as example.com |
| Domain has already been verified by another business | a previous owner or an agency verified it in their own portfolio | ask that portfolio to share the domain with yours |
| No DNS entries were found, or DNS TXT record doesn’t match | the record is missing, hasn’t propagated, or the value was altered | check it with a DNS TXT lookup tool and copy the value exactly |
| Verification file was not found | the file isn’t at the root of the domain | upload it to the root directory |
| Verification file was invalidly directed | a redirect sends Meta’s crawler somewhere else | remove the redirect, or limit it to root-to-www or http/https |
| Verification code doesn’t match | the file was edited or wrapped in other markup, or the tag’s content changed | download the file again, and paste the tag exactly as given |
The meta tag fails for a reason the error message doesn’t spell out: Meta’s crawler doesn’t use JavaScript, so a tag injected by a tag manager or rendered by a JavaScript framework is invisible to it. To check, put the domain into Meta’s Sharing Debugger, open the Scraped URL and search for facebook-domain-verification. Expired certificates that block the crawler show up there too, among the warnings.
Facebook domain verification when landing pages live on a tracking domain
Meta verifies root domains only. Its troubleshooting article says you can’t verify a subdomain or a subdirectory, and that “when you verify a domain, you also get control of all subdomains”. The one exception it lists is selling on Facebook commerce.
So the answer depends on where your landing pages sit, which in lead gen is often not the main site. A tracking domain that serves landing pages is usually a subdomain of the brand’s site or a separate domain bought for campaigns.
| Where the landing pages live | What you verify | Notes |
|---|---|---|
The main site, such as example.com/offer | example.com | nothing else to do |
A subdomain of your domain, such as go.example.com | example.com | covered; you can’t verify go.example.com on its own |
A separate domain you own, such as example-quotes.com | example-quotes.com, as a domain of its own | use the DNS TXT record if it has no homepage |
A shared subdomain on a builder’s domain, such as yourbrand.builder.example | nothing | the root domain belongs to the builder, and Meta only verifies root domains |
| A client’s domain, run by an agency | the client’s root domain, in the client’s portfolio | the client shares it with the agency’s portfolio |
The fourth row is the one to fix if link editing matters to you: move the landing pages to a domain you own. And since link editing applies to ads that link to your domain, it’s simplest when the URL in the ad sits on the domain you verified, with no redirect through someone else’s domain in between.
DropCPL logs the click on the same domain that serves your landing page, so no redirect domain sits between your ad and the domain you verify. The first-party cookie is set server-side in the same response that renders the landing page. Start free →
Agencies: verify in the client’s portfolio, then share
Meta’s developer docs carry a warning for agencies: verify a client’s domain in the domain owner’s Business Manager, and let the owner share access with yours afterwards. An agency that verifies a client’s domain in its own portfolio leaves the “already verified by another business” error for whoever comes next, the client included.
The client shares it from Brand safety > Domains: select the verified domain, click Assign partner, enter the agency’s business portfolio ID and choose Partial access or Full control. Meta’s sharing article notes that sharing a domain “doesn’t give your partner ownership”, and that access can be removed at any time.
Two details of link editing affect agencies directly:
- Only the verifying portfolio sets the lists. If the domain was shared with you, the allow and deny lists stay in the portfolio that verified it.
- An allow list needs matching shares. If the client picks Allow only specific advertisers, only the Facebook Pages on the list can edit link previews in ads to the domain, and Meta’s link editing article advises sharing the domain with those advertisers “to avoid any issues with publishing an ad”. Changes can take up to 24 hours.
If you manage several clients, keep each client’s landing pages on that client’s domain. Verification and link controls then belong to the business that owns the brand, and they stay with it if the agency changes. First-party tracking covers why the click should be logged on that same domain too.