Landing Page vs Homepage: Which One Should You Send Traffic To?
Sending campaign traffic to your homepage asks the visitor to find their own way. What changes when you send it to a landing page instead, and when it should not.
A designer can only build what you have already decided. Hand over a brief that says "landing page for the new service, something clean and modern" and you have not commissioned a page: you have asked someone else to guess at nine decisions on your behalf, inside a design tool, where guessing is slow and expensive to undo.
Almost every bad landing page is a design problem caused by a decision nobody made. Settle these nine questions first, on paper, and the layout largely designs itself.
Decisions one to three: the action, the audience, the source
Decide the single action. Not the goal. The action. One thing you want the visitor to do, phrased as a verb they perform: submit an enquiry form, book a slot, ring a number, download a file. If two candidates are competing, pick the one you would rather have and demote the other to a line of text. A page with two equal actions has no action, because the reader resolves the choice by leaving.
Decide who is arriving. "Homeowners" is not an audience. "Homeowners in the northern suburbs whose boiler has just failed in February" is. The narrower you can make this, the more of the page writes itself, because you already know what they are worried about, how fast they need it, and what they will compare you against.
Decide the traffic source. A page receiving paid search traffic for a named service is a different page from one receiving a link at the bottom of an email to existing customers. The ad visitor needs the promise from the ad repeated in the first line. The email visitor already knows who you are and wants the practical detail instead. If the two sources genuinely differ, that is two pages, not one page with two openings bolted together.
Decisions four to six: the offer, the objection, the proof
Decide what you are actually offering. Most briefs say "get more enquiries", which is a result rather than an offer. The offer is the specific thing on the other side of the button: a free survey, a fixed-price service at a stated figure, a fifteen-minute call, a document. Vague offers produce vague pages, and the vagueness shows up in the headline first.
Decide the one objection that stops people. There is usually a single thing that makes an otherwise interested person hesitate: the price is unknown, the contract length is unclear, they suspect the "free consultation" is a sales call in disguise, they are not sure you cover their area. Pick the biggest one and answer it in plain words on the page. If you cannot name it, ask whoever answers the phone. They hear it several times a week.
Decide what proof you genuinely have. Not what you wish you had. Photographs of finished work, a named client who will let you quote them, a licence number, the year you started trading, a review that exists somewhere a reader could go and check. Proof you have to invent is not proof, and a page padded with generic reassurance reads worse than a page carrying one real testimonial and nothing else.
Decisions seven to nine: length, fields, and what happens next
Decide how long the page should be. Length follows commitment, not taste. A free download that costs the reader an email address needs very little page. A £4,000 installation booked by someone who has never met you needs more: what happens on the day, who turns up, how payment works, what the guarantee covers. Work out what a careful person would need to know before saying yes, write that, and stop.
Decide how many form fields. Every field is a small ask and the reader pays them all at once. Settle on the minimum that makes your next contact useful. Usually that is a name, one way to reach them, and one detail that lets you prepare. A postcode earns its place if you have a service area. Company size earns its place if it changes the price. "How did you hear about us?" does not.
Decide what happens next. The thank-you step is part of the page and it is the part most often left at whatever the form plugin does by default. Say what you will do and when: we will call you back the same working day. If there is a document, put it on screen as well as in an email. If there is a wait, name it. A confirmation reading only "Your message has been sent" wastes the one moment when attention is at its highest.
A one-page brief you can fill in before anyone opens a design tool
Write the nine answers down in one place, in plain sentences, and you have a brief. It needs no template: the action, the audience, the source, the offer, the objection, the proof, the rough length, the form fields, the follow-up. Nine lines. Whoever builds the page can read it in a minute, and will stop asking you questions that begin "did you want...".
It helps to look at finished pages before you specify your own. Browsing a theme like Kendytheme is a reasonable way to see how other people solved the same structural problem (where the form sits, how much is visible before scrolling, what order the proof arrives in) before you commit to a structure of your own. Starting from something that already works is not a failure of imagination. It is a shorter route to a page that behaves.
What changes once these are settled
The design stops being a matter of opinion. When the action is fixed, the position of the button is a consequence rather than a debate. When the audience is named, arguments about headline wording end quickly, because there is a specific person to test the sentence against. When the proof is agreed, nobody has to invent filler to stop a section looking empty.
You also get a page you can judge. If it underperforms, you have nine written assumptions to test one at a time, rather than a general feeling that it ought to look better. That is the practical difference between a page you can improve and a page you can only replace.
Most of this work happens away from the screen, which is exactly why it gets skipped. When we build a landing page, the nine answers come first and the layout follows them. It is simply a faster way to arrive at a page that does one job properly.
