Publishing a Landing Page to Your Own Domain

Every landing page builder will publish to a domain you control, and every one of them counts that allowance differently. Three phrases appear on the pricing pages — root domains, custom domains, subdomains — and they describe overlapping but distinct things. Since the domain allowance is the binding constraint on at least two of the platforms in the best landing page builders ranking, it is worth getting precise about.

Everything below was read from the vendors’ own pricing pages on 21 September 2026.

What each vendor counts

Leadpages counts custom domains: four on Grow at $79 a month annually, six on Optimize at $159, ten on Scale at $319. SSL is included with each rather than sold separately.

Unbounce counts root domains: one on Starter and Build, two on Experiment, three on Optimize.

Swipe Pages counts custom domains: one on Startup at $29, five on Marketer at $69, unlimited on Agency at $149.

Instapage counts subdomains: two on Create at $79, ten on Optimize at $159.

Landingi counts custom domains: one on Build at $24, three on Optimize at $119, ten on Scale.

Root domain, custom domain, subdomain

A root domain is the registrable name itself — the thing you bought from a registrar. A subdomain sits underneath one, at the left: offer.example.com, go.example.com, try.example.com. “Custom domain” is the loosest of the three phrases and generally means any hostname you point at the vendor, whether that is a root or a subdomain.

The practical question that follows is the one nobody answers in a comparison table: if you publish one campaign at offer.example.com and another at trial.example.com, have you used one unit of your allowance or two?

A root-domain meter implies one. A custom-domain meter frequently implies two. A subdomain meter obviously counts subdomains. Vendors differ, their documentation is not always explicit, and the answer changes the value of a plan substantially for anyone running more than one campaign. Ask before you subscribe, and ask in a channel that produces a written answer.

Subdomain or subfolder

There is a second, older argument underneath this, and it applies whenever the page could plausibly live on your main site instead.

A subfolder — example.com/offer/ — keeps the page on the same host as the rest of your site. A subdomain — offer.example.com — does not. There are long-running debates about how search engines treat the two, and this site is not going to settle them with a confident claim, because the honest position is that the effect is smaller than the people arguing about it suggest and depends on circumstances nobody can generalise about.

What is not in dispute is the practical difference. A hosted landing page tool will publish to a subdomain by pointing a DNS record at the vendor. Publishing into a subfolder of an existing site is harder, usually needs a proxy or a plugin, and is not something every vendor in this category supports. If subfolder publishing matters to you, treat it as a hard requirement and check it first, because it will eliminate options.

Should a campaign page be indexed at all

A question that arrives as soon as the page is live, and one where the honest answer is “it depends on what the page is”.

A page built for paid traffic on a commercial keyword is usually competing with your own site for that keyword. Two pages about the same offer, one on your site and one on a campaign subdomain, is a situation search engines handle by picking one, and their pick may not be yours. If the campaign page exists only to receive clicks you have paid for, there is no traffic to lose by keeping it out of the index, and one source of confusion removed.

A page built to stay — an evergreen offer, a long-running service page — is a different case and belongs in the index like anything else.

What matters is deciding rather than defaulting. Every platform here can set a page to be excluded from search; find the setting during the trial, because it is easier to make the decision before the URL has been shared than after. And whichever way you go, keep one canonical version of the offer. Two live pages competing for the same term is a self-inflicted problem that no amount of testing will fix.

The part people forget: the DNS record outlives the plan

Pointing a subdomain at a vendor takes two minutes. Remembering that you did it takes years.

A campaign subdomain with a stale DNS record is a small, quiet liability. Once the subscription lapses the hostname keeps resolving toward a vendor that no longer serves anything for you, which at best produces an error page carrying your brand and at worst leaves a hostname pointing at infrastructure you do not control.

Two habits prevent it. Keep a written list of every hostname you have pointed at a page builder, with the date and the campaign it belonged to. And when a campaign ends, remove the record rather than leaving it in case you need it again. Neither is difficult; both are forgotten constantly, and the cost of forgetting is out of proportion to the effort.

What you can take with you

The domain is the one asset in this arrangement that is genuinely yours, which makes it the thing to keep tidy.

Your pages are not portable in any meaningful sense. Every platform here builds pages in its own editor and its own format, and moving between vendors means rebuilding rather than exporting. That is not unusual and it is not a scandal, but it is worth pricing into a decision: the switching cost of a landing page platform is the rebuild, not the subscription.

Your leads are portable, and you should make sure of that before you need it. Any form on any of these platforms should be writing to somewhere you own — a CRM, an email list, a spreadsheet, a webhook — rather than only to the vendor’s own submissions table. If the vendor’s database is the only copy of your leads, you have bought a dependency you did not mean to buy.

SSL, and who is responsible for it

Every platform here serves custom domains over HTTPS, and most bundle the certificate — Leadpages states custom domains with SSL on every tier of its campaign line, and the others handle it as part of connecting a hostname.

Two things are worth knowing anyway. The first is that certificate issue is the step most likely to fail on day one, usually because a DNS record has not propagated or because an existing record is pointing somewhere else. Allow for it rather than scheduling a campaign launch for the hour after you connect a domain.

The second is that the certificate belongs to the arrangement, not to you. When the subscription ends so does the certificate, which is one more reason to remove the DNS record rather than leaving it pointed at a vendor you no longer pay.

How the domain meter changes the ranking

For one business with one brand, all of this is invisible. One domain is enough, every plan here allows at least one, and the decision comes down to traffic and testing price.

For anyone running several brands it is the first constraint to check, and it reorders the table. Unbounce’s three root domains at $187 a month works out at $62 per brand. Leadpages’ ten custom domains at $319 is $32. Swipe Pages sells unlimited custom domains on a $149 plan, which is arithmetically unanswerable above about five brands — the detail is in the Swipe Pages review.

Work out how many hostnames you will need in eighteen months, not today. The domain meter is the allowance people size correctly for launch and badly for growth, and unlike a traffic cap it does not announce itself when you hit it — you simply find that the next campaign needs a plan upgrade before it can go live.