Publishing landing pages under your own domain

Last updated: June 17, 2021 Written by: Avatar Marta Szeliga
Table of contents
Table of contents

Once a landing page has been created and published for the first time, it is available under the test domain. In the Landingi platform, you can publish it on your own domain (previously purchased from the selected provider) in several ways.

NOTE: Landingi does not offer domain sales services.

Domains and Subdomains in Landingi platform

Root Domain is the part of the domain directly followed by the top-level domain (e.g., .eu or .com) and is separated from it by a dot for the mydomain is the root domain.

Subdomain precedes the main domain and is separated by a dot


here, the subdomains are ‘landingpage’ and ‘www.’

The URL address is the subdomain for the root domain called In the domain providers' administration account, you can usually create as many free subdomains as you like for the root domains.

If you want to host your landing page on Landingi servers, you can publish it only under the first-level subdomain.

NOTE: ‘www’, in fact, is also a subdomain added to the root domain.

The A record is used to create a redirection from an address without "www" to an address with "www" so that the user who enters the address without "www" in the browser bar (such as will be automatically redirected to the "www" page. (such as, on which the landing page is hosted.

It is not possible to host a landing page on a naked domain (without "www") on Landingi servers in this case, we recommend publishing it on your own server (embed .PHP).

Landing page URL address and publishing options

Depending on what the URL of your landing page is supposed to look like, you have different publishing options:

  •, you can publish a landing page in any way you want;
  • – you can publish a landing page in any way you want;
  •, you should publish your landing page on your own server (embed .PHP) or WordPress.

If you decide to publish under the subfolder/subdirectory with a path (e.g.,, both the main page (current homepage) and the landing page must be redirected to the same servers. Setting a separated CNAME record for the main page and the landing page is impossible. If you redirect the main domain to our servers, the existing page will no longer be displayed.

If you already have an active webpage on your main domain, we recommend using the subdomain or adding a landing page to your own server if you want to publish it as a path.

Landing page publishing options

With Landingi, you can publish a landing page under your own domain in three ways:

  1. Connect the domain with an account and publish the landing page on Landingi servers
  2. Publish the landing page on your WordPress domain
  3. Publish the landing page on your own server

I. Connect the domain with an account and publish on Landingi servers

The entire process takes two following steps:

  • (A) First, redirect your domain on our servers using DNS records that you will change or add in your domain provider’s administration panel.
  • (B) Once you have correctly added the domain to your account and activated it, assign a landing page to it.

We will automatically install a free Let’s Encrypt SSL certificate during the process of adding the domain to the account.

A. Add a domain to the account

1. Log into your account and go to the Domains tab, then click Add domain.

Type the domain name you want to add and click on Continue.

NOTE: the ‘www’ will be added automatically to the naked domain (e.g.,

3. IMPORTANT: In the next step, click on Done only after you have completed all the steps listed below.

Now you can configure the domain by adding DNS records to the domain in the administration panel of your chosen domain provider (outside the Landingi platform) according to the following steps:

4. Log in to the domain administration panel on your domain’s provider and find the DNS records settings (DNS settings). Remember: make sure you are not using the DNS servers dedicated for other purposes.

5.1. Add two new DNS records (CNAME and A) to redirect the root domain:

Type: CNAME 

Type: A 

5.2. Add one new DNS record (only CNAME) to redirect the subdomain:

Type: CNAME 

Some of the panels require adding a dot (‘.’) manually at the end of the URL address or/and the name (most of the panels are adding them automatically). If you still have doubts about it, check the instructions in your provider’s FAQ.

6. When you are ready, go back to the Landingi platform and click on Done.

NOTE: Some of the panels, such as OVH, may require deleting the TXT records for the given domain.

You will see a pop-up message that the configuration is done.

Our system is verifying if DNS redirections have been done correctly. During this time, a clock icon will be visible next to the domain with the information that the domain is being verified. Usually, the domain will be active a few hours after adding it, but the total waiting time depends on the number of domains in our system waiting in the queue to install the certificate. We will inform you by e-mail when the first domain is installed correctly.

IMPORTANT: Due to the time needed to disseminate DNS records and installation of the SSL certificate, we recommend performing the above steps at least 3 days in advance of the campaign. If you want to use Cloudflare at the same time, please have a look here.

7. A green globe icon indicates an active domain, to which you can assign a selected landing page.

B. Assign landing page to your domain

1. Go to the Landing pages tab and select the landing page for which you want to change the domain.

Select More > Publishing Options.

2. Click on Change URL.

3. In the new window, select the domain you want to assign to the landing page (1) optionally, you can add the path to the address (2) and then Save Changes (3). The landing page will be visible immediately under the new URL.

IMPORTANT: There are several paths you can not add to the address. Do not use:

  • '/sitemap.xml',
  • '/robots.txt',
  • '/policy',
  • '/order',
  • '/max-unique-users.html',
  • '/favicon',
  • '/apple-touch-icon.png',
  • '/apple-touch-icon-precomposed.png',
  • '/email',
  • '/contact"/"contact-us',
  • '/send',
  • '/facebook',
  • '/background',
  • '/picture',
  • '/style',
  • '/submit'.

II. Publish on your WordPress domain

If your webpage is powered by WordPress and you want to display your landing pages on it, you can do it thanks to one of the dedicated plugins: Landing Pages App (without Landingi branding) or Landingi Landing Pages (with Landingi branding), which are available or in a plugin search engine in WordPress dashboard.


  • Installing the SSL certificate is on your side.
  • Landing page publication is possible only on a first-level subdirectory (subfolder).
  • You can change the URL path of your landing page at any time after importing it to your WordPress.
  • You can set up your landing page as a homepage.
  • If you use the plugin, changes on your landing page after re-publishing can be visible up to a few minutes.
  • The configuration should be made in two steps: inside Landingi platform and in your WordPress dashboard.

A. Configuration in Landingi platform

1. Log in to Landingi platform. Click on your profile name at the top bar and then go to the API Tokens tab.

api tokens landingi

2. In the new window, click on the Add token button.

3. In the Create new API Token field, type the name of your token (e.g., WordPress) (1) and click on Generate new token (2).

4. The generated token will be automatically saved in the API Tokens tab.

5. Download and install one of our WordPress plugins.

B. Plugin configuration in WordPress

1. Log into your WordPress account.

2. In the sidebar on the left, click Plugins (1). If you have not downloaded our plugin before, select Add new (2) and search Landingi Landing Pages (3) and then add it to your account.

wordpress landingi

3. Go to the Installed Plugins tab, find Landingi Landing Pages there, and then click Activate.

4. In the sidebar, the Landingi tab will appear (1). Go to it and then click Settings (2). In the Setup connection window, paste the previously generated API token (3) and click Save API Token.

5. Go to Available Landings (1). On the right side, the list with your landing pages made in our platform will appear. Select the landing page that you would like to import and click Import (2). From now on, each of them will be automatically active (published).

6. In the Imported Landings tab (1), you will see the previously imported landings. If you want to change the settings of any landing page, choose the right action that will appear after hovering over a selected landing page (2).

7. To change the URL address, hover over the selected landing page and click Edit. The direct link will appear in a new window. Click Change Permalinks.

8. In Permalink Settings, you can type the new path’s name in Custom Structure. To confirm click Save Changes.

III. Publish on your own server

If you do not want to use the hosting option in Landingi servers or want to publish the landing page under your naked domain along the path (e.g.,, you can download the landing page in a .PHP file and add it to your server.


  • Installing the SSL certificate is on your side.
  • The landing page edition is the same as before generating a .PHP file. After making changes in the editor, click Publish – there is no need to generate the .PHP file again. Changes on the landing page can be visible online up to a few minutes after the publication.
  • If your account in the Landing platform expires, the landing page on your server will no longer be available to users.

Download a .PHP file of your landing page

1. Log into the platform and go to the Landingi tab.

2. In the list of all the landing pages, find the one you want to add to your server and click in More. From the drop-down menu, choose the Publishing Options.

3. In the new window, click on Embed on server.

4. In the next window, click on Download a .PHP file.

5. After downloading, insert the .PHP file on the server in a folder, just like any other website file.


Was this manual helpful?