Will this hurt Webflow SEO?

No — you add a subdomain (or proxied path). Apex Webflow pages stay as they are.

Webflow + Blogizi

Add a blog to Webflow without living in Webflow CMS

Keep marketing pages in Webflow, blog on blog.yourapp.com
Publish markdown from Claude instead of the Webflow CMS
Sitemaps, OG images and canonicals handled, from $9/mo

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 vs Blogizi

Webflow CMS fits designer-edited collections. Founders who want agent-written product posts usually want a separate publish path.

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.com at your DNS provider.
Add and verify blog.yourapp.com in Blogizi → Settings → DNS.
Link “Blog” in the Webflow nav to https://blog.yourapp.com.

DNS records · yourapp.comdns1 record to add

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

Add only the CNAME. Leave the records Webflow 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

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.

Publish from Claude instead of the Webflow CMS

Agents draft markdown through the CLI or hosted MCP. Posts land on blog.yourapp.com as drafts; you publish when they're right.

See agent setup »

Terminal

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