Landing page design

What a landing page does that a homepage cannot

A homepage is a junction. It serves every audience you have, describes everything you do and offers routes to everywhere, which is right for someone researching your company and wrong for someone who just clicked an advert about one specific thing. A campaign landing page is a continuation of that click. One entry context, one audience, one offer, one primary action, and navigation cut back to what the decision actually needs. The narrowness is the point. Everything that does not help the visitor make this decision is competing with the thing that does.

The scope connects four things: the campaign context the visitor arrives with, the proof that supports the offer, the enquiry path that follows, and the measurement you agreed beforehand. What sits inside a given engagement depends on what already exists. If the offer, the copy and the proof are settled, the work is short. If they are not, deciding them is the work.

Fix the campaign, audience and offer before the design

The intake sequence is short and it saves a lot of rework. Name the entry source: a search advert, a Meta or TikTok advert, an email, a printed code. Name one priority audience, not three. State the approved offer, including what it does not include. Then write down, word for word, the promise made before the click. That last step is the one people skip, and it is the one that later explains why a page that looks good does nothing. Google Ads documentation describes landing page experience as how relevant and useful your landing page is to people who click your advert, which is a fair plain-language description of the whole job.

Running the campaign and building the destination are two different jobs, and it is worth being clear about who holds each. We do both: we manage Google Ads, Meta Ads across Facebook and Instagram, and TikTok Ads. Your business owns the ad accounts, the billing profile and the data in them, and media budget is paid to the platform by you rather than through us. The landing page is still website work and is scoped as website work, whether we run the campaign or your existing agency does.

Choose the one action, then build everything around it

Write the offer down in a sentence: what it is, who it is for, what is included and excluded, and the one action the page asks for. Then build the hierarchy in the order a visitor uses it. Confirm the entry context first, because their opening question is whether they are in the right place. Explain the offer. Show the evidence. Deal with the things that make people hesitate, such as what happens after they send the form and who will contact them. Then the action, with the form in plain sight rather than behind a scroll. A secondary action is allowed only when it supports the first, such as a phone number for someone who will never fill in a form. A link to your full website at that moment competes with it.

Proof that survives a sceptical reader

For every proof item, record four things: what it demonstrates, who supplied it, whether you have permission to publish it, and what limitation or date belongs next to it. A review with a name, a role and a date does work. A photograph of the actual job does work. A number you can source does work. Anything that fails those four tests is decoration, and a sceptical reader treats decoration as a reason to doubt the rest. The deeper task of mapping a whole visit-to-enquiry funnel is a separate exercise with its own guide still to be published here.

The form, its states, and where the enquiry actually goes

The W3C's accessibility guidance is specific and practical here. Every control needs a label that is properly associated with it, and most people prefer or need that label to be visible rather than implied by a placeholder. Instructions should be understandable before someone types. Feedback has to tell the person what happened, distinguishing success from failure, and error messages should explain in plain words how to fix the problem, with focus moved to the first field that has an error. Its planning guidance treats accessibility as an assigned responsibility, integrated through production and evaluated early and repeatedly, rather than a check run the week before launch. That informs how we build and review. It is not a certificate of compliance, and nobody should present it as one.

Three states get conflated and should not be. A submission attempted, a submission validated, and an enquiry delivered. A page that shows a cheerful success message when delivery has failed is worse than one that shows an honest error, because you never learn that the enquiries stopped. Decide before the build where an enquiry goes, whether that is an inbox, a shared mailbox, WhatsApp or a CRM, who is accountable for answering it, what the visitor is told happens next, and how anyone would notice if delivery quietly stopped.

Field-level decisions are their own exercise

Field purpose, labels, instructions, validation, consent wording, the confirmation message and the handoff to whoever answers are each a separate decision. Asking for less usually produces more enquiries and weaker ones, and the right balance depends on who you would rather spend your time talking to. The detailed treatment of field design, error handling and enquiry quality is its own guide, still to be published here.

Test the journey from the click to a useful enquiry

Take a fictional service business promoting one assumed offer, a request for a project consultation, from a single campaign entry context. The roles, responses and policies below are hypothetical, and they show where the three checks that matter actually sit.

Measurement is a chain, and every link is a different kind of evidence: an interaction on the page, a validated submission attempt, a confirmed delivery, a permitted record of the enquiry, an agreed quality review, and a business outcome later where one is available. Definitions, access, retention, consent and who reports on what all need agreeing before implementation rather than after the first month of spend. One warning about a familiar number: Google describes Quality Score as a diagnostic tool for comparing your ad quality with other advertisers, states plainly that it is not a key performance indicator and should not be optimised or aggregated with the rest of your data, and says it is not an input in the ad auction. It is a hint, not evidence about your page.

When a full website is the better fit

If visitors need to understand your company broadly, compare several services, follow different journeys by audience, or use navigation that has to outlive one campaign, a website is the right scope and a landing page will frustrate them. There is a harder truth as well. A landing page cannot rescue a campaign pointed at the wrong audience or an offer nobody wants, and no amount of page design changes that. The full comparison between a landing page and a homepage is a separate guide, still to be published here.

What to prepare before we scope it

Bring the campaign or entry source with the exact advert wording, one priority audience, the approved offer, the action you want, the proof you are allowed to publish, the current destination if there is one, where enquiries should land, how you define a good one, and any real constraint such as a launch date or approved brand wording. Scope and responsibilities get agreed from that rather than assumed. If you have most of it, tell us about the campaign and we will tell you what the page needs and what it cannot do for you.