Landing page requirements decide how many review rounds a page takes, and most second rounds trace back to an input nobody wrote down: the form's destination, the conversion event, the consent rule or the final headline. Google's own destination rules show how little room there is for guessing: a page that returns an HTTP error to Google's AdsBot crawler, or that redirects to a different domain from the final URL, is disapproved before it serves a single ad (Google Advertising Policies Help).
This guide is the requirements template we would want in hand before building a campaign page, section by section, with the external rules each line answers to: Google's ads and Search documentation, Meta's deduplication rules, WCAG 2.2, web.dev's Core Web Vitals and Nielsen Norman Group's form research.
Why landing pages go to a second round
A landing page is a day or two of build work. The waiting is what takes weeks: for the real headline, the logo in SVG, the CRM field the lead should land in, the approved consent text.
The usual pattern is that round one is built with placeholders and round two replaces them. Real headlines are longer than "Headline goes here", so the layout changes too. A third round appears when someone tests the form on a phone and finds the notification goes to an inbox nobody reads.
That is a requirements problem, not a design one. If you are still choosing who builds the page, our guide to what a landing page design agency should deliver covers the scope side. This page covers the inputs.
The landing page requirements template, section by section
| Section | What to hand the builder | Owner | Done when |
|---|---|---|---|
| 1. Goal | One conversion action and the number it is measured by | Marketing lead | The action is a single verb: book, download, start |
| 2. Traffic and audience | Channels, campaigns, ad groups or segments sending traffic | Paid media | Every source has its headline promise written down |
| 3. Copy | Final headline, subhead, body, proof, CTA labels, FAQ | Copywriter | Approved text in one document, no placeholders |
| 4. Assets | Logo in SVG, images at final crop, video files, customer logos with permission | Design | Every asset named and in one folder |
| 5. Structure | Section order, or a wireframe, with mobile order if different | Marketing lead | Each section maps to an objection |
| 6. Form | Fields, required or optional, validation, thank-you state | Marketing and sales | Field list signed off by whoever works the leads |
| 7. Routing | CRM, list or inbox, notification recipients, lead owner | Sales operations | A test lead arrives in the right place |
| 8. Tracking | Conversion events, pixels, click IDs, UTMs, consent behaviour | Analytics | Events fire once, in a test, with consent states checked |
| 9. Technical | URL, indexing, meta title, Open Graph image, redirects | Builder | Live URL returns 200 and passes the destination rules |
| 10. Acceptance | Performance, accessibility and browser thresholds | Builder and reviewer | Every line has a measured value next to it |
| 11. Review | Approver, feedback format, number of rounds, launch date | Project owner | One name, one document, one date |
Source: Octo Agency template, built on the rules cited in the sections below
Sections one to five are what most briefs already contain in some form. Sections six to eleven are where the second round hides. The rest of this page goes through the ones that need more than a line.
Goal and audience: one action, one promise per source
The conversion. Write the action as a verb and the number that measures it: "book a demo, measured as qualified demo bookings in the CRM", not "generate leads". If there is a secondary action, say which one wins when they compete for space.
The traffic. List every source and what it promised. A search ad about compliance software and a LinkedIn ad about an audit deadline make two different promises, and the page has to keep both. Our PPC landing page best practices cover message match in detail; for the requirements, paste each ad's headline next to the page headline it maps to.
The objections. Ask sales for the three questions prospects ask before they convert, and give each one a section.
Copy and assets: final, plain and in one place
Copy that changes after the layout is built is the most common cause of a second round. Final does not mean perfect; it means approved, and not about to grow by forty words.
Keep it plain. Unbounce's 2024 Conversion Benchmark Report, covering more than 41,000 landing pages, found pages at a 5th to 7th grade reading level converted at 11.1%, more than twice the 5.3% for professional-level writing. The same vendor data found conversion fell as word count, reading time and long words rose. That is correlation across industries, not proof for your page, but it is a sound default: short sentences, common words, one idea per section.
Assets and proof. Hand over the logo as SVG, photographs at their final crop and customer logos with written permission. Quotes need a name, a role, a company and the person's consent. Both are slow to collect, so they belong in the requirements, not the review.
Form fields and routing: decide before the build
Fields. List every field, mark it required or optional, and give a reason for each. Nielsen Norman Group's form recommendations remain the cleanest checklist: cut fields that can be derived or collected later, use a single column, do not use placeholder text as labels, keep optional fields to one or two, and show specific errors that do not rely on colour alone. Our form conversion statistics collect the data on form length; the requirement is the signed-off list.
States. Write the error text, the thank-you message or redirect, and what happens to a duplicate submission.
Routing. Name the CRM object, the notification inbox and the person who owns follow-up. Then require one test lead from the live URL that arrives there with every field mapped. A form that submits but lands in a forgotten inbox is the most expensive bug a landing page can have, because nobody sees it until the campaign report.
Tracking and consent: requirements, not intentions
"Add tracking" is not a requirement. The table below is what a tracking section should specify, with the rule that makes each line necessary.
| Requirement | What to specify | Why it matters |
|---|---|---|
| Primary conversion event | Event name, the trigger (thank-you state, not button click), the platforms it goes to | One definition across Google Ads, Meta and analytics |
| GCLID capture | Hidden form field filled from the URL, stored with the lead in the CRM | Google's offline conversion import matches on the stored GCLID; auto-tagging must be on |
| Import window | Which connector imports offline conversions | Salesforce and HubSpot connectors look back 14 days on the first run; file and cloud imports look back 90 |
| Enhanced conversions for leads | Whether the hashed email is sent with the conversion | Google matches SHA256-hashed first-party data to ad interactions |
| Meta deduplication | Shared `event_id` and `event_name` for Pixel and Conversions API | Meta discards a duplicate only if both match within 48 hours |
| Consent mode | Basic or advanced, regional defaults, banner provider | Consent mode v2 requires `ad_user_data` and `ad_personalization` as well as `ad_storage` and `analytics_storage` |
| UTM convention | The exact parameter values per channel | Reports group on the strings, so "LinkedIn" and "linkedin" split the data |
Sources: Google Ads Help (GCLID, enhanced conversions), Meta for Developers, Google for Developers consent mode documentation
Basic or advanced consent. This is a privacy decision, not a build one. In Google's documentation, basic mode holds tags back until the visitor uses the banner; advanced mode loads them at once with denied defaults and sends cookieless measurements until consent is granted. The two produce different numbers, so write the choice and the reason down.
Test both states. Submit once with consent granted and once denied, and note what each platform received. It takes ten minutes and settles the usual argument about why the numbers disagree.
Technical and accessibility acceptance criteria
An acceptance criterion is a line with a threshold. Without one, review comments drift into taste. The thresholds below come from the people who define them, so nobody has to argue about them.
| Check | Threshold | Source of the rule |
|---|---|---|
| Largest Contentful Paint | 2.5 seconds or less at the 75th percentile, mobile and desktop | web.dev Core Web Vitals |
| Interaction to Next Paint | 200 milliseconds or less | web.dev Core Web Vitals |
| Cumulative Layout Shift | 0.1 or less | web.dev Core Web Vitals |
| Text contrast | At least 4.5:1, or 3:1 for large text | WCAG 2.2, 1.4.3 (AA) |
| Tap and click targets | At least 24 by 24 CSS pixels, or enough spacing | WCAG 2.2, 2.5.8 (AA) |
| Form labels and errors | Labels on every field; errors identified and described in text | WCAG 2.2, 3.3.1 and 3.3.2 (A) |
| Images | Text alternative for meaningful images; decorative images ignored | WCAG 2.2, 1.1.1 (A) |
| Ads destination | Works on common browsers and devices, crawlable by AdsBot, no redirect to another domain | Google Advertising Policies Help |
| Social preview | `og:title`, `og:type`, `og:image` and `og:url`, plus `og:image:alt` | Open Graph protocol |
Sources: web.dev (2024-10-31), W3C WCAG 2.2 Recommendation (2024-12-12), Google, ogp.me
A new URL has no field data on launch day, so require a lab test on a mobile profile then and a field check about four weeks later.
Indexing. Paid-only variants and near-duplicates usually should not appear in search. Google's Search Central notes that `noindex` only works if robots.txt does not block the page, because a blocked page is never crawled. Write "noindex meta tag, not blocked in robots.txt", in those words.
URL. Fix the final URL before the ads are written. A slug changed after launch breaks every ad, email and QR code that points at it.
Review rules that keep it to one round
One approver. One person says yes or no. Others comment through the approver, who resolves conflicts before they reach the builder.
One feedback document. Every comment is tied to a section and labelled as a bug (the page misses a requirement), a change (the requirement changed) or a preference. Bugs are fixed in the round, changes are scoped, preferences are the approver's call.
One round, defined. Write how many rounds the price includes. Our four-week marketing-site process reviews at fixed points with one consolidated set of comments, and we would run a single landing page the same way on a shorter clock: staging link, one review window, one document, fixes, launch.
For the trade-offs between templates, builders and agencies, see what a landing page costs in 2026.
What this means for your next landing page brief
Start from the eleven sections and fill in what you know. Each blank is a question that would otherwise reach the builder mid-project, so give it an owner and a date. Do not book the build until the form routing, the tracking plan and the approver are settled, because those three cause most rework.
For the builder, the document is also the test plan: every "done when" line and threshold can be checked by someone who was not in the room. When the page meets every line, the talk after launch turns to what to test next.
Our marketing websites service page explains how we scope landing pages and the sites around them.


