> ## 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.

# Build a landing page

> How a landing page gets briefed, structured, written, tracked, and linked back to the campaign driving traffic to it.

Use this when a campaign needs a destination page, or when an existing page needs rebuilding.

## Before you start

| You need                             | Where it lives                                                 |
| :----------------------------------- | :------------------------------------------------------------- |
| The campaign sending traffic         | [Marketing campaign brief](/marketing-campaign-brief)          |
| The value proposition and objections | [Messaging](/messaging)                                        |
| A named customer profile             | [Customer profile library](/customer-profile-library-overview) |
| Visual rules                         | [Visual identity](/visual-identity)                            |

## The path

<Steps>
  <Step title="1. Read the concepts once">
    [Landing page brief concepts](/landing-page-brief-concepts) explains what a landing page brief is deciding and why. Read it the first time.
  </Step>

  <Step title="2. Fill in the brief">
    Work through [landing page standards](/landing-page-standards): the one action the page exists to produce, the traffic it receives, the objections it has to answer, and the proof it carries.

    The objections come from the optional section in [messaging](/messaging) if you filled it in.
  </Step>

  <Step title="3. Lay out the page">
    Use the [landing page skeleton](/landing-page-skeleton) for section order. The skeleton decides what appears and in what sequence; the brief decides what each section says.
  </Step>

  <Step title="4. Write the copy">
    Each section gets written against the brief. Voice comes from [brand voice and tone](/brand-voice-and-tone). Claims come from the approved claims table in [messaging](/messaging). See [write copy](/write-copy) for the fuller path.
  </Step>

  <Step title="5. Apply the visual system">
    Type scale, spacing, color pairings and imagery all come from [visual identity](/visual-identity). Check the contrast pairings rather than choosing color combinations freshly.
  </Step>

  <Step title="6. Wire up tracking">
    The page has to record what happens on it. Add any new events to the [event tracking plan](/event-tracking-plan) using [event naming conventions](/event-naming-conventions), and make sure inbound links are tagged to [UTM standards](/utm-standards).
  </Step>

  <Step title="7. Review and publish">
    Run the [creative review checklist](/creative-review-checklist) on the built page. Anything with a claim, price, or comparison also goes through [legal review](/legal-review-process).
  </Step>

  <Step title="8. Link it back">
    Record the live URL on the campaign brief in the [campaigns library](/campaign-library-overview), so the page and the traffic driving to it are findable from each other.
  </Step>
</Steps>

## If you're testing the page

A landing page is one of the most common things to test. Don't build variants ad hoc: give the test an ID from [experiment ID](/experiment-id) and brief it properly. See [run an experiment](/run-an-experiment).

## Related resources

* [**Landing page standards**](/landing-page-standards) The workbook.
* [**Landing page skeleton**](/landing-page-skeleton) The section order.
* [**Landing page brief concepts**](/landing-page-brief-concepts) The reasoning.
* [**Write copy**](/write-copy) For the writing itself.
* [**Run an experiment**](/run-an-experiment) If the page is being tested.