Battlecard/compare SEO pages (vs Crio, Euron, Graphy, Maven)

Why / Context

Teardown STEAL (Euron Systems /compare): live, SEO-indexed comparison/battlecard pages across named competitors are "a proven SEO and bottom-of-funnel conversion tool once we have real, defensible advantages to cite." Teardown §6 already scripts the positioning language vs Crio.do and vs Euron Systems (lead-withs, concessions included — honesty is part of the play).

Schema already in place — NO migration required

• Pure marketing surface: no data model. (Optionally reuse Waitlist(source: 'compare-<slug>') for CTAs.)

Implementation plan

1. Comparison framework component: honest feature matrix (us/them columns with citations), "where they're genuinely strong" section (teardown mandates conceding Crio's free funnel + Euron's AI tooling), positioning copy blocks, CTA.
2. Pages (ISR, MDX-driven content in src/content/compare/): vs Crio.do, vs Euron Systems, vs Graphy, vs Teachable/Kajabi-class, vs Maven — copy sourced from teardown §6 battlecards + §4 matrix.
3. SEO: targeted metadata ("X alternative", "X vs Y"), FAQ schema (JSON-LD), internal links from pricing/catalog, sitemap inclusion.
4. Claims hygiene process: every factual competitor claim carries a source + last-verified date (front-matter), quarterly re-verification checklist (teardown warns pricing/features move) — stale claims auto-flag in CI (date lint).
5. Programmatic long-tail: "best platform for creators" pages fed by live catalog counts.
6. Conversion instrumentation: PostHog events per page → signup/purchase attribution (issue #12).
7. Legal pass: comparative-advertising review of claim wording.

Acceptance criteria

• Five comparison pages live, indexed, with honest concessions and sourced claims
• Every claim shows last-verified date; CI flags claims older than 90 days
• FAQ schema validates in Rich Results test
• CTA conversion tracked per page in PostHog
• Copy matches teardown §6 tone (no disparagement, concede real strengths)

Dependencies / sequencing

• Marketing site from MVP M13; issue #12 for attribution
• Ship AFTER we have the defensible advantages each page cites (post project-tiers + portfolio)

Start with the implementation plan and teardown §6, then inspect the MDX-driven content area at src/content/compare/ and the pricing/catalog entry points. Done means five indexed comparison pages with sourced, dated claims, FAQ schema validation, sitemap inclusion, CI age checks, and per-page PostHog attribution via issue #12.