Vibe currently renders as a client-side React SPA. For interactive apps and brochure sites this is fine — but for SEO-critical content pages (blogs, resource libraries), the initial HTML is an empty root div. Search crawlers deprioritize JS-rendered content, and AI crawlers largely don't execute JS at all.

The request is an additional SSG build mode — not a replacement of current behaviour — where:

Content is fetched from an external CMS API (e.g. headless WordPress REST/WPGraphQL) at build time

Each route is emitted as a fully prerendered static HTML page

A CMS webhook optionally triggers a rebuild on publish

The data connection already works today (Vibe can query public CMS endpoints via fetch). The gap is rendering — content needs to be in the initial HTML response, not assembled in the browser.

Who this unblocks:

Partners building high-velocity content sites for clients where SEO and AI crawler visibility are the primary business case. Blackfeather Digital (AI Certified Partner) raised this directly — it is the single blocker preventing them from standardizing all web builds on Vibe.

Full details:

Transcript: https://docs.google.com/document/d/1jNNQcSivs7jcDy5L6_x9gm6UnHUXAQkc-MvtUkZ4tPQ/edit?tab=t.0

Feature request: https://docs.google.com/document/d/1P7FCO2tQystSuM1vYKrGJ2mFhQr2lq0JL6REsH5wh2w/edit?tab=t.0#heading=h.1pe48taedqc9