How to Connect a Custom Domain to Your Page Builder

A site isn't a page (and mixing them up trips everyone up)

Connecting a custom domain to your page builder takes less than 10 minutes: you create the site on the server, point the www CNAME over at the registrar where you bought the domain, wait for propagation, then publish the page with SSL. The bottleneck isn't technical. It's understanding the difference between a site and a page, which is where most people get stuck.

Before you touch DNS, hold on to this distinction:

Site is your domain. The address up top in the browser, the www.yourdomain. It's the container.

Page is what you publish inside that site. The sales page, the opt-in, the upsell. The content.

Anyone who runs this knows it sounds obvious on paper, but when it's time to set up, people try to publish the page expecting the domain to show up on its own. It won't. First you establish the site on the server, then connect the domain to the site, and only then publish the page on that address.

How do you create the site on the server?

When you open an account on the platform, you already have the option to create a site. Go to the sites menu and create one.

The name here doesn't matter. It can be any word, anything. This name only serves to make sure there's an active domain on the server, a reserved space for you. If you click on it, you'll see the screen already active, just empty. Nothing published yet.

It comes with a random URL, something generic the platform generates automatically. Nobody wants to run traffic to that ugly address. You want your clean domain. That's what the next step is for.

Connecting the domain to the site

In the listing for the site you just created, look for the clip icon next to the trash can. That's where you connect the domain.

Click it and type your domain. Important point: put www in front. The www subdomain is active by default, so the address you'll connect is www.yourdomain. Type it and click connect.

As soon as you connect, the platform shows you a task to complete: the pointer record. It generates a pointer value you need to copy. This value tells your domain where it should respond. Copy that pointer, because now the work moves off the platform and over to the registrar where you bought the domain.

How do you set up DNS at the registrar?

Open the panel at the registrar where you registered the domain. The path has a different name depending on the company, but the logic is always the same.

You look for the domains section, find your domain in the list, click manage, and go into the DNS area. Inside DNS, scroll until you find the CNAME record for WWW. That's the one that matters. That's what you'll edit.

Open the edit view and swap the target. The wording varies a ton between registrars. The field you need to change might show up as:

• target
• object
• content
• value

Whatever it's called, that's the field where you paste the pointer you copied from the platform. Paste it exactly as it came, without adding anything.

There's one more field to check: TTL. Some registrars need you to enter 14400. Others use a different number, or it comes pre-filled with the default. If the panel didn't ask you to set the TTL, it pulled it automatically and you don't need to touch it. Save the change and done, the record is updated.

To sum up what you changed: the WWW CNAME, swapping the target for the platform's pointer. That's it. Copy from the platform, paste at the registrar.

Propagation: why doesn't it work right away?

Go back to the platform and click verify. If you get "not found," relax. That's normal and it's not your fault.

The change you made to DNS needs to spread across the internet. This process is called propagation, and it takes time. In most cases it runs 5 to 15 minutes. Some registrars take a bit longer, depending on their infrastructure.

What you do in that window is simple: keep clicking verify every so often until it works. Wait a few minutes, verify again. When it takes a little while to respond like this, it's usually a sign things worked and propagation is happening. It tends to resolve in under 10 minutes. You'll see the hostname added successfully message, and that random name disappears. Your domain is there in its place.

SSL comes included

As soon as the domain connects, notice the green padlock next to the address. That's the SSL, the security certificate, and the platform issues it for free.

You don't need to buy a separate certificate or configure anything. It goes up automatically along with the domain connection and is ready to use. This matters because Meta rejects ads pointing to a page without HTTPS, and a checkout without a padlock kills conversion on the spot. With SSL active, the page is secure from the very first visit.

Publishing the first page on the domain

Now that the site (your domain) is connected and secure, the page comes in.

You open one of your pages and click publish. The domain you just connected already shows up there as the destination, without you having to type anything again. Publish, wait a few seconds, and the page is live, running on your own address, with SSL.

From zero to a connected domain with a published page: under 10 minutes. The heavy lifting was one line of DNS.

One note for anyone running volume: connecting a domain is easy. The friction shows up when you need to launch dozens of pages and campaigns in parallel after the funnel is ready. Operators running several offers at once handle the bulk publishing side on Meta with platforms like DirectAds, which launches hundreds of campaigns across multiple accounts without redoing manual setup. The connected page is just the start of the funnel. The ad volume on top of it is where the time disappears.

Takeaways

• Separate site from page in your head: the site is the domain, the page is the content. Create the site first, connect the domain, then publish.
• Edit the WWW CNAME at your registrar: paste the platform's pointer into the target field (or value, object, content) and save.
• Don't panic over "not found": propagation takes 5 to 15 minutes. Keep verifying until the host added message appears.
• Check for the green padlock before running traffic. Without SSL, Meta rejects the ad and checkout loses conversion.

Frequently asked questions

Do I need to put www in the domain or does it work without it?

In the default setup, the www subdomain is active, so you connect it as www.yourdomain and edit the WWW CNAME at the registrar. That specific record is the one that receives the pointer.

How long does domain propagation take?

In most cases, 5 to 15 minutes. Some registrars take a bit longer. You just need to click verify every so often until the platform recognizes the change.

What do I put in the TTL field?

At some registrars you set 14400. At others the value is already pre-filled with the default or pulled automatically. If the panel didn't ask you to choose the TTL, leave it as is.

Does SSL cost anything?

No. The security certificate is issued for free by the platform and goes up automatically when the domain connects. You don't need to buy or configure anything separately.

My CNAME isn't in the DNS list, now what?

If there's no WWW CNAME record, you create a new one instead of editing. Set the host to www and paste the platform's pointer into the target or value field. The effect is the same.