Do I need a headless CMS?

Not for a product SEO blog. Use a CMS when you need multi-model content and editorial workflows. Use Blogizi when agents and markdown are enough.

Vercel + Blogizi

Add a blog to your Vercel site

yourapp.com/blog with one Vercel rewrite, or blog.yourapp.com
No Sanity or Payload to run for a product blog
Your agent drafts markdown; you publish when it's right

See agent setup

Add a blog to your Vercel site with Blogizi: rewrite yourapp.com/blog to Blogizi (path mode) or CNAME blog.yourapp.com — no Sanity or Payload required for a product blog.

Headless CMS on Vercel vs Blogizi

For founders who already ship on Vercel and need SEO posts on the same brand without another CMS project in the monorepo.

Topic	Typical path	With Blogizi
What you deploy	CMS + preview + webhooks on Vercel	One Blogizi project + API key
URL shape	You build /blog routes	Rewrites or CNAME — Blogizi hosts pages
Publishing	CMS editors	Agents / markdown / CLI

Path mode

yourapp.com/blog with Vercel rewrites

In Blogizi, enable path mode (Settings → DNS), set root domain and base path blog, then add rewrites on the Vercel project that hosts the marketing site:

vercel.jsonjson

1{2  "rewrites": [3    {4      "source": "/blog/:path*",5      "destination": "https://YOUR-SLUG.app.blogizi.com/:path*"6    },7    {8      "source": "/api/sites/:path*",9      "destination": "https://YOUR-SLUG.app.blogizi.com/api/sites/:path*"10    }11  ]12}

Highlighted lines send yourapp.com/blog to your Blogizi project.

If the root site is also Next.js, copy the /_next/* middleware snippet from Dashboard → Settings → DNS so blog assets resolve without breaking the main app.

Subdomain

Or CNAME blog.yourapp.com

Add blog.yourapp.com in Blogizi DNS settings and CNAME it to YOUR-SLUG.app.blogizi.com. No rewrites required — simplest when path mode is not a requirement.

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.

Publish without touching the Next.js app

Keep product code on Vercel. Agents draft markdown via CLI or hosted MCP; you publish when ready. Pair with Add a blog to Next.js without a CMS for the product-blog framing.

See agent setup »

Terminal

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