> ## Documentation Index > Fetch the complete documentation index at: https://docs.snowdoughnut.com/llms.txt > Use this file to discover all available pages before exploring further. # Landing page briefs concepts > What a landing page is for, the decisions that make one convert, and how the brief captures each of those decisions before anyone builds. Read this to fill in a landing page brief with intent and to judge whether a page is set up to do its job. A landing page is a single page built to turn one kind of visitor into one kind of action. The brief is the document that records the decisions behind it before design or code starts. This guide explains the decisions that shape a landing page: the job it does, who it speaks to, the offer and message, the objections it answers, the proof it rests on, and how success gets measured. For each one, it shows what the decision is, why it matters, and how the brief captures it. Use it to fill in a brief with intent, or to check whether an existing page is set up to convert. ## How a landing page differs from a regular page A regular website page can serve several purposes at once: explain the product, rank in search, tell the brand story, and link out to a dozen places. A landing page narrows to one. A visitor arrives from a specific source, usually an ad or an email, and the page exists to move them toward a single action. That constraint is the whole advantage. When a page has one job, every section can support it, and you can tell afterward whether it worked. When a page has several jobs, the sections compete for attention and the result is hard to measure. The rest of this guide walks through the decisions that keep a page focused, in the order the brief asks for them. ## The one job of the page Every landing page should have a single job and a single action that counts as success. The job is the outcome the page drives toward. The conversion action is the specific thing a visitor does that marks that outcome: submitting a form, booking a call, starting a trial, buying. When both are explicit, the rest of the work falls into place. The designer knows what to make prominent, the copywriter knows what every section drives toward, and the team can measure whether the page did its job. A page can still carry secondary actions, a newsletter opt-in or a link to a case study. Naming the one action that matters most keeps those secondary paths from competing with it. A page asked to serve two primary goals equally tends to help neither. For example, a page for cold paid-social traffic might have one job: start a free trial. The newsletter signup in the footer is secondary and the page is not built around it. **In the brief:** state the job in one sentence and name the single conversion action. Mark any secondary actions as secondary. ## Who the page speaks to A landing page speaks to one customer profile. Everything else on the page, the message, the objections, the proof, follows from who that customer profile is. Pull the audience from a shared source rather than describing it fresh each time. When every campaign references the same definition, the copy on the page matches how those people are described everywhere else, and no one maintains two drifting versions of the same description. A page can technically target more than one audience, but each audience it tries to address at once splits the message. A page for DevOps leads and a page for procurement managers want different openings, so two audiences usually means two pages. **In the brief:** link the audience entry from your customer profile library. Do not paste a fresh description. ## Traffic source and awareness Where a visitor comes from shapes the mindset they arrive in, which changes how the page should open. Someone who clicked a branded search result already knows the company and wants to get to the point. A visitor from a cold paid-social ad has never heard of it, so the page has to establish the problem before it pitches anything. Awareness level captures the same thing from the visitor's side: how much they already grasp about the problem and the product before they land. Match the opening to that mindset. A high-intent search visitor often wants pricing and process early; a cold visitor may need convincing that the problem is even theirs. **In the brief:** record the traffic source, the awareness level, and the ad or keyword theme. If the campaign brief already holds this, link to it and treat the campaign brief as the source of truth. ## The offer and the core message The offer is what the visitor is asked to take: the trial, the demo, the download, the purchase. The core message is the one idea they should leave with even if they read nothing else. These come before any talk of layout or sections. A page can be well structured and still convert poorly when the offer and the message underneath it are fuzzy. The offer is the transaction; the message is the reason it's worth making. A page can name its offer clearly and still leave out why anyone should want it, which is how a page ends up looking complete without converting. For example, the offer might be a 30-day free trial with no card required, and the core message might be that a team can ship to production in an afternoon instead of a sprint. **In the brief:** write the offer, the core message, and why it matters now. ## Message priorities A list of possible messages is not the same as a plan for using them. Priorities put the messages in order so the copywriter and designer know what leads, what supports, and what can be cut if the page runs long. Without that order, every review turns into a debate about which point belongs at the top. With it, feedback gets concrete: moving a message up is a conversation about the priority list, not a general opinion about the page. **In the brief:** rank the messages, with the lead message first and supporting messages below it. ## Objections A visitor converts when they believe the right things and stop doubting the wrong ones. Objections are the doubts that hold them back: cost, time, trust, whether the product actually works. Listing each objection and pairing it with how the page answers it turns a vague "make it persuasive" into specific work. The copywriter and designer know exactly what to address and where. Which objections matter depends on who is arriving. Pull them from the specific audience and traffic source rather than reaching for a generic list, since the doubts a ready-to-buy visitor carries look nothing like the doubts of someone who isn't yet sure they have the problem. For example, if setup looks like it will take a week, the page can show a one-afternoon setup timeline near the top, before the doubt has a chance to settle. **In the brief:** list the likely objections and, for each, how the page handles it. ## Proof Proof is what makes a claim believable: testimonials, numbers, logos, certifications, results. Each proof point usually maps to a specific claim or objection, and it does its job when a doubting visitor sees the reason to trust the claim right where the doubt occurs. List the proof the team can actually use, not the proof it wishes it had. A testimonial needs permission. A stat needs to be current and defensible. Writing down what genuinely exists keeps the page honest and keeps the copywriter from building around evidence that was never available. **In the brief:** list the specific proof points, with the source, and note anything that still needs permission or verification. ## Lead qualification When the conversion is a lead rather than a direct purchase, volume alone can mislead. A page can bring in plenty of submissions that sales later rejects as a poor fit, so the page looks like it worked while the pipeline does not move. Describing what a useful lead looks like lets the team shape messaging, calls to action, and form fields to attract more of the right people and fewer of the wrong ones. This is a shared understanding of who the page is for, not a mandate to add every filter to the form. The team can apply it lightly or firmly depending on how much volume versus fit the campaign needs. **In the brief:** describe what a qualified lead looks like and what a poor-fit lead looks like, so the difference is explicit. ## Success metrics Naming the metric before launch keeps "did the page work" from becoming a matter of opinion afterward. It also tells the team what the page is optimizing for, which shapes how it gets built: optimizing for cost per qualified lead pushes different choices than optimizing for raw signups. Most pages get revised after launch, and the metric guides what to test next. Setting it now gives the first build a standard to measure against, instead of a page that gets called good or bad based on how it looks in review. **In the brief:** name the primary metric and its target, plus any secondary metrics that matter. ## Owner and links A brief works as a shared source of truth only when someone owns it and it connects to the documents around it. Every brief has one owner: the person accountable for the page from brief to launch, who answers questions and makes the call when linked documents disagree. That is separate from the people doing the work. Naming the developer and the creative roles up front gives every question an obvious destination instead of leaving it to bounce around a channel. A landing page also sits inside a system of other documents, and links are what connect them: * The campaign brief holds the strategy the page serves. * The skeleton is where the page's structure and final copy get filled in, as a separate step after this brief. * The creative briefs cover the ads and assets that drive traffic and set the expectation a visitor arrives with. * The finished-asset links record where the real deliverables ended up once they exist. Link to these live sources rather than copying their contents in. Each document has its own owner and changes on its own schedule, so a pasted copy quietly goes stale. A link that has no destination yet is useful information on its own: it shows what still has to be produced before the page can be built. **In the brief:** name the owner and team, and link the campaign brief, skeleton, creative briefs, and finished assets. Leave a link empty if the document does not exist yet, and note who owns creating it. ## Fill in the brief in order The brief asks for these decisions in a sequence that moves from the page's purpose to its execution. Name the one job, the single conversion action, and the audience the page speaks to. Write the offer, the core message, and the message priorities that order everything else. List the objections and the proof that answer them, and describe what a qualified lead looks like. Name the success metric and target, assign the owner, and link the connected briefs and assets. ## Related resources [**Landing page brief**](/landing-page-standards) The fillable brief that captures every decision in this guide, section by section. [**Customer profile library**](/customer-profile-library-overview) The shared source for audience definitions to link from the brief. [**Marketing campaign brief**](/markeitng-campaign-brief) The strategy the landing page serves, including traffic source and awareness. [**Page skeleton**](/landing-page-skeleton) Where the page structure and final copy get filled in after the brief.