Generate SEO-optimized landing pages with AEO blocks and CTAs

This skill writes a publishable landing-page draft for a product, service, or offer, structured to help the visitor understand the offer, trust it, and take a next step. It optimizes for human readers first, then structures the page so search engines and answer engines can parse it. The skill accepts a structured JSON input (product_name, business_type, target_audience, primary_keyword, secondary_keywords, usp, pain_points, features, benefits, social_proof, cta_primary, cta_secondary, offer, keyword_data, competitor, tone) and returns Markdown following a required 13-part flow: SEO Metadata, Hero and direct-answer block, Problem, Solution, Features and Benefits, Social Proof, Mid-page CTA, How It Works, Comparison or Alternatives, FAQ, Trust and Risk Reversal, Final CTA, and Internal-Link Suggestions.

It applies a set of decision rules while drafting: it follows the visitor's search intent rather than forcing a sales structure onto an informational request, picks one emotional anchor from the pain points and one central outcome from the benefits, maps every included feature to a concrete user benefit (omitting features with no clear outcome), and keeps the product itself out of the opening Problem section so the reader's situation is established before the pitch. The primary keyword is placed naturally in the H1, the opening copy, one H2, and at least one FAQ answer when supplied, without hitting arbitrary keyword-density targets.

Use it when creating or improving a conversion-focused product, service, offer, or homepage while preserving a clear search- and answer-engine structure. It is not meant to force a sales layout onto content meant to inform rather than convert, and it will not validate legal claims, product capabilities, accessibility, performance, or actual conversion results - those require project-specific review outside the skill.

Input is the JSON object of product/audience/keyword/proof fields listed above; any field left out is either inferred when obvious or listed as a missing assumption before the draft. The skill never invents customers, reviews, logos, performance claims, prices, guarantees, awards, security claims, or compliance certifications - where proof is missing it inserts a placeholder such as [verified customer quote], and a comparison with no reliable competitor facts is drafted against a generic alternative such as "doing this manually," explicitly labeled a positioning draft.

Output is Markdown following the exact section order above: an H1 (6-10 words), a meta title (50-60 characters where practical) and URL slug, a hero with a standalone 25-40 word sentence stating what the product is, who it's for, and the primary outcome, a features/outcomes table, an FAQ block with standalone answers normally under 50 words, and internal-link suggestions using descriptive anchors rather than "click here." A closing "Assumptions and verification notes" section is added only when placeholders or unsupported claims remain.

The skill can receive optional context from seo-aeo-keyword-research and seo-aeo-content-cluster, and hands off the completed page to seo-aeo-meta-description-generator, seo-aeo-content-quality-auditor, seo-aeo-internal-linking, and seo-aeo-schema-generator when those are available or requested.

Marketers, growth and content teams, and founders drafting a new landing page or reworking an existing one who need a structured, evidence-disciplined first draft rather than final, legally-reviewed copy.