Birta
← Back to Birta

One offer, one page, one address

How to Make a Landing Page That Goes Live Today

One goal, one action, one form. What belongs on a landing page, the prompt that builds it, and how to change the offer later without changing the link.

One goal, one action, one form

That is the whole shape. Everything below is how to make a landing page with that shape and get it to a public address in one sitting.

You describe the page to an agent connected to Birta. It writes the HTML, declares the form and publishes. The address works a minute later, and you can keep editing the offer afterwards without the link changing.

Decide the one thing the page asks for

Before any wording, name the single action a visitor can take. Book a call. Send an enquiry. Join the list. Buy the one thing.

Write it as a sentence: "a visitor who arrives ready will book a call." If you cannot finish that sentence, the page has no job yet, and no amount of design fixes that.

One action means one. A second call to action does not double your chances, it gives somebody a way to leave without doing either.

What goes on the page

No navigation menu. No about page. No footer full of links. Every one of those is a door out of the only room you wanted the visitor in.

Length follows the ask. A free newsletter needs a headline and a field. A $4,000 project needs proof, scope and a price band before anyone fills anything in.

Write the offer before you write the page

The headline says what the visitor gets. The line under it says who it is for. That is the pair that does the work, and both are easier to write about a specific person than about a market.

Compare these two:

  • Bespoke digital solutions for modern businesses.
  • Shopify stores for jewellers who sell at fairs and want the stock to match.

The second one loses most readers on purpose. The ones it keeps are the ones who can say yes.

Proof beats adjectives. "Twelve stores since 2021, three of them for repeat clients" is a fact somebody can check. "Award-winning" is a word they have read on every other page they opened today.

Tell the agent what to build

Paste this, filled in. It carries the four blocks, the single action and the form fields, so the agent has no gaps to invent.

Build me a single landing page and publish it on Birta.

The offer: [what the visitor gets, in their words]
Who it is for: [the specific person]
The one action: [book a call / send an enquiry / join the list]
Proof I can use: [result, client name, or number]
About me, one line: [name, what you do, city if it matters]

Rules:
- One page, no navigation, no links off the page except my email.
- The action appears at the top and once more at the bottom.
- Declare a form with these fields: [name, email, one message field].
- Mobile first: I will look at it on a phone before anything else.

Show me the offer headline and the subheadline before you build the whole page.

That last line matters more than it looks. The headline is the part you will want to argue with, and arguing about one sentence is faster than regenerating a page.

Publish it, then use your own form once

  1. Step 1PublishThe form only works on the live site, not in a preview.
  2. Step 2Open it on a phoneThe offer and the action have to be visible without scrolling.
  3. Step 3Submit onceFill the real form in as a visitor would.
  4. Step 4Read itCheck every field arrived the way you typed it.

Publish first, then look at it on your phone before you look at it on your laptop. Most of your visitors will arrive on a phone, and a headline that fits a wide screen often takes four lines on a narrow one.

Then fill in your own form, once, on the public address. A version preview refuses submissions on purpose, because a request belongs to the live site rather than to a draft. So this test only works after publishing.

Read what arrives, not just that something arrived. A required field the agent never declared is exactly the failure you want to find before the page has traffic.

Where the request lands

A submission arrives against the project and waits in its Leads tab with every field as the visitor typed it. An email digest follows, covering everything that landed in a short window rather than pinging you per submission.

The page itself stays a static file. It has no database and runs no code, so the form is the one moving part, and the agent declares it as a contract: which fields exist, what each one accepts, and what a visitor sees when it is accepted.

A public page that collects real enquiries runs on Solo, the first paid plan.

The first version of an offer is a guess. Ask the agent to rewrite the headline, publish again, and the address stays the same. Anyone holding your link sees the new page.

Old versions stay where they are, so a rewrite you dislike takes one rollback rather than a rebuild. Change one thing at a time if you want to learn anything from it.

When one page is not the answer

Two signals. If visitors need to compare several services before choosing, one page starts fighting itself. And if you are writing a second landing page for the same audience, you probably want a small site with one page per offer.

Both of those are decisions before they are builds, and the landing page or website questions settle them faster than a redesign will.

Describe the offer, get the page

Your agent writes the page and publishes it. The enquiries land in your panel.

Connect your agent to Birta

Frequently asked questions