All Collections
Landing Pages
How to use a custom domain for Landing Pages
How to use a custom domain for Landing Pages

If you want your Landing Page to use your own custom domain rather than ours, here's how to get set up!

Updated over a week ago

Your page, your domain.

By default, any Landing Page you create in ConvertKit will be hosted on your domain, which can be customized by clicking your account name at the top right of the navigation, followed by Settings > Domains.

If you own your own domain, however, you have the option of using that for your Landing Pages instead!

NOTE: For a higher-level overview of your domain options and which might be right for you, check out our overview of account domains versus custom domains.

Things to note

Before we get into the technical set-up, let's cover a couple of important points to be aware of:

Setting up a custom domain will not break or invalidate your default domain. You'll be able to use your Landing Page's URL to visit your Landing Page!

The same also applies if you change your domain's prefix, such as changing to—the original prefix will still work too.

2. If you already have a website on your custom domain, you'll want to use a subdomain for your Landing Pages

This is important!

For example, if you own and your existing website lives there, you'll want to set up the custom domain for your Landing Pages on a subdomain, such as

This is because in order to use your custom domain for your ConvertKit Landing Pages, you have to change that domain's DNS records. (More on this later.)

If you make these DNS changes on directly, your Landing Page will take over that domain. You don't want that to happen if you already have a website there!

The only time you wouldn't use a subdomain is if you want to point directly to a ConvertKit Landing Page rather than to your own website.

NOTE: If you accidentally made DNS changes to your main domain instead of a subdomain, don't worry—it's reversible!

Just remove the records you added, and everything should go back to normal once the changes to your DNS records take effect.

Refer to your hosting provider's documentation to learn how to set up a subdomain with them. (They'll be the best resource for this as each provider may have a slightly different process.)

Once you've created your subdomain, return to this tutorial for the next steps.

Let's get started!

Here's the process of connecting your ConvertKit Landing Pages to your custom domain or subdomain.

1. Add your (sub)domain to ConvertKit

Under the Homepage field for your custom (sub)domain, select the Landing Page you want your users to land on if they visit that (sub)domain directly.

For example, if you set up your sales landing page as the homepage of your custom domain, then users will see your sales landing page when they visit

NOTE: You'll still be able to customize each Landing Page's URL, such as With this step, you're just selecting where people should land if they visit directly (and you can change this anytime).

After setting up your custom (sub)domain, you'll need to wait until its DNS records have been verified. This may take up to 24 to 48 hours.

If you're having trouble getting your custom (sub)domain verified, check out our custom domain troubleshooting guide.

2. Set your Landing Page paths

Once your domain is verified, you can set individual paths for your Landing Pages.

Your Landing Page's path is the my-landing-page portion of (or if you opted to use a subdomain). Basically, it's the individual link to your Landing Page!

To set this up, open your Landing Page by going to Landing Pages & Forms under the Grow tab in the navigation. Then, click Settings from the toolbar of the Landing Page builder:

Then, click Domain Name from the left of the settings modal:

From here, select your domain from the Custom Domain dropdown (you can have multiple custom domains per account!) and enter your desired path in the Page URL field.

Click Add, then save your changes.

Finally, try visiting your Landing Page's URL to see if you're directed to your Landing Page!

Did this answer your question?