{"slug":"landing-page-builder","title":"landing-page-builder","tags":["site-building","frontend","landing","page","builder"],"agent_summary":"Purpose Research, write, design, code, and validate a production-ready landing page from a source URL or text brief","trigger_phrases":["landing-page-builder","landing guide","page guide","builder guide","landing page from url","build landing page","comprehensive landing page","website from page"],"runnable":false,"markdown":"**Trigger:** Use when \"landing page from URL\", \"build landing page\", \"comprehensive landing page\", \"website from page\", \"Manus landing page\".\n\n### Purpose\n\nResearch, write, design, code, and validate a production-ready landing page from a source URL or text brief. The output includes a fully coded page with SEO/AEO optimization, E-E-A-T signals, schema markup, crawler directives, and a complete evidence/research pack.\n\n### Workflow\n\n**Phase 1: Auto-Discovery and Research**\n\n1A. Source Analysis — Extract from text (preferred) or URL (fallback): brand name, services/products, positioning, proof points, contact details, primary keyword, 3-5 secondary keywords and LSI terms, dominant search intent, voice and tone, geo signals.\n\n1B. Location Verification (Critical) — Find footer address on the page. Find any embedded map. Cross-reference: footer address MUST match map location exactly. Check Contact/About pages and any existing JSON-LD for confirmation. If mismatch or missing: set geo_verified=false, switch to non-local approach.\n\n1C. E-E-A-T Inventory — Document author/org credentials, publish/update dates, citations, contact page quality, privacy policy presence, about page depth, trust signals (certifications, awards, memberships).\n\n1D. Competitor Intelligence — Query primary keyword + city/state if geo_verified. Collect 5-10 direct page-1 competitors (exclude directories, marketplaces, news, Wikipedia). For each competitor, document: URL, SERP rank, target keywords, word count, CTA count, schema types, trust signals, UX patterns. Compute target word count: min(max(round(avg_top5_word_count * 1.15), 1500), 2500)\n\n1E. People Also Ask Research — Expand PAA for the primary keyword. Select 8-12 intent-aligned questions. Draft 100-150 word answers with natural keyword use. FAQs are MANDATORY on every generated page.\n\n**Phase 2: Content Strategy**\n\nInformation Architecture (sections in order):\n1. Hero (50-100 words): H1 with primary keyword, subheadline value prop, single primary CTA, trust badges\n2. Value Proposition (200-300 words): 3-4 key benefits with icons, outcome-focused\n3. Services/Products (400-600 words): Core offerings with details, optional pricing, secondary CTA\n4. Why Us / Differentiators (300-400 words): Address competitor gaps, proof points\n5. Social Proof (200-300 words): Testimonials, logos, stats, reviews\n6. Education/Depth (500-800 words): In-depth content addressing objections and user questions\n7. FAQ (300-500 words): 8-12 PAA items with comprehensive answers\n8. Final CTA (100-150 words): Strong close with contact info, hours, location\n9. Footer: Full contact, legal links, nav, social\n\n**Phase 3: Content Creation**\n\nWrite all sections: Readability Flesch 60-70, grade 8-10, short paragraphs (2-4 sentences), subheadings every 200-300 words. Bold key concepts, use bullet points for lists. No plagiarism, no repetition, human-like style. E-E-A-T signals embedded throughout.\n\n**Phase 4: Design and Code**\n\nResponsive Layout (Mobile-First): Design for 375px first, scale to tablet (768px) and desktop (1920px+). Touch-friendly elements (minimum 44x44px tap targets). Base font minimum 16px on mobile. Color contrast minimum 4.5:1.\n\nCTA Strategy: 3-6 CTAs total. Primary above the fold. Consistent style. CTA copy formula: [Action Verb] + [Value/Benefit] + [Urgency optional]. Click-to-call, mailto, compact contact form with a11y validation.\n\n**Phase 5: Technical SEO**\n\nMeta Tags: robots index/follow, title (50-59 chars with primary keyword + location + brand), meta description (150-155 chars), canonical tag, Open Graph tags, Twitter Card tags.\n\nSchema Markup (JSON-LD): WebPage (always), FAQPage (always), Service (for core offerings), LocalBusiness (only if geo_verified=true), BreadcrumbList (if nav supports it).\n\n**Phase 6: Crawler Directives**\n\nrobots.txt: Allow /, Disallow /admin/ and /cgi-bin/, Sitemap URL, LLM policy reference.\nllms.txt: Crawl-access allow, Source-of-truth URL, Contact, Data-use policy, Last-updated date.\n\n**Phase 7: Geo-Targeting** (if geo_verified=true)\n\nUse local currency and units. Regional spelling and vocabulary. Reference local landmarks and neighborhoods. Include area-specific keywords: \"[service] in [city]\". Display local phone, hours, timezone. Embed map with location pin. List service areas/cities.\n\n**Phase 8: Quality Assurance**\n\nContent: Word count within target, tone consistent, no placeholders, facts verified.\nSEO: Title 50-59 chars, description 150-155 chars, H1 present, H2/H3 logical, keyword density ~1-2%, internal links present, canonical present.\nSchema: All types validated, matches on-page content.\nTechnical: Robots tags, canonical, OG/Twitter, favicon, HTTPS-ready, no console errors.\nConversion: Primary CTA above fold, 3-6 CTAs total, phone clickable, email functional.\nPerformance targets: FCP <1.8s, LCP <2.5s, INP <200ms, CLS <0.1, TTI <3.8s, TTFB <600ms. Lighthouse: Mobile >90, Desktop >95.\n\n---\n","html":"

Trigger: Use when \"landing page from URL\", \"build landing page\", \"comprehensive landing page\", \"website from page\", \"Manus landing page\".

\n

Purpose

\n

Research, write, design, code, and validate a production-ready landing page from a source URL or text brief. The output includes a fully coded page with SEO/AEO optimization, E-E-A-T signals, schema markup, crawler directives, and a complete evidence/research pack.

\n

Workflow

\n

Phase 1: Auto-Discovery and Research

\n

1A. Source Analysis — Extract from text (preferred) or URL (fallback): brand name, services/products, positioning, proof points, contact details, primary keyword, 3-5 secondary keywords and LSI terms, dominant search intent, voice and tone, geo signals.

\n

1B. Location Verification (Critical) — Find footer address on the page. Find any embedded map. Cross-reference: footer address MUST match map location exactly. Check Contact/About pages and any existing JSON-LD for confirmation. If mismatch or missing: set geo_verified=false, switch to non-local approach.

\n

1C. E-E-A-T Inventory — Document author/org credentials, publish/update dates, citations, contact page quality, privacy policy presence, about page depth, trust signals (certifications, awards, memberships).

\n

1D. Competitor Intelligence — Query primary keyword + city/state if geo_verified. Collect 5-10 direct page-1 competitors (exclude directories, marketplaces, news, Wikipedia). For each competitor, document: URL, SERP rank, target keywords, word count, CTA count, schema types, trust signals, UX patterns. Compute target word count: min(max(round(avg_top5_word_count * 1.15), 1500), 2500)

\n

1E. People Also Ask Research — Expand PAA for the primary keyword. Select 8-12 intent-aligned questions. Draft 100-150 word answers with natural keyword use. FAQs are MANDATORY on every generated page.

\n

Phase 2: Content Strategy

\n

Information Architecture (sections in order):

\n
    \n
  1. Hero (50-100 words): H1 with primary keyword, subheadline value prop, single primary CTA, trust badges
    2. \n
  2. Value Proposition (200-300 words): 3-4 key benefits with icons, outcome-focused
    3. \n
  3. Services/Products (400-600 words): Core offerings with details, optional pricing, secondary CTA
    4. \n
  4. Why Us / Differentiators (300-400 words): Address competitor gaps, proof points
    5. \n
  5. Social Proof (200-300 words): Testimonials, logos, stats, reviews
    6. \n
  6. Education/Depth (500-800 words): In-depth content addressing objections and user questions
    7. \n
  7. FAQ (300-500 words): 8-12 PAA items with comprehensive answers
    8. \n
  8. Final CTA (100-150 words): Strong close with contact info, hours, location
    9. \n
  9. Footer: Full contact, legal links, nav, social
    10. \n
\n

Phase 3: Content Creation

\n

Write all sections: Readability Flesch 60-70, grade 8-10, short paragraphs (2-4 sentences), subheadings every 200-300 words. Bold key concepts, use bullet points for lists. No plagiarism, no repetition, human-like style. E-E-A-T signals embedded throughout.

\n

Phase 4: Design and Code

\n

Responsive Layout (Mobile-First): Design for 375px first, scale to tablet (768px) and desktop (1920px+). Touch-friendly elements (minimum 44x44px tap targets). Base font minimum 16px on mobile. Color contrast minimum 4.5:1.

\n

CTA Strategy: 3-6 CTAs total. Primary above the fold. Consistent style. CTA copy formula: [Action Verb] + [Value/Benefit] + [Urgency optional]. Click-to-call, mailto, compact contact form with a11y validation.

\n

Phase 5: Technical SEO

\n

Meta Tags: robots index/follow, title (50-59 chars with primary keyword + location + brand), meta description (150-155 chars), canonical tag, Open Graph tags, Twitter Card tags.

\n

Schema Markup (JSON-LD): WebPage (always), FAQPage (always), Service (for core offerings), LocalBusiness (only if geo_verified=true), BreadcrumbList (if nav supports it).

\n

Phase 6: Crawler Directives

\n

robots.txt: Allow /, Disallow /admin/ and /cgi-bin/, Sitemap URL, LLM policy reference.\nllms.txt: Crawl-access allow, Source-of-truth URL, Contact, Data-use policy, Last-updated date.

\n

Phase 7: Geo-Targeting (if geo_verified=true)

\n

Use local currency and units. Regional spelling and vocabulary. Reference local landmarks and neighborhoods. Include area-specific keywords: \"[service] in [city]\". Display local phone, hours, timezone. Embed map with location pin. List service areas/cities.

\n

Phase 8: Quality Assurance

\n

Content: Word count within target, tone consistent, no placeholders, facts verified.\nSEO: Title 50-59 chars, description 150-155 chars, H1 present, H2/H3 logical, keyword density ~1-2%, internal links present, canonical present.\nSchema: All types validated, matches on-page content.\nTechnical: Robots tags, canonical, OG/Twitter, favicon, HTTPS-ready, no console errors.\nConversion: Primary CTA above fold, 3-6 CTAs total, phone clickable, email functional.\nPerformance targets: FCP <1.8s, LCP <2.5s, INP <200ms, CLS <0.1, TTI <3.8s, TTFB <600ms. Lighthouse: Mobile >90, Desktop >95.

\n
\n"}