Does this work with bolt.new exports?

Bolt + Blogizi

Add a blog to your Bolt app

Keep the AI-built product exactly as it is
Real blog routes on blog.yourapp.com, not an embed
Publish SEO posts from markdown when you confirm

Add a blog to your Bolt app with Blogizi on blog.yourapp.com — keep the AI-built product as-is and publish SEO posts from markdown when you confirm.

Build-your-own blog vs Blogizi

Same pattern as other AI builders: product on Bolt, crawlable content on a Blogizi subdomain.

Topic	Typical path	With Blogizi
Time to live	Wire CMS + routes in the Bolt app	CNAME + Blogizi project
Agents	Ad hoc paste	First-class CLI / MCP
SEO	DIY	Hosted sitemaps + OG

Setup

CNAME the blog subdomain

Create a Blogizi project.
CNAME blog → YOUR-SLUG.app.blogizi.com.
Verify the domain in Blogizi and publish a first draft.

DNS records · yourapp.comdns1 record to add

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

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

Settings → DNSSuccess

✓ blog.yourapp.com verified✓ SSL certificate issued✓ sitemap.xml and robots.txt live→ https://blog.yourapp.com

Path mode

If you export to Vercel

Bolt apps often deploy to Vercel or Netlify. Once you control rewrites, you can enable Blogizi path mode — see Blog for Vercel. On managed Bolt hosting alone, prefer the subdomain.

Publish posts from the same AI workflow

Keep building in Bolt. Your agent drafts posts through the CLI or hosted MCP, and nothing goes live until you publish.

See agent setup »

Terminal

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