RULE: For content-heavy SEO/AI-critical clients (~$10k+ budget), default proposal is headless WordPress + Astro on Cloudflare Pages

Rule: For Candid Creative clients in the content-heavy, SEO-critical, AI-citation-sensitive tier (typically $10k+ budget — Use Case C in Reference: alternative-stack recommendations by use case and budget (Candid 6-tier framework)), the default proposal is headless WordPress (WPGraphQL) + Astro on Cloudflare Pages, not WordPress + page builder, not Next.js SSR.

Why:

• Performance: Astro ships ~90% less JS than Next.js for static content (Astro vs Next.js (eastondev benchmark, Dec 2025): ~40% faster, ~90% less JS for static content)
• Cost: ~$0/month on Cloudflare Pages vs $20-200/month for Next.js SSR (Astro on Cloudflare Pages: ~$0/month vs Next.js SSR ~$20-200/month (Bobes 2026 benchmark))
• SMB migration: $1.5k-$5k from WordPress to Astro; ongoing $700-2,100/yr → <$200/yr (Web Aloha agency)
• AI extractability: pre-rendered HTML, server-render-first, no JS hydration needed for content reads — see AI crawlers (GPTBot, ClaudeBot, PerplexityBot) generally do not execute JavaScript — client-side React/Vue without SSR is invisible
• Practitioner satisfaction: State of JS 2025 — Astro 39-point satisfaction lead over Next.js (Astro on Cloudflare Pages: ~$0/month vs Next.js SSR ~$20-200/month (Bobes 2026 benchmark))

How to apply:

• For Use Case C clients (content-heavy, SEO-critical, AI-sensitive): lead the proposal with Astro headless. The page-builder + WordPress comparison is presented as "the old way."
• Use Case D (web app, authenticated flows): Next.js is still right — Astro is for content sites.
• The Stage 4 pilot client in Candid Creative page-builder transition roadmap: 4 stages over 12 months is the first Astro production reference; document the build hours and case-study results before quoting the same approach to Client #2.
• WordPress remains the authoring layer (clients edit in wp-admin); Astro renders the public site.