Landing Page Conversion Best Practices, Step by Step
- Difficulty
- Moderate
- You need
- Page editing access and analytics
- Optional
- Ad account access
On this page
Landing page conversion best practices come down to one idea: a page built for one visitor, one offer and one action. The page should match what brought the visitor there, say plainly what you offer, show proof you can back up, answer the questions that stop people and make the next step easy. This guide is part of our website design best practices guide.
Before you start, you'll need editing access to the page and analytics that records the enquiry as a key event, so you can tell whether changes help. If that isn't set up yet, follow how to set up GA4 for your website first. Access to the ads or emails that send traffic to the page helps with step 2.
What a landing page is for
A landing page is any page a visitor arrives on from a specific source, such as an ad, an email, a social post or a search result. A dedicated campaign landing page has one job: to turn that visit into one action, like a booking, a call or an enquiry.
That focus is what separates it from a home page, which has to serve everyone. A home page offers many routes; a landing page removes the ones that don't lead to the goal.
Relevance matters to ad platforms too. Google Ads rates landing page experience as one of the three parts of Quality Score, described as how relevant and useful your landing page is to people who click your ad. Google calls Quality Score a diagnostic tool rather than a target, but a "below average" landing page rating is a useful sign the page and the ad don't match.
The parts of a landing page
The landing pages we build usually share these building blocks, in roughly this order. Treat it as a starting structure, not a template to copy:
| Part | Its job | What to check |
|---|---|---|
| Headline and subhead | Say what you offer and for whom | Matches the ad or email that sent people |
| Main action | Make the next step obvious | Visible without scrolling on a phone |
| Proof | Show others trust you | Real, attributable, and yours to use |
| What happens next | Remove uncertainty | Steps, timing and what it involves |
| Objections and FAQs | Answer what stops people | Taken from real sales questions |
| Form or contact | Capture the enquiry | Only the fields you really need |
| Repeat action | Catch people who read to the end | Same action as the first one |
Steps
- Name the visitor and the one action.
Write one sentence before designing anything: who is arriving, from where, and what you want them to do. For example, "facility managers from a search ad who should request a site visit". If you can't write that sentence, the page will try to do too much. Every section that follows should help that person take that action.
- Match the message to where visitors come from.
Visitors decide in seconds whether they're in the right place. Repeat the promise from the ad, email or post in the headline, using the same words and the same offer. If one page serves several campaigns, consider separate versions so each headline matches its source.
- Write a headline that says what you offer.
Lead with the outcome or service in plain words, not a slogan. The subhead adds who it's for and what makes it different. Read the headline aloud to someone outside the business: if they can't say what you sell, rewrite it.
- Make the main action easy to find.
Place the main button or form near the top, where it's visible on a phone without scrolling, and repeat it after the proof and at the end. Use a label that says what happens, such as "Request a site visit", rather than "Submit". Keep competing offers off the page.
- Show proof you can back up.
Use reviews, testimonials, client logos, case studies and accreditations only if they're real, current and yours to use, with permission where needed. Attribute testimonials to a name and role. Never round up a review count or invent a result; if a number changes, like a review total, recheck it before every launch.
- Answer the questions that stop people.
Collect the questions your team hears before people commit: price range, process, timing, what's included, who does the work. Answer them on the page in short sections or an FAQ. Every unanswered question is a reason to wait.
- Keep the form short.
Ask only for what you need to reply well, usually name, a way to contact them and a short message. Every extra field is one more reason to stop. Our guide on how to design a contact form people finish covers labels, errors and spam handling.
- Make it fast and stable on a phone.
Visitors from ads and social posts are often on a phone, sometimes on mobile data. Compress the hero image, avoid heavy sliders and video backgrounds, and reserve space so nothing jumps while the page loads. Check the page against the Core Web Vitals thresholds with our website speed test guide.
- Change one thing at a time and compare.
Record enquiries as a key event, then change one element, such as the headline or the form, and compare results over a fair period. Changing several things at once hides which one mattered. Our guide on how to set up conversion tracking shows how to count leads reliably.
If you'd rather have landing pages designed, built and measured for you, our in-house web team designs and develops sites with SEO foundations built in.
Landing pages that work for everyone
A landing page that some visitors can't use loses those enquiries entirely. These are accessibility problems we often find on campaign pages, each tied to a WCAG 2.2 success criterion.
Pop-ups that hide the page. Full-screen promotions block the content for everyone, and a dialog that doesn't take keyboard focus, or can't be closed with the keyboard, traps some visitors. Google's own guidance is to use small banners instead of interstitials, and not to cover the whole page. Sticky bars must never hide the focused element, which WCAG 2.2 added as Focus Not Obscured.
Sliders and moving backgrounds. Anything that moves automatically for more than five seconds needs a way to pause, stop or hide it. Auto-advancing carousels also move content away before people finish reading. A single strong hero usually does the job better.
Buttons people can't read or hit. Button text needs at least 4.5:1 contrast with its background, including text over images. Targets should be at least 24 by 24 CSS pixels or well spaced. Button labels should describe the action, so a screen reader user hears "Request a site visit", not "Learn more".
Layouts that break when zoomed. Check the page at 320 CSS pixels wide and at 200 percent zoom. Headings should describe each section, so people scanning by heading can find the price, the process and the form.
Our website accessibility testing checklist covers the full set of manual checks.
Troubleshooting
Visitors leave without scrolling
Cause: the first screen doesn't confirm they're in the right place. The headline may not match the ad or email, the hero may be a photo with no clear message, or the page may still be loading when they decide. On phones, a cookie banner and a large hero image together can push every word of the offer below the fold.
Fix: compare the first screen with the ad side by side and make the promise identical. Put the headline, one line of supporting text and the main action in the first screen on a common phone size. Shrink or remove the hero image if it delays the content. Check the page in your analytics by device; if mobile visitors leave far more often than desktop ones, test on a real phone over mobile data.
People click the button but don't finish the form
Cause: the form asks for more than the visitor expected, or something in it fails. Common culprits are long forms, required fields that feel intrusive, such as budget or company size, confusing errors, a puzzle CAPTCHA, or a form that breaks for keyboard or autofill users. A button that opens a separate page with a different message also loses people.
Fix: use the form start and submit events to see where people drop out. Remove every field you don't need to reply, make the rest clearly labelled and test the form with only a keyboard and with browser autofill. Replace puzzle CAPTCHAs with less intrusive spam checks. Keep the form on the landing page itself, or make sure the next page repeats the offer.
Google Ads rates the landing page experience below average
Cause: Google compares your landing page with other advertisers' pages for the same searches, and a "below average" status means the page looks less relevant or useful to people who clicked. Typical reasons are a page that doesn't mention what the ad promised, a generic home page used as the destination, slow loading on mobile or intrusive pop-ups.
Fix: send each ad group to the page that matches its keywords and promise, rather than the home page. Repeat the searched-for service in the headline and the opening copy. Speed the page up on mobile and remove interstitials. Remember that Quality Score is a diagnostic, not a goal, so judge the changes by enquiries recorded in analytics as well as the status.
Common questions
How long should a landing page be?
As long as it takes to answer the questions that stop someone acting, and no longer. A simple offer people already understand can work with a short page. A bigger decision, such as hiring a firm for a project, usually needs more detail on process, proof and next steps. Put the offer and the main action near the top either way.
Should a landing page have the site's main navigation?
It depends on the traffic. For paid campaigns with one clear goal, many teams trim the navigation so the page stays focused. For pages people reach from search, keep it, because visitors may need to check who you are before acting. Either way, keep a link to your home page and contact details so nobody feels trapped.
How many calls to action should a landing page have?
One main action, repeated where it makes sense, such as after the hero, after the proof and at the end. A secondary option, like calling instead of filling in a form, is fine if it leads to the same outcome. What hurts is several competing offers on one page, because the visitor has to choose before they've decided to act.