SEO Landing Page Brief With Evidence-Backed Conversion Angles

Create an evidence-backed SEO landing page brief for the supplied keyword, audience, offer, page type, and conversion goal. The deliverable must give writers, editors, SEO reviewers, designers, and compliance reviewers enough detail to build and assess the page without inventing claims or confusing recommendations with completed work.

## Inputs

- Target keyword: [Target keyword]
- Landing page goal: [Landing page goal]
- Audience segment: [Audience segment]
- Offer or product: [Offer or product]
- Search intent notes: [Search intent notes]
- Competitor pages: [Competitor pages]
- Proof points: [Proof points]
- Required internal links: [Required internal links]
- Conversion action: [Conversion action]
- Brand or compliance constraints: [Brand or compliance constraints]
- Buyer awareness stage: [Buyer awareness stage]
- Primary objections: [Primary objections]
- Differentiators: [Differentiators]
- Required sources or citations: [Required sources or citations]
- Page type: [Page type]

## Input and evidence rules

Treat the target keyword, landing page goal, audience segment, offer or product, conversion action, and page type as blocking prerequisites. If any are missing or materially ambiguous, ask concise clarification questions first. If answers are unavailable, return a clearly marked Blocked or Partial brief containing only safe, bounded recommendations; preserve unknowns rather than filling them with invented details.

Competitor pages, proof points, search intent notes, objections, differentiators, internal links, constraints, and required sources are strongly recommended context. When these are absent, identify the resulting evidence gap and explain which recommendations remain provisional.

Reconcile conflicting inputs explicitly. Do not silently choose between contradictory offer descriptions, audience definitions, claims, compliance rules, or conversion actions. Record the conflict, its effect on the brief, and the decision owner needed to resolve it.

Classify material used in the brief as one of the following:

- Supplied fact: explicitly present in the inputs or attached source material.
- Observed evidence: directly visible in content ChatGPT actually accessed during this run.
- Assumption: a bounded working premise that still requires confirmation.
- Hypothesis: an idea proposed for research or testing, not an established fact.
- Unknown: information that is unavailable.
- Conflict: supplied sources that disagree.

## ChatGPT access and action boundaries

Use ChatGPT to synthesize supplied keyword notes, page text, competitor excerpts, analytics summaries, proof documents, brand rules, and internal-link inventories into the brief. Do not imply that ChatGPT inspected a URL merely because a URL was supplied.

If browsing is unavailable or not used, treat linked pages as uninspected and request relevant page text, titles, headings, snippets, or screenshots. If browsing is available and actually used, identify each accessed page, the access date, and the observations supported by it. Distinguish live observations from user-supplied summaries.

This run creates recommendations and a draft brief only. It does not publish or edit a landing page, change metadata, add links or schema, run an SEO crawler, measure rankings or conversions, conduct an experiment, obtain legal approval, or confirm implementation. Never describe an item as implemented, tested, measured, verified, approved, published, deployed, or completed without corresponding execution evidence supplied in the inputs or produced through a capability actually used during this run.

Do not invent search volume, rankings, traffic, conversion rates, customer results, testimonials, logos, certifications, product capabilities, prices, guarantees, citations, competitor content, or legal conclusions. Do not copy competitor language. Avoid keyword stuffing, doorway-page tactics, fake scarcity, misleading urgency, unsupported superlatives, and schema for content that will not be visible on the page.

Do not expose confidential customer data, personal data, credentials, or private analytics. Recommend redaction or aggregation where supplied evidence contains sensitive information. Claims involving legal, medical, financial, employment, privacy, security, or other regulated matters must remain pending qualified human review.

## Brief development workflow

1. Validate the blocking prerequisites and classify the supporting materials.
2. Determine the most defensible primary intent and any secondary intent. Separate evidence-based conclusions from hypotheses requiring a live SERP review.
3. Map the audience's problem, desired outcome, awareness stage, objections, decision criteria, and trust requirements to the offer.
4. Review only competitor material that was supplied or actually accessed. Identify patterns, gaps, proof approaches, CTA approaches, and differentiation opportunities without copying.
5. Build conversion angles that connect an audience need to a documented offer value, admissible proof, an objection, and a relevant CTA.
6. Design page architecture around intent satisfaction and conversion progression rather than keyword frequency.
7. Specify metadata, topic coverage, internal links, citations, and eligible structured data. Mark recommendations that require CMS, SEO, legal, or engineering validation.
8. Audit claims and proof. Downgrade or remove angles that lack sufficient support.
9. Run the acceptance checks below and hand off unresolved items with owners and required evidence.

## Required deliverable

### 1. Brief status and objective

State the handoff status as Ready for writer review, Partial, or Blocked. Do not use Approved or Published unless documentary evidence supports that state.

Include the target keyword, page type, landing page goal, audience, offer, awareness stage, conversion action, constraints, blocking gaps, and a one-sentence strategic premise. Separate supplied facts, assumptions, unknowns, and conflicts.

### 2. Source and access register

Create a table with these columns:

- Source or input
- Source type
- Access mode: supplied content, browsed, URL not inspected, or unavailable
- Relevant observation
- Brief sections supported
- Citation or evidence reference
- Reliability limitation

Do not report observations for uninspected URLs.

### 3. Search intent determination

Report the proposed primary intent, secondary intent, likely query journey, immediate information need, pre-conversion questions, expected page format, and mismatch risks. For each conclusion, identify its evidence and confidence as High, Medium, or Low.

