Domain verification in Business Manager confirms that your business controls a website domain. It usually takes a few minutes when you can edit DNS, upload a file, or change the site’s HTML. The fastest method is normally a DNS TXT record, but Meta also supports an HTML file or a meta tag. The right choice depends on who controls your website and DNS. Verification doesn’t prove everything, and you’ll also need to know which settings it unlocks and when a different business portfolio should own the domain.
What domain verification does
Domain verification links a website domain to a Meta business portfolio. It tells Meta that someone with control of the domain has approved its use. The domain can then support business assets such as Facebook Pages, Instagram accounts, ad accounts, catalogs, and related website settings.
The process is mainly for businesses that advertise, manage several brands, or share website assets with different people and teams. It can help control who may edit website links in ads and can support Meta’s website event settings. It’s also useful when a company needs a clear owner for a domain instead of leaving control with an individual employee.
Verification does not mean Meta has checked your business, approved your products, or secured your website. It also doesn’t replace HTTPS, a trademark registration, DNS security, or access controls inside your hosting account.
The common misconception is that adding a domain inside Business Manager proves ownership by itself. It doesn’t. Meta needs a matching proof, such as a DNS record, an uploaded verification file, or a meta tag on the live website.
Meta’s interface may use names such as Business Settings, Business Portfolio Settings, or Brand Safety. The labels can change by account, but the domain must be added to the correct business portfolio before you verify it. If it’s added to the wrong portfolio, the proof may work technically while the wrong team receives control.
How to verify a domain in Business Manager
Before you start, choose the business portfolio that should own the domain. You’ll need administrator access to that Meta portfolio and access to either the domain’s DNS, the website files, or the site’s HTML editor.
-
Open Meta Business Settings or Business Portfolio Settings, then go to Brand Safety and Domains. Select Add, enter the root domain such as
example.com, and save it. Don’t addhttps://, a page path, or an email address. -
Open the domain record in Meta and choose a verification method. Use DNS verification if you can edit DNS. Choose an HTML file or meta tag only when you control the website but not its DNS.
-
For DNS verification, copy Meta’s TXT value exactly. In your DNS provider, create a TXT record for the root domain, often shown as
@, and paste the value into the record field. Leave the TTL at the provider’s default unless your provider gives a different required setting. -
For an HTML file, download Meta’s supplied file and upload it to the top-level website folder. The file must open at the exact URL Meta shows, not inside a subfolder or behind a login. For a meta tag, paste the full tag inside the website’s
<head>area. -
Publish the DNS record, file, or tag. If you use a content management system, clear its cache only when the system requires it. Don’t edit Meta’s token, add quotation marks, or change the file name.
-
Return to the domain in Meta and select Verify. DNS changes may not appear immediately, so retry later if the record is correct. Check the record with your DNS provider before changing it again.
-
After verification, review the domain’s assigned people, partners, Pages, ad accounts, and other assets. Give access only to the business assets that need it, and remove old partners or employees.
The main judgment call is ownership. If your company controls DNS, use the TXT method; if a web agency controls DNS but you control the site, use the HTML file or meta tag. A freelancer, developer, or IT administrator can do the technical change, but don’t give them full business access just to add one record.
Domain verification settings at a glance
These settings cover the main paths, but your DNS provider and website platform may use different field names.
| Situation | What to use | How long | What to watch for |
|---|---|---|---|
| You control DNS | Meta TXT record | Until Meta detects it | Use the root domain and copy the value exactly |
| An agency controls DNS | HTML file | Until Meta detects it | The file must stay at Meta’s exact public URL |
| You control site HTML | Meta tag | Until Meta detects it | Keep the tag inside the live page’s <head> |
| The domain has subdomains | Add the root domain first | One setup per business need | shop.example.com and example.com may be treated differently |
| A redirect is active | Verify the final live domain | After the record is published | A redirect doesn’t replace proof of control |
| Several businesses use the domain | One clear owner | Depends on the business setup | Use partner access instead of duplicate ownership |
| The site uses a CDN or proxy | DNS TXT record | After DNS publishes | Add the record at the authoritative DNS provider |
If the domain is already verified by another business, don’t delete its proof without checking ownership. The business that controls the domain should decide which portfolio owns it and how other teams receive access.
Details that prevent failed verification
Start by writing down the exact root domain, the business portfolio ID or name, and who controls DNS. This avoids a costly mix-up between example.com, www.example.com, and a country-specific domain. Check the domain in a normal browser before you choose the file or tag method.
Work in this order: add the domain, copy the proof, publish it, verify it, then assign assets. Don’t assign Pages or ad accounts first and assume that assignment verifies the domain. Meta’s proof and the asset permissions are separate steps.
Check the record from your DNS provider’s own control panel, not only from a browser. A TXT record won’t appear as a normal web page. If your provider automatically adds the domain name to the host field, entering the full domain can create a duplicated name and make the record fail.
Leave the proof in place after verification. Removing a TXT record, deleting the HTML file, or changing the meta tag can cause future checks to fail. The mistake costs time and may interrupt domain-dependent advertising settings while your team proves control again.
If Meta reports that the domain is already owned, stop before trying random methods. Confirm which business portfolio owns it, then ask that portfolio’s administrator to transfer control or add your business as a partner. If neither team can establish ownership, use Meta’s support process rather than changing another company’s DNS.
Domain verification problems and fixes
The message you see usually points to the next safe check. Don’t keep changing records when the domain or business portfolio is wrong.
| What you notice | What it usually means | What to do first |
|---|---|---|
| Meta can’t find the TXT record | The record is missing, mistyped, or published elsewhere | Check the authoritative DNS provider and copy the value again |
| The HTML file can’t be found | The file is in the wrong folder or blocked | Open Meta’s exact file URL in a private browser window |
| The meta tag fails | It isn’t in the live page head or was removed by the site builder | View the published page source and confirm the full tag |
| The domain is already verified | Another business portfolio controls it | Identify that portfolio and request transfer or partner access |
| Verification works, then fails later | The proof was removed or the domain changed | Restore the same proof and confirm the root domain is unchanged |
| The button stays unavailable | You may lack portfolio admin rights | Ask a business administrator to add or verify the domain |
A DNS lookup tool can help confirm a TXT record, but it can’t grant Meta permission. If the record is visible and exact yet Meta still rejects it, use Meta Business Support or ask the DNS provider to confirm which nameservers are authoritative.
Meta rules and access limits
Meta requires a person with the right business permissions to add or verify a domain. Being an administrator of a website, Facebook Page, or ad account doesn’t automatically make you an administrator of the business portfolio.
Meta’s Business Help Center publishes the current requirements and interface guidance for domain verification. Check that guidance when the menu names or supported verification options differ from the ones shown in your account.
A domain can’t safely be treated as a shared free-for-all. The business that controls the domain should own it in Meta, while agencies and related companies should receive partner access. This keeps asset control separate from day-to-day campaign work.
You shouldn’t change DNS, website code, or business ownership without authorization. If the next step could affect email, website traffic, advertising rights, or another company’s assets, send it to the domain owner, IT administrator, or Meta Business Support instead.
Keep the verification active
Leave the TXT record, HTML file, or meta tag in place after Meta confirms the domain. Verification isn’t a reason to remove the proof. Keep a note of the domain owner, the business portfolio, the chosen method, and the person who can restore it.
Review the entry when your company changes its DNS provider, website platform, hosting account, or business structure. Those changes can remove a record or file even when the website still loads normally.
If verification stops working, restore the original proof before creating a new one. If you can’t find the old value, open the domain in Meta and follow the currently displayed method. Don’t copy a token from a different domain or portfolio.
There’s no reliable universal renewal interval for this process. The point at which it needs attention is a failed verification check, a changed domain setup, or a warning in Meta—not a fixed calendar date.
When domain verification isn’t right
Domain verification is wrong when you don’t control the website or DNS, or have no agreement with the owner. This commonly applies to an agency, contractor, or partner working for a client. Ask the owner to verify it in the correct Meta business portfolio, then give your company the partner access it needs. Don’t add a DNS record or upload a verification file without the owner’s authorization.
It’s also wrong when the goal is to prove legal trademark ownership. Verification tells Meta that a business can control the domain; it doesn’t decide who owns the name or mark. For trademark rights, check the relevant trademark office and speak with a qualified legal adviser. If the issue is a brand dispute, keep registration records, assignments, and other ownership documents rather than treating domain access as proof.
Don’t use verification to repair a hacked website, recover an expired domain, or correct broken DNS. Restore security and domain control first, then verify the clean, live domain after confirming it resolves normally. If companies dispute the domain, stop token attempts. Have whoever controls it contact Meta Business Support; tokens won’t settle ownership disputes.
Frequently asked questions
Can I verify a domain without access to DNS?
Yes, you can use Meta’s HTML file or meta-tag method when you control the live website. The file must be publicly reachable at the exact path Meta provides, while the tag must remain in the page head. If an agency manages both your site and DNS, ask it to add the proof while your business administrator keeps control of the Meta portfolio.
Why does Meta say my domain is already verified?
Meta says this when another business portfolio has already claimed the domain. First, identify the portfolio owner and check whether it belongs to your company, an old agency, or a former employee. Don’t remove records blindly. The current owner may need to transfer the domain, or it may need to give your business partner access.
How long does domain verification take?
DNS verification can take from a short time to longer, depending on when the authoritative DNS servers publish the TXT record. Website-file and meta-tag checks can work soon after the page is publicly available. If the proof still fails after the record or page is clearly correct, check the root domain and contact Meta Business Support.
Is it safe to leave Meta’s TXT record in DNS?
Yes, leaving the verification TXT record is normally the correct choice. It doesn’t replace your website’s security controls, and it should contain only the value Meta supplied. Don’t publish a token from another business or domain. Ask your DNS administrator to review it if you’re unsure which records are active.
What happens if I remove the verification record?
Meta may no longer be able to confirm that your business controls the domain. Domain-dependent permissions or settings can then become harder to manage, especially after a later review. Restore the original TXT record, file, or tag first. If you can’t recover it, generate the current proof in Meta and verify again.
Can two businesses verify the same domain?
One business should normally keep clear ownership while other companies receive access through Meta’s partner tools. Two companies trying to claim the same domain can create an ownership dispute and block the team that needs the asset. If the businesses are related, document who owns the domain and let that owner manage verification.
Conclusion
After verification, review your business portfolio’s domain ownership, assigned assets, and approved traffic settings. Keep DNS and website access documented, especially if your agency or developer manages them. If your business structure changes, update ownership promptly so advertising, brand protection, and future integrations don’t depend on outdated permissions.
Olivia Jones
Contents
Need help with your Facebook setup?
We set up profiles, Business Managers and ad accounts the right way.
See our services →