# SEO-AEO landing page writer Human Guide

## What This Is For
Writes complete, structured landing pages optimized for SEO ranking, AEO citation, and visitor conversion. It gives the agent a clearer input/output frame for search and SEO workflows: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the SEO-AEO landing page writer agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for SEO-AEO landing page writer.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the SEO-AEO landing page writer guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Use when building a landing page for a new product or service
- Use when an existing landing page needs a full SEO and AEO rewrite
- Use when you need a page that can be cited by AI engines like Perplexity or ChatGPT
- Use when you want conversion copy that leads with pain before pitching the product
- Hero — H1 + AEO sentence + CTA
- Problem — audience pain, no product mention yet
- Solution — introduce product as the answer
- Features as Benefits — table format
- Social Proof — testimonials, logos, stats
- How It Works — numbered steps
- Comparison — table with honest competitor comparison
- FAQ — minimum 6 entries, each under 50 words

## Decision Points And Nuance
The original skill emphasizes: Overview, When to Use This Skill, How It Works, Step 1: Map Inputs, Step 2: Write AEO Extraction Sentence, Step 3: Follow the Narrative Arc, Step 4: Run SEO and AEO Checklists, Examples, Example 1: Hero Section Output, Example 2: FAQ Section Output.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- users. A 14-day free trial is available — no credit card required.
- ✅ **Do:** Write FAQ answers as standalone — each must make sense without context
- ❌ **Don't:** Use "revolutionary", "game-changing", or "best-in-class" anywhere
- ❌ **Don't:** Use "Submit" or "Click Here" as CTA button text
- ❌ **Don't:** Write paragraphs longer than 4 lines
- **Solution:** Every FAQ answer must be under 50 words and self-contained.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

## Copy-And-Paste Prompt
```text
Use the SEO-AEO landing page writer human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the sickn33/agentic-awesome-skills skill entry for `seo-aeo-landing-page-writer`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# SEO-AEO Landing Page Writer

## Overview

Generates a full, publish-ready landing page following a defined section order with SEO heading structure, AEO extraction blocks, FAQ section, comparison table, social proof, and conversion-focused CTAs. Every section serves a specific purpose in a narrative arc that moves the visitor from awareness to action.

Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).

## When to Use This Skill

- Use when building a landing page for a new product or service
- Use when an existing landing page needs a full SEO and AEO rewrite
- Use when you need a page that can be cited by AI engines like Perplexity or ChatGPT
- Use when you want conversion copy that leads with pain before pitching the product

## How It Works

### Step 1: Map Inputs
Extract product name, audience, primary keyword, pain points, features, benefits, USPs, social proof, and CTAs. Map every feature to a user outcome before writing any copy.

### Step 2: Write AEO Extraction Sentence
Write one 25–40 word sentence that answers "What is [product]?" — standalone, no jargon, placed in a blockquote immediately after the H1. This is the sentence AI engines extract.

### Step 3: Follow the Narrative Arc
Write sections in this exact order:
1. Hero — H1 + AEO sentence + CTA
2. Problem — audience pain, no product mention yet
3. Solution — introduce product as the answer
4. Features as Benefits — table format
5. Social Proof — testimonials, logos, stats
6. Mid-page CTA
7. How It Works — numbered steps
8. Comparison — table with honest competitor comparison
9. FAQ — minimum 6 entries, each under 50 words
10. Trust Signals
11. Final CTA

### Step 4: Run SEO and AEO Checklists
Verify keyword placement, heading hierarchy, FAQ count, AEO block presence, and meta description placeholder before outputting.

## Examples

### Example 1: Hero Section Output
Ship Faster With Your Remote Team

Syncro is a remote-first project management platform that helps
distributed engineering teams track work, communicate
asynchronously, and ship without the chaos of email and
scattered spreadsheets.

[Start Free Trial]  [See How It Works]
"4,000+ remote teams" · "40% fewer status meetings" · "4.8/5 on G2"

### Example 2: FAQ Section Output
Q: What is Syncro?
A: Syncro is a remote-first project management platform for
distributed engineering teams. It centralises task tracking,
async communication, and sprint planning in one tool.
Q: How much does Syncro cost?
A: Syncro offers a flat-rate plan at $49/month for unlimited
users. A 14-day free trial is available — no credit card required.

## Best Practices

- ✅ **Do:** Write the problem section before mentioning the product — empathy first
- ✅ **Do:** Place the AEO extraction sentence in a blockquote immediately after H1
- ✅ **Do:** Write FAQ answers as standalone — each must make sense without context
- ✅ **Do:** Include at least one honest point in the comparison table where the alternative wins
- ❌ **Don't:** Use "revolutionary", "game-changing", or "best-in-class" anywhere
- ❌ **Don't:** Use "Submit" or "Click Here" as CTA button text
- ❌ **Don't:** Write paragraphs longer than 4 lines

## Common Pitfalls

- **Problem:** Product mentioned in the pain section
  **Solution:** The pain section exists to build empathy. Save the product introduction for the solution section.

- **Problem:** FAQ answers are too long to be extracted by AI engines
  **Solution:** Every FAQ answer must be under 50 words and self-contained.