Cloudflare on your landing pages
If you run one landing page on one domain, DNS is a one-time chore. Media buyers rarely do. A domain per offer, a domain per geo, a domain per client: each one means logging in to a registrar, finding the DNS screen, creating a record in that provider's format, waiting, and checking whether HTTPS needs a second record. It's the slowest part of launching a page that's otherwise ready.
LanderLab's Cloudflare connection takes that part away. You sign in to Cloudflare once and approve access, and from then on LanderLab creates and maintains the DNS records for every domain you add from that account. When you add a domain, LanderLab checks where its DNS is managed and recommends Cloudflare when it finds it there.
Custom domains without copying DNS records
With Manual DNS, every domain is a small project: open the provider's DNS screen, create the record LanderLab shows, match each provider's idea of what a host should look like, clear any record already on that host, then refresh until it verifies, and sometimes add a second record for HTTPS. It works with any registrar, and it's still the step where launches stall.
With Cloudflare connected, LanderLab writes the records into your Cloudflare account itself and maintains them afterwards. You enter the domain, choose which workspaces can publish to it, and the page you built this morning can go live on its own domain the same day.
A domain per offer, per geo, per client
Buyers who split traffic across domains, one per vertical, one per country, one per client, add domains far more often than anyone else. That's exactly when signing in once pays off: every new domain from a connected Cloudflare account skips the DNS work entirely.
Each domain can be limited to the workspaces that should publish on it, or opened to All Workspaces, which also covers workspaces you create later. An agency can keep each client's domains in that client's workspace, connected through the client's own Cloudflare account.
Root domains for brand-led offers
Some offers should live on the root domain, not on lp. or go. in front of it: an advertorial brand, a product site, a client who wants their own clean URL in the ad. Many DNS providers can't put the record LanderLab needs on a root domain, which is why Manual DNS usually asks for a subdomain. Cloudflare supports both, so the root domain is an option from the start.
Domains that aren't on Cloudflare yet
A domain registered elsewhere can still take the Cloudflare route: one nameserver change at the registrar, made once per domain, instead of DNS records to maintain there for every page you publish.
The change can take from a few minutes to 48 hours to reach everyone, and the domain shows as Pending until it does, so make it before launch day, not on it.
Ready for paid traffic once it's Active
Whichever way a domain is connected, its settings are where paid traffic gets looked after. Disable Indexing adds a noindex tag to every page on a domain used only for ads. A custom fallback URL sends people who hit a dead link to a page with an opt-in form instead of a 404. Domain-level custom code puts a tag manager, a pixel or a consent banner on every page published there, once.
