> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amadora.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Landing Page Specifications

Landing Page Drafts transform any row in **Site Structure** into a complete, production-ready content spec in Markdown—including section-by-section page copy, FAQs, SEO metadata, JSON-LD schema, image briefs, and internal linking strategies.

<Frame>
  <img src="https://mintcdn.com/amadoraai/VEZKc6seBzRoZL5M/images/site-structure.png?fit=max&auto=format&n=VEZKc6seBzRoZL5M&q=85&s=b54bfdc58f1db3b50576e6853d1b8b1e" alt="Site Structure" width="2936" height="1434" data-path="images/site-structure.png" />
</Frame>

## Output Overview

Generated drafts provide a structured, well-researched foundation designed to accelerate page creation while maintaining strict factual integrity:

<Frame>
  <img src="https://mintcdn.com/amadoraai/I0tPWIJGmZ0cF4Bl/images/lading-page-draft-overview.png?fit=max&auto=format&n=I0tPWIJGmZ0cF4Bl&q=85&s=88d514aa1a047d7f366b484d1105e7e9" alt="Lading Page Draft Overview" width="2452" height="1434" data-path="images/lading-page-draft-overview.png" />
</Frame>

* **Markdown Output:** Delivered as a brief for copywriters or CMS imports, not raw HTML.
* **Factual Guardrails:** The agent never fabricates metrics, case studies, or customer quotes. Missing proof points are flagged inline as `[PROOF NEEDED: exact detail required]`.
* **Conversion & GEO Focus:** Built with clear extraction zones for AI search engines (definition blocks, FAQs, comparison tables) along with primary conversion goals and repeated CTA placements.

## Archetype Word Ceilings

The system selects one of nine archetypes based on the page type. Default ceilings automatically scale down if your measured **Page Style** profile mandates tighter content budgets:

| Archetype                         | Word Ceiling            |
| --------------------------------- | ----------------------- |
| **Hub / Pillar Page**             | 2,000 words             |
| **Comparison / Alternative Page** | 1,800 words             |
| **SaaS Product / Feature Page**   | 1,300 words             |
| **Service Page**                  | 1,100 words             |
| Homepage                          | 1,100 words             |
| **Local Service Page**            | 900 words               |
| **About Page**                    | 800 words               |
| **Pricing Page**                  | 700 words (plus tables) |
| **Lead-Gen / Campaign Page**      | 500 words               |

## Draft Document Structure

Every generated Markdown file contains two distinct sections:

### Part 1: Landing Page Copy

Complete section-by-section copy, headings, structured tables, CTA placements, and end-of-page FAQs, featuring inline `[PROOF NEEDED]` placeholders where specific company facts are required.

### Part 2: Publishing Pack

| Section                | Description                                                                              |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| **SEO Meta**           | Title tags (50–60 characters), meta descriptions (140–160 characters), and primary slug. |
| **Social Meta Tags**   | Open Graph metadata and 1200×630 image specifications.                                   |
| **JSON-LD Schema**     | Pre-formatted structured data tailored to the target page archetype.                     |
| **Image Briefs**       | Visual descriptions, page placements, and alt text under 125 characters.                 |
| **Internal Links**     | 3–5 contextual internal link recommendations with anchor text.                           |
| **AI Prompt Coverage** | Mapping of page sections against target tracked prompts.                                 |
| Handoff                | Open proof item checklists and remaining pre-publication tasks.                          |

## Execution Workflow

1. **Preview & Select:** Click **Draft** on any Site Structure row to preview the outline.
2. **Export Markdown:** Download the draft file (also collected centrally in **Deliverables**).
3. **Fill Proof Markers:** Replace every `[PROOF NEEDED]` marker with verified company statistics, client names, or dates.
4. **Verify Prompt Coverage:** Review the **AI Prompt Coverage** section in the Publishing Pack to ensure all targeted AI search queries are addressed.
5. **Handoff:** Send the Markdown file and Publishing Pack to copywriters for final polish or developers for implementation.

## FAQs

<AccordionGroup>
  <Accordion title="Can I publish generated drafts immediately?">
    No. Drafts are Markdown specs containing `[PROOF NEEDED]` placeholders that require human verification before going live.
  </Accordion>

  <Accordion title="Why is my draft shorter than the archetype ceiling?">
    Your **Page Style** profile takes precedence over default archetype ceilings. If your site historically uses concise page formats, generated drafts adapt to match.
  </Accordion>

  <Accordion title="Do I need all four Brand Detail documents set up first?">
    Yes. Without **Company Details**, **Evidence Database**, **Writing Style & Voice**, and **Page Style**, drafts lack factual specifics and return generic copy.
  </Accordion>

  <Accordion title="How do blog post drafts differ from landing page drafts?">
    Landing page drafts originate from **Site Structure** rows (`platform_` filename prefix). Blog post drafts and briefs are generated within **Content Creation** (`blog_` filename prefix).
  </Accordion>
</AccordionGroup>