Sending paid traffic straight to your home page wastes most of it. The home page speaks to everyone, which means it speaks to nobody in particular — and the person who clicked your advert about single parents in Manchester lands on a general greeting and leaves.

A landing page fixes that. One page, one audience, one promise, one signup form. You can have as many as you like, and each can live on its own address on your domain.

Landing pages are an add-on. See current availability on the pricing page.

Upload your own HTML as a ZIP archive. The page then lives on your domain.

Connect a page built elsewhere — in Tilda, Unbounce, Instapage, GetResponse or a similar builder. This is the practical choice for most owners: you edit the page in a visual editor, run tests, and change the offer without touching your site.

Builders also let you run A/B tests to find which offer converts best, then send your paid traffic to the winner. That lowers what you pay per registration, which is usually the whole point of the exercise.

Admin panel: Services > Customize your service > System > Landing pages (/admin/landings/index/).

Click Add landing page, give it a name and the part of the address where it should sit. You do not type the full address into the Link field, only the tail.

Upload the ZIP archive with the page files. The archive must contain an index.html file, otherwise the system cannot process it.

Click Preview to see the result. There is no limit on how many pages you add.

If the upload fails, check post_max_size, upload_max_filesize and memory_limit in your php.ini — the archive may simply be larger than your server allows.

This is the step people forget, and it is the one that matters. A beautiful page whose form leads nowhere collects nothing.

The simplest version: an HTML form with the required fields, submitting to your-site.com/users/registration. About an hour of work for any developer, design aside.

If you want the full registration form from the field editor on your landing page, allow around two hours. Any developer can do it, or ask us.

If you build pages in an external service, the same page can end up on two addresses: yours and the builder's. Search engines see duplicates and both versions suffer.

Decide which address is the real one, then check robots.txt, canonical addresses and the sitemap — on your site and on the builder's side. Five minutes of setup, and it saves a problem that is hard to diagnose later.

One audience per page. That is the entire advantage over the home page. Single parents, people over fifty, one city, one interest. Two audiences on one page means neither feels spoken to.

Say how many people are already there. The number of members in their city is the one fact that decides whether someone joins a dating site.

Ask for the email first. Everything else can be filled in after registration. Every field before the email is a chance to lose the person — see abandoned signups for what that costs.

Make one page per advert, not per campaign. The wording on the page should echo the advert the person clicked. When it does not, they assume they clicked the wrong thing and leave.

I changed the page and nothing changed on the site.
Clear the cache for the page to refresh.

The page uploaded but the images are missing.
Paths inside the archive have to point through the uploads folder: not images/4.jpg but /uploads/landings/1/images/4.jpg. The correct path for your page is shown on its edit screen in the admin panel. The same applies to stylesheets and scripts.

How many pages should I have?
As many as you have distinct audiences, and no more. Ten pages you never look at are worse than two you test and improve.

How do I know which page works?
Registrations per page, not visits. See analytics for dating platforms.