Landing Page CRO Analysis

Standalone CRO teardown for a single landing page. Produces a section-by-section score, prioritized fixes, and A/B test hypotheses. Unlike market-audit, this skill does not fan out - it runs end-to-end in the parent and writes one report.

When to Use

• User supplies a landing-page URL and asks for conversion optimization, CRO review, or signup-rate help
• Slash: /market-landing <url> or /market landing <url> (via market orchestrator)
• After /market-audit if the funnel dimension flagged the landing page as the bottleneck

When NOT to Use

• Whole-site audit across many pages - use market-audit
• Copy-only rewrite without conversion-mechanic analysis - use market-copy
• Full funnel (ad → landing → email → checkout) - use market-funnel

Authoring a fresh sales/squeeze/OTO/landing page from a brief - use /convert <page-type> (business-conversion pack). market-landing audits existing pages; convert-pack authors fresh ones.

Inputs

• <url> - required. Bare domains are normalized to https://<url>.
• out_path - optional. Default: build_report_path("business-marketing", f"landing {url}").

Workflow

Step 1 - Fetch the page

Prefer web_extract for the readable text + visible CTAs. If the analysis needs raw HTML for above-the-fold structure, form field counts, button colors, or <meta> tags, use terminal + curl, then parse with analyze_page.py (shared with market-audit):

curl -L --max-filesize 200000 -A "Wayland-CRO-Bot/1.0" \
     -o .wayland/tmp/landing-<slug>.html "<url>"

import sys
sys.path.insert(0, "business-marketing/market-audit/scripts")
from analyze_page import analyze
parsed = analyze(url)  # {seo, content, conversion, trust, tracking, technical, scores, ...}

Children-blocked tools do not apply here - this skill runs in the parent agent loop only.

Step 2 - Identify the page type

Page type sets benchmark expectations and scoring weights.