Is this only for Next.js from v0?

v0 + Blogizi

Add a blog to your v0 app

Ship the v0 app, host the blog on Blogizi
yourapp.com/blog on Vercel, or a blog subdomain
Your agent drafts posts; you approve before they go live

Add a blog to a v0-generated app with Blogizi — deploy on Vercel with /blog rewrites or CNAME blog.yourapp.com, and let agents publish markdown drafts you approve.

CMS in the v0 repo vs Blogizi

v0 output is usually Next.js on Vercel. Blogizi fits that stack without adding a headless CMS.

Topic	Typical path	With Blogizi
Repo scope	CMS schemas + blog UI in-app	App stays product-only
URL	You implement /blog	Vercel rewrites or CNAME
Publish	Editors / DIY API	blogizi draft / publish

Setup

Two options after you deploy v0 to Vercel

Path mode: enable in Blogizi DNS settings, add the vercel.json rewrites from Blog for Vercel.
Subdomain: CNAME blog.yourapp.com → Blogizi platform host.

DNS records · yourapp.comdns1 record to add

Type	Name	Target	Copy
CNAME	blog	your-slug.app.blogizi.com
A	@	Vercel · unchanged

Add only the CNAME. Leave the records Vercel uses for your app alone.

Keep generating UI in v0; publish posts elsewhere

v0 is for UI. Blogizi is for the SEO content loop — Claude Code drafts from the repo, Blogizi hosts.

See agent setup »

Terminal

$ blogizi auth <key>$ blogizi use your-slug$ blogizi draft ./posts/v0-launch-notes.md# review in the dashboard, then:$ blogizi publish ./posts/v0-launch-notes.md