Landing pages for a campaign: what visitors from the ad need to find

Someone arriving from an ad has one exact phrase in mind: the ad's. If the first lines of the page don't match it, they realize they're in the wrong place and go back, often without even scrolling. A campaign page shouldn't be more polished than the homepage: it has to continue a conversation started elsewhere, for an audience that's already known and for a single offer.

That's where the difference comes from. The homepage has to hold up for anyone arriving, from any direction, so it lists everything. A campaign page only has to hold up for one direction. Anything that doesn't serve that direction weakens it, even when it's true and well written.

Continuing the ad's sentence, without raising the stakes

The ad made a promise in a few words. The page's headline has to pick it up in the same words, not a more elegant synonym. The reader isn't judging your prose: they're checking, in two seconds, that they clicked the right thing.

• The words from the search and the ad belong in the headline and the first paragraph, exactly as the customer uses them. If the ad says “boiler replacement,” the page doesn't open with “heating comfort solutions.”
• The offer has to be the same. If the ad talks about a site visit, the page can't only offer a phone quote: that's a different thing, and the visitor notices.
• The audience has to be the same. A page aimed at both homeowners and businesses at once speaks to neither, because the questions they ask aren't the same.

Then there's the opposite temptation: making the promise bigger than it really is, because that brings in more leads. It does bring in more, but from people expecting something else. The cost just moves from the campaign to your own time.

The order of sections: the problem first, then how it works, then the proof

A campaign page is read from top to bottom and abandoned at any point. Order matters more than quantity: each section answers the question the reader is asking themselves at that moment, not the one you'd like to ask them.

1. Is this my problem? The situation described in the customer's own words, not your internal categories.
2. What do I get? The outcome, not the list of activities. “We tell you whether the system can be salvaged” is an outcome; “advanced technical diagnosis” is an activity.
3. How does it work? The steps in order, to remove any uncertainty about what responding involves.
4. Why should I believe you? Work shown with its context, relevant qualifications, checkable references. Adjectives don't count as proof.
5. Under what conditions? Service area, the jobs you handle, what's included. Clear conditions filter out the wrong leads better than any required field.
6. What do I do now? The request, repeated where needed, always in the same words.

An example: the page for a site-visit request

A systems company launches a campaign in a specific area and wants site visits, not generic phone calls. The text in the column is illustrative: it shows the level of concreteness required, not text to copy as-is.

One single request, and the objections that come before it

Two different actions on the same page — requesting a quote and downloading a catalog — don't double your leads: they split attention and make the result unreadable. Pick one as the main action. A second way to get in touch, such as a phone number, can stay as an alternative, not as an equal option.

Before reaching the request, the reader has three or four objections in mind. They should be spelled out, not sidestepped: leave them unanswered and the reader answers them alone, usually badly.

• “Then you'll flood me with calls.” Say what happens after the form is sent and who gets in touch.
• “How much does it cost?” If the price depends on the case, say what it depends on.
• “Am I committing to anything?” This has to be stated explicitly.
• “Do you cover my area?” Coverage should be written out, not left for the reader to infer from an address at the bottom.

Checking that the lead arrives, and that it's useful

The check happens in two stages, and the second is the one almost everyone skips.

1. Before launch: send a test request from a phone and from a computer, and check that it arrives where it should, not in spam, with every field readable.
2. In the following weeks: log the outcome of every request. How many were in the service area, how many were about the campaign's service, how many turned into an appointment.

It's the second check that tells you whether the page works. A page that brings in many out-of-area requests is shifting the filtering from the campaign to your front desk: this is usually fixed by moving the conditions higher up, not by adding fields to the form.

When you don't need a new page

• If the offer and the audience match an existing service page, it's better to improve that one: two nearly identical pages compete for the same space and double the maintenance work.
• If no one can respond within a reasonable time, the page produces leads that go cold. Decide first who's going to respond.
• If the campaign runs for only a few days and communicates just a date, a section of an existing page can be enough.

There's still the temptation to make a variant for every keyword. It only makes sense when the need actually changes: someone looking for a repair and someone looking for a replacement have two different problems. Someone looking for the same thing in different words has one problem, and ten near-identical pages are ten pages to keep updated.

What this guide doesn't cover

This guide is about building the page for a single campaign, with one need to answer. What questions to put in the form, how many, and in what order, is a discussion of its own. And if the problem isn't the campaign but the website as a whole — visits arriving but no leads — the diagnosis has to come first, following the visitor's whole path.