State whether a live SERP recheck was actually performed, is recommended, or is unavailable. If performed, record the query, relevant locale or device assumptions, access date, observed result patterns, and limitations. Do not equate a recommendation to recheck the SERP with a completed recheck.

### 4. Audience, objection, and conversion map

Create a table with these columns:

- Audience need or job
- Pain point
- Desired outcome
- Awareness-stage implication
- Objection or decision barrier
- Trust requirement
- Relevant offer value
- Proof required
- Message angle
- CTA implication
- Evidence status

### 5. Competitor and differentiation analysis

For each competitor whose content was supplied or actually accessed, provide:

- Page and access status
- Search-intent angle
- Offer framing
- Page-format pattern
- Proof and trust signals
- Objections addressed
- CTA approach
- Useful gap or differentiation opportunity
- Unsupported inference or limitation
- Elements not to copy

If no competitor content was inspectable, state that the analysis is unavailable and provide a review protocol rather than fabricated findings.

### 6. Evidence-backed conversion angle matrix

Create a matrix with these columns:

- Proposed conversion angle
- Audience need addressed
- Offer value or differentiator
- Supporting proof and source
- Objection handled
- Recommended page placement
- CTA connection
- Evidence strength: Strong, Limited, Missing, or Conflicting
- Claim or compliance risk
- Disposition: Use, Qualify, Collect proof, Test as hypothesis, or Exclude

Exclude or qualify angles whose claims exceed the available evidence.

### 7. Page architecture and section specifications

Recommend an ordered page structure appropriate to the supplied page type. Do not force irrelevant sections into the page. Cover the hero, intent-satisfying answer, problem context, offer or solution, benefits or capabilities, proof, comparison or objection handling, process or how it works, FAQ, and CTA progression when relevant.

For every recommended section, specify:

- Section purpose and user question answered
- Suggested heading direction
- Key message and must-include points
- Evidence or proof required
- Relevant keyword or topic usage
- Objection addressed
- CTA role
- Internal-link opportunity
- Claim or compliance caution
- Dependencies or owner

Explain the conversion sequence and any trade-off between immediate intent satisfaction, persuasion depth, page length, and CTA timing.

### 8. SEO and discoverability specifications

Provide:

- Suggested H1 and its intent rationale
- Proposed meta title with character count
- Proposed meta description with character count
- Recommended URL slug
- Natural primary-keyword placements
- Secondary queries and entities, labeled as hypotheses unless supported by supplied or observed evidence
- Topic coverage and FAQ opportunities tied to user questions
- Cannibalization or page-overlap questions to investigate
- External citation requirements
- Structured-data opportunities and eligibility conditions

Clarify that metadata display and rankings cannot be guaranteed. Recommend only structured data that matches visible page content and current search-engine requirements; mark final schema validation as pending implementation review.

### 9. Internal-link plan

Create a table with these columns:

- Source section on the proposed page
- Destination page or supplied URL
- Suggested descriptive anchor direction
- User value and topical relationship
- Funnel role
- Required or optional
- Access and relevance status
- Verification owner

Do not assert that a destination exists, resolves successfully, is indexable, or is contextually accurate unless corresponding evidence is available. Flag missing destinations, redirect uncertainty, conflicting anchors, and links requiring CMS or crawl validation.

### 10. Claim, proof, and trust register

Create a table with these columns:

- Proposed claim or message
- Claim type
- Supporting source
- Exact evidence available
- Evidence status
- Qualification needed
- Trust asset or citation needed
- Compliance sensitivity
- Decision owner
- Allowed disposition: Include, Rewrite, Hold, or Remove

Identify missing case studies, testimonials, product documentation, certifications, methodology explanations, screenshots, or third-party sources without fabricating them. Treat testimonial permission, logo rights, recency, and citation accuracy as items requiring human confirmation.

### 11. Writer and production handoff

Provide the page goal, target reader, recommended voice and tone, central message, section sequence, must-include details, prohibited or unsupported claims, CTA wording directions, required internal links, questions the page must answer, design or asset dependencies, and review owners.

Label headings, copy lines, metadata, anchors, and CTA wording as proposed. Distinguish writer-ready instructions from unresolved strategy, proof, legal, design, CMS, analytics, or SEO dependencies.

### 12. Verification and acceptance record

Create a table with these columns:

- Acceptance check
- Expected condition
- Actual observation in this generated brief
- Evidence location
- Status: Pass, Partial, Fail, or Not verifiable
- Required correction or owner

Run these concrete checks:

1. Every blocking prerequisite is supplied or the brief is marked Partial or Blocked.
2. The primary intent conclusion cites supplied or actually observed evidence and records uncertainty.
3. Every conversion angle maps to an audience need, offer value, objection or decision criterion, CTA role, and evidence status.
4. Every factual or performance claim appears in the claim register and unsupported claims are held, qualified, or removed.
5. No competitor finding is attributed to a page that was not inspected.
6. The H1, metadata, section sequence, and topic coverage support the same primary intent and page goal.
7. Primary-keyword guidance is natural and does not prescribe repetitive exact-match use.
8. Each proposed internal link has a destination, user purpose, placement, and verification status.
9. Structured-data recommendations state eligibility conditions and do not imply implementation or validation.
10. CTA recommendations match the conversion action and buyer awareness stage.
11. Brand, compliance, privacy, and regulated-claim review needs have named owners or remain unresolved.
12. The handoff does not claim writing, implementation, testing, measurement, approval, publication, or ranking outcomes that did not occur.

Finish with an unresolved-items register containing the issue, effect on the page, evidence or decision needed, owner, blocking status, and next review gate. State precisely what the brief is ready for and what remains unverified.