Need help? You’ve come to the right place

What’s New Getting Started Building Integrating Publishing

Change your Leadpages Domain

Last Updated

A default Leadpages Domain will be created for you when you create a Leadpages account (i.e. When you publish your first page or site, you will be asked to choose a custom Leadpages Domain for your account. However, if you want to change your Leadpages Domain again, this article will help detail how to get in touch with support and what information is needed to change it.

Changing your Leadpages Domain will change the URL of all of your landing pages and sites published to that domain.

To change your domain, file a support ticket and let us know what you’d like your new domain to be. Your domain must…

  • be at least six characters
  • be unique (no two Leadpages customers can have the same domain)
  • begin with a letter
  • comply with our terms of service

We’ll ask you to confirm this change, since it affects the URLs of your published pages. If you have several choices for what you’d like your domain to be, please list them in order of preference.


After your domain change…

Once you change your domain, you may need to republish your landing pages or pop-ups (depending on how you published them originally). Here are some things to check to make sure that you can continue collecting leads:

Running promotions

Leadpages will not automatically redirect traffic from your old domain to your new one. As such, if you have any running promotions, broadcasted links, ads, newsletters, etc., you’ll need to update those URLs to reflect your new domain.

NOTE: These URL updates will typically not affect any pages that are published to a custom domain, with a few exceptions covered below.


Changing your Leadpages domain affects your pop-ups’ publishing code. Pop-ups can only be published to the Leadpages domain, and the code for the pop-up references it. If you were to change your Leadpages domain, the updated name would not be reflected in pop-up codes you’ve already placed in pages.

If you’ve used pop-up code for your site, email signatures, newsletter templates, your blog, etc., you’ll need to update it. To do so, you can follow our publishing guide below to replace the code wherever you have pop-ups published:

TIP: If you published any pop-ups using our WordPress plugin (version 2.1 or above), you don’t need to worry about manually updating them.

Pages published with our WordPress plugin

NOTE: We recommend updating your plugin to at least version 2.1 before changing your domain. You can learn how here: Migrating from Previous WordPress Plugin Versions.

If you’re using version 2.1 or later of the plugin, you shouldn’t need to do anything after changing your domain. All your pages will continue working as normal, but please don’t hesitate to check out our troubleshooting guide or reach out to us if you do run into issues.

Here’s what you can do if you were running an older version of our plugin before changing your domain:

  1. Make a list of all your WordPress-published landing pages and the pages' URLs so you can re-publish them with the same URLs.
  2. Deactivate and delete the old plugin.
  3. Replace your plugin with a newly downloaded version.
  4. Check your landing pages to make sure that everything is working as expected. You may need to republish some or all of your pages, depending on which version you upgrade from.

For detailed steps on updating your WordPress plugin, see Migrating From Previous WordPress Plugin Versions.

Landing pages published via HTML

If you have published your pages to your own server by downloading the HTML file of the page, dynamic or full HTML, you must download the HTML file of the page again and republish the page to your servers.

WARNING: We do not support changes to your pages’ full HTML code. If you run into particular issues changing your page’s code, you’ll need to contact a web developer for assistance.

Need more help?

You can always get in touch with our support team—just click Support in your Leadpages navigation menu, or submit a ticket ↗

Was this article helpful?
Powered by Zendesk