Blogging inside a website builder, compared honestly

Ten posts in, every blogging tool inside a general website builder looks fine. You write in a box, you hit publish, a page appears with the date on it. The differences that decide whether you keep writing don't show up until the archive has weight — a few dozen posts, categories that no longer map cleanly onto what you're writing about, maybe a second person helping out. That is where blogging bolted onto a page builder starts to show the seams, and it's also the point most reviews stop looking, because most are written by someone who built a demo site with three posts in it.

This one is written from the other end: assume you're writing weekly for a year, and ask what breaks. Two platforms survive that test without a plugin, a workaround or a second tool. The rest are fine for a companion blog next to a marketing site — worth knowing exactly where they stop. Whether those pages then rank is a separate question, covered in our guide to SEO and performance across website builders — this piece is about the writing workflow, not the ranking.

If the site is one page, this whole question may not apply

Before comparing blog engines, it's worth naming the case where none of this matters: a single-person site with no ongoing publishing plan doesn't need a CMS, and bolting a blog module onto it just adds an empty menu item nobody clicks. For a portfolio, a CV turned into a page, or a consultant's one-pager, reach is the strongest answer available — upload a résumé and a photo, answer a short form, pick a look, and it generates a complete page in about twenty seconds, live at a free yourname.joinreach.app subdomain in under two minutes. That's not templated the way a shared gallery is: the layout is assembled from a large set of vetted components — twenty hero layouts alone, across five design families — filled with copy written fresh from the specific CV it was given, not from a prompt describing a business in the abstract.

The limitation that matters here: reach has no CMS at all. One project is one index.html, no sub-pages, no collections, no editorial workflow — content comes from the CV and the profile, full stop. If any part of the plan is "and I'll add posts over time," reach is the wrong tool for that part, cleanly and by design. Everything below is for the reader whose site does need an archive.

Drafting, scheduling and more than one author

Wix and Squarespace both handle the single-author case well: a rich-text editor, a scheduled-publish date, draft state, and post-level SEO fields. Squarespace's editor is the more consistent of the two — blocks behave the same in a blog post as on any other page, which sounds trivial until you've used a builder where they don't. Neither, though, was designed around a second byline. Wix's Light plan includes two collaborators total, covering a blog and its owner, not an editorial team; Squarespace's Basic plan gives two contributors, and permissions on both are closer to "can edit any page" than "can write on this blog."

Webflow's editor mode is built for exactly this — content editors can draft and publish blog posts without touching the site's design in Designer — but the CMS that makes a real blog possible only starts at Premium, not Basic. That's the trap: comparing Webflow's cheapest paid tier against Wix or Squarespace means comparing a plan with no blog collection against two that have one.

Ghost's editor autosaves without a spinner, scheduling is a first-class action rather than a menu item three clicks deep, and post status — draft, scheduled, published, sent — is visible at a glance across the list. Its Starter plan limits you to one staff user; multi-author only opens up on Publisher and above.

WordPress is the only platform here with no ceiling on author count baked into the pricing: Author, Editor, Contributor and Administrator are distinct from install day one, and a fifth writer costs nothing extra. The tradeoff is that nothing about it is opinionated — you're choosing an editor plugin, choosing whether contributors need approval, choosing everything.

Tool	Cheapest plan with a real blog	Authors on that plan
reach	$4.99/month or $49/year (Premium)	No CMS — one page, no blog module
Wix Light	$17/month, annual	2 collaborators
Squarespace Basic	$19/month annual, $25 monthly	2 contributors
Webflow Premium	$25/month annual, $39 monthly	Editor-mode seats, priced separately
Ghost Starter	$18/month, billed annually	1 staff user
WordPress.org (hosting only)	from ~$1–3/month intro	Unlimited, no plan gate

Prices checked August 2026. reach's row exists to be honest about scope, not to compete on it: there is no blog here to compare, which is the entire point of the section above — buying Premium for a blog module that doesn't exist would be a mistake, not a plan choice.

Categories, tags and an archive that stays usable

Ten posts don't need categories. A hundred do, and this is where most blog modules reveal they were designed for ten.

Wix and Squarespace both support categories and tags, and both render an archive page automatically. What neither handles gracefully is an archive that's grown organically for a year — categories created early tend to overlap with ones added later, with no built-in way to merge or restructure them without editing every post individually. Squarespace's tag and category pages are functional but plain, with no faceted filtering and no way to combine a tag and a category in one view — a real limitation once a single tag returns forty results.

