Webflow · SEO blog
Add a blog to Webflow without living in Webflow CMS
Add a blog to Webflow by putting SEO posts on Blogizi and pointing blog.yourapp.com at your project — keep marketing pages in Webflow, publish markdown from Claude when you confirm.
Webflow CMS fits designer-edited collections. Founders who want agent-written product posts usually want a separate publish path.
From $9/mo · 7-day free trial · drafts by default
Pricing
$9/mo· 10k pageviews · 7-day free trial
Webflow CMS vs Blogizi
| Topic | Typical path | With Blogizi |
|---|---|---|
| Editors | Webflow Designer / CMS UI | Markdown + agents (CLI / MCP) |
| Domain | Same Webflow hosting | blog subdomain CNAME to Blogizi |
| SEO stack | Collections + templates you maintain | Hosted blog with sitemaps + OG |
Setup
Keep Webflow on the apex; blog on a subdomain
- Leave Webflow DNS for yourapp.com / www unchanged.
- CNAME
blog→YOUR-SLUG.app.blogizi.comat your DNS provider. - Add and verify
blog.yourapp.comin Blogizi → Settings → DNS. - Link “Blog” in the Webflow nav to
https://blog.yourapp.com.
Path mode
yourapp.com/blog on Webflow
Native Webflow hosting does not give you Vercel-style reverse proxies. For /blog on the same host, put Cloudflare (or similar) in front and use a Worker from Blogizi’s path-mode snippets — or stick with the subdomain.
SEO
Webflow SEO + Blogizi posts
Optimize Webflow pages in Designer as usual. Long-form product content, sitemaps, and OG images for posts live on Blogizi so you are not fighting CMS collection limits for agent drafts.
FAQ
Can I replace Webflow CMS entirely?
For the blog, yes. Keep Webflow for marketing/landing pages if that is where your design system lives.
Will this hurt Webflow SEO?
No — you add a subdomain (or proxied path). Apex Webflow pages stay as they are.
Start publishing with your agent
Create a project, connect Claude or another agent, and ship SEO posts to your domain — $9/mo with a 7-day trial.