audit-page

Audit Page

Diagnose the current state of a page, section by section, and tell the user which sections to revamp first and why. Apply a proven CRO framework as the lens, but organize the audit by SECTION so the output routes straight into the fix.

This is the Audit altitude of Web Anatomy: a whole-page diagnosis that runs standalone, with no benchmark data required. It feeds the grounded rework in write-page.

You do NOT write copy, headlines, or rewrites here, and you do NOT need benchmark data. Output is problem framing and prioritization: where conversion leaks and what to fix first. This is the on-ramp. The grounded next step is where the real edge is, so always end by handing off to it. There are two grounded paths and they answer different questions, so Step 6 asks the user which one they want.

Output Behavior

When file access is available, always write the orchestration handoff:

• .webanatomy/audit-page/{page-or-section}-{YYYY-MM-DD}/scorecard.json (your per-item judgments)
• .webanatomy/audit-page/{page-or-section}-{YYYY-MM-DD}/score.json (written by the scorer)
• .webanatomy/audit-page/{page-or-section}-{YYYY-MM-DD}/audit.json
• .webanatomy/audit-page/{page-or-section}-{YYYY-MM-DD}/report.md

audit.json is the machine handoff that write-page reads so it does not re-diagnose. The score block is copied verbatim from score.json (Step 3); do not hand-edit those numbers. Use this exact shape:

{
  "schema": "webanatomy.audit-page.v2",
  "target": "<url or page name>",
  "industry": "<resolved or inferred industry>",
  "locale": "en|fr",
  "score": {
    "overall": 0,
    "band": [0, 0],
    "coverage": 1,
    "evidenceBacked": 1,
    "evaluated": 49,
    "naCount": 0,
    "categoryScores": [
      { "category": "Hero", "score": 0, "passCount": 0, "failCount": 0, "naCount": 0, "failedItemIds": [] }
    ]
  },
  "currentSnapshot": [{ "label": "Headline", "text": "..." }],
  "strengths": [
    { "section": "trust", "what": "Recognizable customer logos sit above the fold", "why": "fast credibility for a cold visitor; keep it" }
  ],
  "recommendations": [
    {
      "section": "hero",
      "severity": "HIGH",
      "kind": "copy",
      "opportunity": "Lead the H1 with the outcome, not the product name",
      "why": "what it unlocks, tied to the real page",
      "failedItemIds": ["hero.outcome_focus"]
    }
  ],
  "pageLevel": [
    { "section": "page", "opportunity": "Fix the narrative order (pain then outcome then product)", "why": "..." }
  ],
  "sectorSpecific": [
    { "section": "contact", "opportunity": "Surface the capital-loss risk notice near the form", "why": "regulated finance; judgment, not the rubric" }
  ],
  "startHere": "hero",
  "notes": "industry inferred; capture method + confidence"
}