Premium Landing Pages

When to use

Use for a product, service, campaign, or waitlist page whose goal is to explain an offer and help a defined audience take an action.

When not to use

Do not apply a fixed section recipe to an authenticated product screen, documentation page, or editorial page with a different user goal. Do not invent positioning or proof to fill missing content.

Inputs and assumptions

Establish audience, problem, offer, differentiator, conversion action, traffic source, proof available, pricing constraints, legal requirements, and existing brand and framework.

Workflow

1. Inspect the current site, routes, content, assets, SEO conventions, and existing components.
2. Write a one-sentence value proposition and identify the reader's main uncertainty.
3. Plan the smallest information sequence that answers: what it is, who it helps, how it works, why trust it, and what to do next.
4. Select only sections with a real content purpose: hero, demonstration, benefits, use cases, pricing, evidence, FAQ, and footer as applicable.
5. Use specific, scannable copy and a clear primary CTA; keep secondary actions visually subordinate.
6. Use authentic product imagery or clearly labeled prototypes. Do not fabricate testimonials, customer logos, metrics, or certifications.
7. Implement semantic headings, descriptive links, accessible forms, responsive layouts, metadata, and appropriate image loading.
8. Test form states, CTA destinations, mobile content order, and page performance.

Decision rules

• Match page content to audience intent and acquisition context.
• A feature list must explain user benefit and product mechanism.
• Pricing and claims must reflect approved, current facts.
• Trust evidence is optional; fabricated proof is never acceptable.
• Keep meaningful content in HTML and avoid text embedded only in images.

Example

For a developer API, show the problem, a short working request/response, supported use case, limits or integration constraints, and a CTA to try the API. A generic three-card feature block is not required if the example explains the product better.

Common failures

• Empty superlatives, vague hero copy, and repeated CTAs with no context.
• A long page that repeats the same value proposition.
• Unverified claims, fake customer marks, or nonfunctional signup forms.
• Shipping only the desktop composition.

Validation

Verify content truthfulness, heading order, CTA destinations, form feedback, keyboard access, mobile reading order, metadata, image alternatives, and that each section supports the stated conversion goal.

Supporting guide

Use the landing-page content and proof guide to build a page brief, map claims to evidence, and review conversion behavior before implementation.