Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Templates

Landing Page Brief Template

A landing page brief template: goal and conversion, traffic sources and message match, audience and objections, sections, proof, form fields and tracking.
Templatebeginner9 min readUpdated

What this template is for

Use the brief whenever a page is built or rebuilt to receive campaign traffic: a paid search destination, a page for an email or social campaign, a lead generation page for an event or offer. It also suits a product or service page that has become the main destination for paid traffic and needs rebuilding with that job in mind. It is not needed for a small copy change on an existing page; that is a test or an edit.

The brief has neighbours with different jobs. The creative brief directs the ads that send traffic and the content brief directs articles written to be found in search. Once the page exists, the landing page checklist verifies it before launch and the landing page audit scorecard grades it once it has traffic. The brief comes before all of those: it specifies a page that does not exist yet, so the checklist and the audit have something to compare the result with.

The brief is short on purpose. A designer needs the decisions, not the reasoning that led to each, and a developer needs the form and tracking requirements stated exactly. Everything longer belongs in the guides linked below or in an appendix.

The template

Copy the table into a document and keep the field names. Fill the first two rows before anything else; if the page cannot name one action and the promises that bring people to it, the rest will not hold together.

FieldWhat to write
Page goal and conversionThe single action the page exists for, and the key event that records it
Traffic sources and promisesEach ad group, email or link that sends traffic, and the promise each makes, so the page can keep it
Audience and objectionsWho arrives, what they already know, and the objections the page must answer
Headline and offerThe headline that matches the main source, and the offer stated plainly with its conditions
Section orderThe sections from first screen to footer, with the job of each
ProofReviews, logos, credentials, guarantees and numbers the page may use, with where each is substantiated
Form or checkoutFields required, fields removed and why, validation and error messages, and the success state
Speed and mobile requirementsPage weight, image and script limits, and what the mobile first screen must show
TrackingEvents, parameters and the conversion action the page feeds
Test ideas and ownerHypotheses held back for later tests, the page owner and the review date

Attach the sources' ad copy or email draft to the brief. The designer should read what the visitor read one click earlier.

How to fill each section

Page goal and conversion

Write the one action the page exists for and the event that records it. The anatomy of a landing page guide starts from this rule: a Landing Page has one job, and every section either moves the visitor towards it or answers a reason not to. Secondary actions, such as a phone number for people who will not fill a form, can stay, but name them as secondary so they do not compete with the main call to action.

Traffic sources and promises

List every source that will send traffic and copy the promise each makes. The message match guide explains why the click and the page must agree at the level of words, offer and design, and how keyword intent should decide which page a search lands on. If sources make different promises, either the page keeps all of them or the sources need different pages; the brief is where that choice becomes visible. Message Match failures are usually decided here, not in design.

Audience and objections

Describe who arrives and what they already know, then list the objections the page must answer in the order they matter. The audience research guide covers where those objections come from: sales calls, support tickets, reviews, search queries and interviews. Write objections in the visitor's words. "Is it going to hurt?" is briefable; "address pain concerns" is not.

Headline and offer

Write the headline that matches the main source and state the offer exactly: what the visitor gets, at what price, with what conditions. The message match guide treats the headline as the first test the visitor applies, so it should repeat the promise of the click in recognisable words. If dynamic text or variants will change the headline by source, list them here.

Section order

List the sections from the first screen to the footer and give each one job. The anatomy guide explains how order follows intent: visitors who arrive ready to act need the action early, while visitors who arrive uncertain need the reasons first. A section with no job written beside it is decoration and is the first candidate to cut.

Proof

List every piece of proof the page may use and where it is substantiated: the review platform, the client who approved a logo, the document behind a figure. The trust and proof guide covers types of Social Proof, placing proof near the decision it supports, and why claims must be accurate and current. A proof row with no source should not reach the designer.

Form or checkout

Write the fields the form keeps, the fields removed and why, the validation and error messages, and what the visitor sees after submitting. The forms guide explains that every field has a cost and that qualification can often happen later, and covers labels, input types, errors and accessibility. The page must be usable with a keyboard and a screen reader; the Web Content Accessibility Guidelines are the reference the developer builds to.

Speed and mobile requirements

State the limits the page must meet and what the mobile first screen must contain. The speed and mobile guide covers page weight, third-party tags, Core Web Vitals and thumb reach. Check the device split of the sources in analytics, and describe the mobile first screen explicitly rather than leaving it to the desktop layout to collapse.

Tracking