Webflow's CMS collections are the most structurally sound of the general builders here: a blog post is a full CMS item with as many custom fields as you define — a category isn't just a label, it can be its own collection, and the archive can be filtered and sorted with the same visual tools used for any other collection. The cost is that a well-organized Webflow blog is a design project, not a settings panel.

Ghost keeps this deliberately narrow — posts and pages, tags with no separate category taxonomy, no custom content types, no plugin ecosystem to add them. For a single-focus publication that's a feature: there's no wrong way to organize a hundred posts when there are so few structures to misuse. For anything that wants a real taxonomy of distinct content types, Ghost is a boundary you'll hit and can't extend without a Handlebars theme — code, either way.

WordPress has the deepest native taxonomy here: hierarchical categories, flat tags, custom taxonomies for anyone willing to add a plugin or a few lines to functions.php. A hundred-post archive organized well in WordPress stays organized well at a thousand, which isn't equally true of the others. The cost, made concrete rather than theoretical: Patchstack's State of WordPress Security in 2026 counted 11,334 new vulnerabilities across the ecosystem in 2025, up 42% year on year, 91% of them in plugins rather than core. The taxonomy plugin that solves your organization problem is also software you now have to keep updated.

Feeds, newsletters and where a second tool still shows up

Every platform here ships an RSS feed by default — not a differentiator. What differs is what happens after the feed, when the goal shifts from "publish a post" to "get someone to read it without checking back."

Wix, Squarespace and Webflow all stop at the feed. None ships subscriber management, paid tiers or email delivery as part of the blog — you're wiring up Mailchimp, ConvertKit or a similar tool separately, which works but leaves the subscriber list and the content in two systems that don't share state. WordPress is the same story unless you add a newsletter plugin, reintroducing the plugin-maintenance cost from the previous section for a feature the others don't build in either.

Ghost is the one exception, and it's structural rather than bolted on: subscriptions, member management, paid tiers and email delivery are native to the product. A Ghost blog can charge for a membership tier from the same dashboard that publishes the post, and the email delivery Ghost(Pro) bundles is, per the vendor's own guidance, the most commonly underestimated cost of self-hosting Ghost instead. If the plan is ever "this becomes a subscription business," Ghost is built around that transition — that's the entire reason the product exists.

Getting the archive back out again

This is the question almost no comparison asks, because it only matters on the way out, and by the time someone's leaving a platform they're past reading reviews of it.

Wix and Squarespace both let you export content, but what comes out is closer to what a visitor sees than what a CMS needs to rebuild elsewhere — formatting, categories and metadata don't reliably survive the trip, so migrating off either one in practice means a manual rewrite of the archive, post by post. Webflow's CMS export is similarly limited to what the platform hands over in its own format, not a portable content dump.

Ghost and WordPress treat export as a real feature. WordPress's native export is XML that any other WordPress install, and most CMS platforms with an import tool, can read directly — true for close to two decades, and one reason the software has outlasted every hosted competitor launched against it. Ghost exports a complete JSON archive of every post, tag and setting, importable into another Ghost instance or convertible by third-party tools into formats other platforms accept. Neither is effortless, but both are genuine round trips: content you can take somewhere else, not just look at on the way out. The mechanics are in how to export your site from a builder, for anyone weighing this before they commit rather than after.

The two worth writing in weekly

Ghost and WordPress are the two platforms here built by people whose job was running a publication, and it shows in exactly the places a general builder's blog module doesn't: authorship that scales past one person without a plan upgrade, an archive structure that survives a year of posts, and an export that's a real migration path rather than a manual copy-paste job.

Between the two, the choice is less about features than about which failure mode you'd rather manage. Ghost is deliberately narrow — no plugin ecosystem, no custom content types — in exchange for an editor and a subscription business built into the same product; its pricing (Starter and Publisher both capped at 1,000 members, then a jump to $199/month on Business for 10,000) is billed annually, with monthly rates not verified, and a portfolio alongside the blog needs a Handlebars theme regardless. Prices checked August 2026. Ghost's full tier structure is in our Ghost review. WordPress is the opposite trade: no ceiling on structure or authors, but a real and recurring maintenance job, made concrete by that 11,334-vulnerability figure rather than reputation alone.

Wix, Squarespace and Webflow remain reasonable choices for a blog next to a marketing site that gets a post a month rather than a post a week — the writing experience on all three is fine for that cadence, and the archive rarely grows large enough to hit the limits above. None of them are built for a publication as the main product. Notion Sites belongs in that same companion category for a different reason, covered in our Notion Sites review: its blogging limits come from being a database renderer first, not from a CMS design choice at all.