Copy this Google Ads landing page brief before requesting a design.
A useful landing-page brief is a decision contract between the media buyer, business owner, copywriter, designer, developer and sales team. It should explain which search situation the page serves, what the ad promises, what proof exists, who should respond and how the team will know that the handoff worked. Without that agreement, every specialist can complete a task while the campaign still loses the lead between the click and the first sales response.
Copy the fields below into the project document. Keep each answer specific enough that another person could challenge it. If the same answer applies to several unrelated ad groups, the page may be too broad or the campaign structure may need work before production starts.
| Brief block | Required decision | Example format |
|---|---|---|
| Campaign job | The one commercial action the page must support | Book an eligible assessment—not collect every possible inquiry |
| Search situation | What the visitor is trying to resolve now | Service + problem + market + urgency |
| Ad promise | The claim the first screen must continue honestly | Same service, availability, scope and next step |
| Buyer fit | Who qualifies, who does not and what changes routing | Service area, property or company type, timing and need |
| Evidence | Proof available for each important claim | Process, credentials, real examples, policy or accountable identity |
| Conversion | The observable action that creates a usable lead | Successful form, confirmed booking or connected call |
| Handoff | Where the lead goes, who owns it and when they respond | Inbox or CRM, named owner, backup route and response expectation |
| Decision rule | When the team will review and what can change | Technical QA at launch; commercial judgment after enough qualified traffic |
Start with the business outcome and work backward to the page action.
The page should not optimize for a form submission that sales cannot use. Define a qualified lead in operational terms: eligible service, relevant market, contactable person, realistic timing and any commercial threshold that genuinely changes the response. Then decide the smallest amount of information needed to route that person responsibly.
Separate the page conversion from the business conversion. A successful request can be measured immediately; qualification, appointment, proposal and customer outcomes happen later. The brief should name who records each stage so the advertising team does not mistake raw volume for profitable demand.
- Primary business outcome: the eventual customer action the campaign should influence.
- Page conversion: the successful online action the page can verify directly.
- Qualification rule: the consistent criteria used after the inquiry arrives.
- Sales stages: contacted, qualified, booked, proposed, won or lost—with a reason where useful.
- Feedback owner: the person responsible for returning lead-quality data to the campaign review.
Map each ad group to one honest message path.
Google describes landing-page experience as the relevance and usefulness of the destination to people who click the ad. The practical brief therefore begins before the headline: list the priority search situation, the ad message, the page promise and the action as one row. Split the path when the service, urgency, geography, evidence or next step becomes materially different—not for every close keyword variation.
| Input | Question to answer | Page consequence |
|---|---|---|
| Search intent | What problem or purchase is the person naming? | The H1 and first explanation confirm that situation |
| Ad promise | What specific expectation earned the click? | The first screen continues it without expanding the claim |
| Eligibility | Which visitors can the business actually serve? | Fit and exclusions appear before unnecessary form effort |
| Proof | What evidence makes this promise credible? | Evidence sits near the claim or commitment it supports |
| Action | What is the responsible next step for this intent? | One primary CTA describes exactly what happens next |
Write the offer, objection and proof inventory before the wireframe.
A wireframe cannot solve missing commercial evidence. The brief should state what the visitor receives, what commitment is required, when the business responds and what is not promised. It should also list the objections that a suitable buyer must resolve before acting—availability, price context, trust, implementation, eligibility or risk—and attach evidence to each one.
Use only evidence the business can verify. Real process detail, accurate policies, accountable people, owned demonstrations and clearly labeled hypothetical examples are stronger than invented testimonials or performance lifts. If proof does not exist yet, record the gap and decide whether the page can launch responsibly without it.
- Offer: what the visitor asks for and what they receive next.
- Commitment: fields, call length, appointment, payment or access required.
- Response expectation: who replies, by which channel and within what operating window.
- Objections: the five questions that stop an otherwise suitable buyer.
- Proof inventory: the source, owner and placement for each supporting fact.
- Prohibited claims: guarantees, urgency or credentials the business cannot substantiate.
Specify qualification and lead routing as part of the product.
Every field must have a job. Ask whether the answer changes eligibility, routing, preparation or priority. Remove fields that sales ignores; add a field only when it prevents a costly back-and-forth or routes the lead to a meaningfully different response. State the privacy context and avoid collecting sensitive information the business does not need through an ordinary marketing form.
The brief should also describe failure states. A success message is not proof that the lead reached a person. Test the destination inbox or CRM, notification fallback, source fields, duplicate behavior and the response owner. If delivery fails, the visitor needs a useful recovery route and the team needs an observable error—not a silent loss.
| Handoff field | Decision to record |
|---|---|
| Form inputs | Required, optional, validation rule and why the answer is needed |
| Hidden context | Landing page, source, campaign, ad group or other permitted attribution data |
| Destination | Exact inbox, CRM pipeline, booking system or call destination |
| Owner | Primary responder, operating hours and backup when unavailable |
| Success state | What the visitor sees and what has actually been confirmed |
| Failure state | Visible recovery path, internal error signal and retry behavior |
| Outcome feedback | Who records qualification and final disposition for campaign review |
Define the measurement contract before installing tags.
Google Ads supports separate conversion actions for different website actions and calls. Google Analytics recommends `generate_lead` when a person submits a form or requests information, and its lead-generation event set can continue through qualification and sales outcomes. The names in the brief should describe real states, not visual interactions that merely look like progress.
Preserve click and campaign context deliberately. Google Ads auto-tagging can add a GCLID, while ValueTrack parameters can supply campaign, ad group, device and other click context. The implementation depends on the analytics, consent and CRM stack; the brief should name which fields must survive redirects, form submission and lead delivery, then test them without assuming the platform will carry everything automatically.
| Event or record | Fire or update when | Do not confuse it with |
|---|---|---|
| form_start | A visitor begins interacting with the lead form | A successful inquiry |
| generate_lead | The server or destination confirms the valid request | A button click or client-side attempt |
| phone_click | A person taps the trackable phone action | A connected or qualified call |
| qualify_lead | The business applies its documented fit criteria | Any contactable submission |
| close_convert_lead | The agreed customer outcome is recorded | An appointment or proposal |
| delivery_error | The routing layer cannot complete the handoff | A visitor validation error |
Worked example: a hypothetical emergency plumbing campaign.
This example is hypothetical and demonstrates the brief—not client performance. Assume a plumbing business can serve occupied residential properties in one defined area during its staffed response window. The campaign is limited to urgent leak-response intent; planned remodeling and commercial contracts require different promises and routes.
| Brief field | Hypothetical decision |
|---|---|
| Search situation | Homeowner searching for urgent burst-pipe or active-leak help in the stated service area |
| Ad promise | Request an urgent response assessment during staffed hours; no claim of guaranteed arrival time |
| First-screen message | Urgent residential leak response, eligible area, operating window and the next step |
| Buyer fit | Residential property, active water issue, service ZIP and contactable decision-maker |
| Proof | Accurate license or insurance details where applicable, named response process and real operating contact |
| Primary conversion | A validated request delivered successfully with phone, ZIP, issue and urgency |
| Routing | Urgent inbox or dispatch queue plus phone fallback; named on-duty owner acknowledges the request |
| Measurement | Form start, successful lead, call click, service-area qualification, booked visit and outcome |
| Exclusions | No invented price, availability, diagnosis or arrival guarantee; out-of-area requests receive a clear response |
Turn the brief into launch acceptance—not a subjective reveal.
Approve the page against observable conditions. The final URL loads over HTTPS, the first screen matches the assigned ad promise, mobile users can read and act, form labels and validation work, key evidence is accurate, analytics fires at the correct state and the lead arrives with the expected context. Google also recommends checking mobile usability, simple navigation and loading speed as part of the destination experience.
Technical acceptance can happen before the first paid click. Commercial conclusions cannot. Record the baseline and the minimum evidence required for a decision, then rank the first hypotheses in advance. This prevents the team from changing the headline, offer and form simultaneously after a handful of visits and learning nothing from the spend.
- Test the exact final URL, query parameters and any redirects used by the ads.
- Verify the canonical, title, indexation choice and crawler behavior intended for the page.
- Complete the primary action on a phone and desktop using realistic test data.
- Confirm the success event, lead payload, destination, backup notification and visible response expectation.
- Record the launch version, campaign mapping and first three evidence-based tests.
- Review qualified outcomes and sales feedback—not only the page conversion rate.
Google Ads landing page brief FAQ.
What should a Google Ads landing page brief include?
Include the campaign job, search situation, ad promise, buyer fit, offer, objections, verified proof, primary CTA, form fields, attribution requirements, lead destination, response owner, analytics events, acceptance checks and the evidence threshold for post-launch decisions.
Should every Google Ads ad group have a different landing page?
No. Use the fewest pages that can preserve honest message match. Split the destination when the service, audience, geography, proof, urgency or next action becomes materially different—not for minor keyword variations that share the same buying situation.
Which conversion should a lead-generation landing page track?
Track the successful action the business can verify, such as a delivered form, confirmed booking or connected call. Use separate records for form starts, phone clicks, qualified leads and acquired customers so early interactions are not mistaken for business outcomes.
How long should the brief be?
Long enough to make the commercial, content, technical and ownership decisions explicit. A focused campaign may fit into one or two pages plus an intent map; a regulated or integrated offer may need supporting evidence, data and approval requirements.
Is this template a landing page checklist?
No. The brief assigns the page's job, evidence, measurement and ownership before production. A launch checklist verifies that the built page and handoff satisfy those decisions before paid traffic begins.