Name the events the page sends, their parameters and the conversion action they feed in each ad platform. The key events and conversions guide explains how to choose key events and how they relate to platform conversions. Write the exact event names so the developer and the analyst use the same ones, and include the success state as the trigger, not the button click.

Test ideas and owner

Write the ideas the team argued about and deliberately held back, the page owner and the date the page is reviewed. Each held-back idea becomes a test later; the experiment hypothesis template turns one into a testable statement. The conversion rate calculator helps set the baseline the review will compare against.

Filled example

Below, the brief is completed for an invented business. The figures, names and claims are illustrative.

Illustrative example — not a real result

Elsworthy Dental Studio: implant consultation landing page brief

FieldElsworthy's brief
Page goal and conversionBook a paid implant consultation (£75, deducted from treatment). Key event consultation_booked, fired on the booking confirmation state. Secondary: tap-to-call, tracked as call_click
Traffic sources and promisesSearch ad group IMPLANTS: "Dental implants in Harrogate, fixed-fee plans". Ad group IMPLANT-COST: "Implant prices explained, from £2,400". Email to the practice's list of lapsed patients: "Missing a tooth? Book a consultation with Dr Patel". All three land on /implants
Audience and objectionsAdults, mostly over 45, who have lost one or more teeth or wear a partial denture. Many have asked their own dentist and been referred out. Objections, in order: "How much will it really cost?", "Will it hurt?", "How long does it take?", "Am I suitable?", "Who will do it?"
Headline and offerHeadline: "Dental implants in Harrogate, with a fixed-fee plan". Sub-headline variant for IMPLANT-COST: "Single implants from £2,400, with every fee shown before you start". Offer: £75 consultation with a 3D scan, deducted from treatment if you go ahead
Section order1 Headline, offer, booking button and phone (first screen). 2 Fees table: what is included and what is not. 3 "Will it hurt?": sedation options and recovery. 4 Timeline from consultation to final crown. 5 The clinician: Dr Anya Patel, qualifications and registration. 6 Reviews. 7 Suitability questions. 8 Booking form. 9 Finance options and practice address
ProofAverage review rating and count from the practice's review platform profile, refreshed monthly. Dr Patel's registration number and postgraduate certificate, from the practice records. Before-and-after photos only with written patient consent on file. No success-rate figure: the practice has no audited figure to substantiate one
Form or checkoutKeep: first name, mobile number, email, preferred day and time. Removed: date of birth and medical history (taken at the consultation), postcode (not needed to book), "how did you hear about us" (tracking answers it). Inline errors under each field in plain words. Success state: confirmation with the booked slot and a link to add it to a calendar
Speed and mobile requirementsPage under 1 MB on first load; hero image compressed, no autoplay video; booking button and phone number visible on the mobile first screen without scrolling; tap targets large enough for a thumb
Trackingconsultation_booked with parameters source_page and slot_type, marked as a key event and imported to Google Ads as the primary conversion. call_click as secondary. UTMs on the email link per the house convention
Test ideas and ownerHeld back: showing finance monthly costs in the first screen; a short video of Dr Patel explaining the procedure. Owner: practice manager, Lucy Hartley. Review on 30 June against the first eight weeks of bookings

The fees table moved up to second position after the first draft: two of the three sources promised clarity on price, and the draft had placed it sixth, after the reviews.

Common mistakes

  • Two goals on one page. A page that asks for a booking and a brochure download splits attention and muddles the conversion count. Name one goal and make everything else secondary.
  • Briefing without the ads. A page written without the ad copy cannot keep the ad's promise. Attach the sources to the brief.
  • Objections written as topics. "Address cost" gives a designer nothing. Write the visitor's question and the page will answer it.
  • Proof without a source. Ratings, logos and figures that nobody can substantiate create risk and erode trust when challenged. Every proof row names where it comes from.
  • Fields kept by habit. Each field costs completions. Ask what the business does with the answer before the first call, and move the rest later.
  • Desktop first. A first screen designed for a wide monitor often hides the action on a phone. Describe the mobile first screen in the brief.
  • Tracking the button, not the result. A click on submit counts failed submissions too. Fire the event on the success state.

The creative brief for the ads that feed the page and the experiment hypothesis for the tests that follow are in the templates library.

Terms used on this page

Tools to try

Also related

Sources

  1. Website Forms Usability: Top 10 Recommendations — Nielsen Norman Group
  2. Web Content Accessibility Guidelines (WCAG) — W3C

Related