Cloudflare EmDash 1.0: Should Your WordPress Site Switch?

Another update notice lands in your inbox, a page loads slower than it should, and somewhere in your memory sits the last time a plugin broke something. Then a headline says Cloudflare has released a free WordPress alternative, and the question forms on its own: is it time to move? Cloudflare EmDash is a free, open-source content management system that Cloudflare announced in a 1.0 release on September 28, 2026. It is built on Astro and TypeScript, it is licensed under MIT, and Cloudflare says it uses no WordPress code. For a small business with a working site, the real question is narrower than the headlines: what would come across, what would you have to rebuild, what would it cost, and what does "lock-in" actually mean here? The answers come from Cloudflare's own announcement and the EmDash documentation, and most of them depend on what your site does today. You can find out in about ten minutes, before anyone sells you anything.

How do you know if EmDash even fits your WordPress site?

Start with what your site does, not with which platform is newer. A brochure site with posts, pages, a contact form and a handful of plugins is a very different move from a site that takes bookings, sells products or runs a members area. EmDash's documentation for people coming from WordPress is direct about the trade: your content can move, but WordPress plugins and themes cannot simply be dropped in. They have to be ported or rebuilt.

That single fact sorts most sites into one of three groups. If your site is mostly content, with simple forms, a switch may be worth a test. If it depends on a store, memberships, a page builder or several integrations, a switch is a rebuild project, and it deserves a proof of concept before any decision. And if your main pain is update notices, a slow host or a plugin pile you no longer trust, the cheapest fix may be on the WordPress side, where the WordPress documentation recommends keeping plugins and themes updated.

Nothing in this is a judgment on either platform. WordPress is a mature platform with a long track record, and EmDash is a brand new 1.0 release with its own strengths. The point is fit. Before you spend money on either path, find out which group your site belongs to.

What is Cloudflare EmDash, and what did the 1.0 release change?

Cloudflare's 1.0 announcement describes EmDash as a stable, free, open-source CMS built on Astro. The project is written in TypeScript and includes an admin interface, an API, a command line tool, a media system, localization, migration workflows, deployment tools and an MCP server. Its plugin model runs each plugin in an isolated Worker environment and asks it to declare the capabilities it needs. Cloudflare first introduced the project as an early preview on April 1, 2026, and its original introduction framed EmDash as a successor to WordPress that takes a different approach to plugin security.

The EmDash repository lists the features a small business would care about: Astro templates, custom content types, forms through plugins, SEO fields, menus, taxonomies, media, search, revisions and scheduled publishing. It also notes an emerging e-commerce plugin ecosystem. "Emerging" is the word to keep in mind. The plugin list and maintenance commitments can change after release, so confirm that a plugin you need exists, works with your version and has an active maintainer immediately before you commit to anything.

What does EmDash cost, and what does "free" leave out?

The software has no license fee. Running a website still has costs, and the documentation shows where they come from. EmDash can run on Cloudflare using Workers, D1 and R2, or on a Node.js server with SQLite and compatible storage adapters. On Cloudflare, Workers pricing lists a Free plan with 100,000 requests per day. The Paid plan costs $5 per month at a minimum and includes 10 million requests and 30 million CPU milliseconds monthly, with additional usage charges beyond that. Static assets are free and unlimited under the pricing model Cloudflare cites, and the limits page explains what each plan allows.

Those numbers cover hosting only. The larger cost for a business with an existing site is the work around the software: rebuilding the design as an Astro template, replacing plugin behavior, moving and checking content, setting up redirects, testing, and monitoring after launch. Someone also has to own updates, backups, security, DNS, email delivery and recovery. A switch can reduce routine PHP and plugin maintenance, but it does not remove the need for someone technical to own the site.

What moves from WordPress, and what stays behind?

The migration guide describes two routes: a standard WordPress export file (called WXR) or the EmDash Exporter plugin. The content import page lists what the export file brings across: posts, pages, custom post types, taxonomies, reusable blocks, authors and the URLs of attached media. The Exporter plugin adds supported comments, menus, settings, media metadata, Yoast or Rank Math SEO fields and compatible custom fields.

Two details catch people out. First, media files are downloaded separately from the export, so your WordPress site has to stay up and reachable until the copy and URL rewrite steps finish. Second, WordPress statuses such as pending, private, scheduled and trash are converted to drafts, so someone needs to review them before anything goes live.

The other side of the ledger is just as clear in the documentation. Themes, page-builder layouts, shortcodes, plugin behavior, forms, booking systems, checkout systems and proprietary fields do not carry over automatically. The guide to porting WordPress themes covers how a design gets rebuilt. In practice, the part of your site that earns money, whether that is the quote form, the booking calendar or the cart, is usually the part that needs the most rebuilding and testing.

What does lock-in actually mean with EmDash?

"Lock-in" can mean several different things: the license on the code, the place it runs, where the database and files live, the plugin runtime, or the agency that built the site. Cloudflare's documentation answers the first two directly. EmDash is MIT licensed, which gives you legal use of the CMS code. It is also not limited to Cloudflare, because Cloudflare's announcements and the repository describe running it on a Node.js server with SQLite and compatible storage adapters as well.

The qualification is that Cloudflare's runtime gives the deepest integration. Sandboxed plugins, Workers, D1 and R2 are Cloudflare services, so a site built to use them leans on Cloudflare in a way a plain Node.js install does not. If you ever want to leave, EmDash offers site and seed export tools, which you can read about in the site transfer guide and the command line reference. Those tools move your content and structure out. Another platform may still need conversion work on top.

So, the practical answer for a business owner is this: ask where the site will be hosted, who holds the accounts, and what the exit path costs before you sign anything. That is good practice on any platform. It matters more than whether the CMS code itself is open.

Will switching hurt your Google rankings?

Changing platforms is a site move, and Google has guidance for it. Its site move documentation recommends preparing the new site, mapping every old URL to its new address, testing before launch, using permanent redirects, updating internal links, canonicals and your sitemap, and monitoring Search Console on both the old and new URLs. Google's page on 301 redirects states that permanent redirects do not cause a loss of PageRank, and recommends keeping them for at least one year.

Rankings can still move while Google recrawls and reindexes your URLs, so a dip after launch does not automatically mean something went wrong. In the other direction, nothing in the guidance says a new CMS improves rankings by itself. Your search results depend on how well the move is done and on the quality of the content, not on the name of the platform. EmDash has its own SEO guide for its SEO fields, and the migration guide notes that Yoast and Rank Math data can be brought across with the Exporter plugin.

The safe pattern is to change one thing at a time where you can. A redesign and a full URL restructure at the same time make problems much harder to trace. If your addresses can stay the same, keep them the same.

What can you check in ten minutes today?

You do not need a developer for the first step. You need a short list of what your site depends on. Open your WordPress dashboard and work through the steps below.

List every active plugin and its job

Open the Plugins screen and write down each active plugin and what it does for the business. Mark each one as essential, replaceable, unused or unknown. The WordPress guide to managing plugins shows where to find them. The result should be a dependency list, not just a plugin count, because a plugin count says nothing about whether one of them runs your booking calendar.

Mark the features you cannot lose

Write down your contact and quote forms, booking, payments, subscriptions, memberships, customer accounts, search, maps, analytics, email delivery and SEO fields. Note whether the site uses WooCommerce, a page builder, custom post types, custom fields or a multilingual plugin. Each item on that list is something an EmDash build has to replace or rebuild and test.

Find out who runs what

Confirm who hosts the site, where the domain is registered, who controls DNS, where backups are stored and who is responsible for updates. Write down an emergency contact. If the answer to any of these is "I do not know," that gap is worth fixing whether or not you ever switch. The WordPress documentation on backups is a good place to check yours.

Save your address list

Export or record your current sitemap and your most important URLs. This is the raw material for a redirect map, and it is the one thing you cannot rebuild later if the old site is gone.

Which route fits your site: clean up, test, or wait?

A switch is one of three sensible paths, and it is often not the first. Which one fits depends on what your inventory showed.

If your problem is maintenance, start with cleanup. Removing plugins you no longer use, updating what remains, moving to better hosting, repairing forms, adding backups and fixing slow pages can solve the problem at lower risk than a migration. That may be the whole answer, and it is a fine answer.

If your inventory shows a content-led site with simple needs, and you or your team like working with modern tooling, a small proof of concept is reasonable. Run a test migration to a separate address, rebuild one representative page, replace one form, and see how the media, redirects and SEO fields behave. This is the moment to learn what the documentation cannot tell you about your particular site.

If the site depends on WooCommerce, complex memberships, proprietary page-builder layouts or a business-critical integration, hold off on any cutover until a proof of concept shows that each of those has a working replacement. Support for each form, booking, payment and store integration has to be confirmed by testing in your own build, and the e-commerce plugin ecosystem is described as emerging.

What goes wrong in a migration, and how do you avoid it?

The usual failures are practical ones, and this list is an order of risk rather than a measured ranking. No study establishes how often each one happens, so treat it as a checklist.

• An incomplete feature inventory: Something the business relies on was never written down, so nobody rebuilds it.
• Broken forms or email delivery: The form looks fine but messages never arrive, which means lost leads with no warning.
• Missing redirects: Old addresses return errors and search visibility takes the hit.
• Media that did not copy: Images and files still point to the old site, which then goes offline.
• Page-builder and shortcode content that renders badly: Text shows up as raw code or as empty gaps.
• SEO fields that did not transfer: Titles and descriptions revert to defaults.
• A DNS cutover before testing: The switch is small in effort and large in consequence.
• No owner for maintenance after launch: The site works until the first thing breaks.

The fixes follow the same order. A short audit fixes a missing inventory. A rebuilt and tested form fixes lost messages. A crawl of the old site fixes redirects. Testing on a phone and a computer before the domain moves catches most of the rest. Revenue failures, meaning forms, checkout, booking and URL access, matter more than visual differences, so test those first.

A successful move has a complete dependency list, a tested build, deliberate decisions about URLs, working forms and analytics, valid canonicals and sitemaps, and a plan to roll back. The owner can edit content, receive leads and get help afterward. An unsuccessful one treats a content import as the whole job. For a sense of what that work costs on the maintenance side, see our post on what website maintenance costs.

Frequently Asked Questions About cloudflare emdash

Is EmDash a WordPress plugin?

No. It is a separate CMS built on Astro and TypeScript, and Cloudflare says it uses no WordPress code.

Is EmDash free?

The CMS is free and MIT licensed. Hosting, Cloudflare usage beyond the free plan, development, storage, migration work and maintenance can still cost money.

Can EmDash import my WordPress site?

Content, yes. It supports a WordPress export file and an Exporter plugin route for posts, pages, taxonomies, media links and more. Themes, plugins, page builders, forms and store functions do not carry over automatically.

Do my WordPress plugins work in EmDash?

Not automatically. Each function has to be replaced, ported or rebuilt, and plugin availability can change after release, so check before you commit.

Is EmDash locked to Cloudflare?

Cloudflare and the EmDash repository describe running it on Cloudflare or on a Node.js server. Cloudflare's runtime offers the deepest integration, and EmDash provides site and seed export tools for leaving, though another platform may still need conversion work.

Will switching platforms hurt my Google rankings?

It can if URLs are not mapped and redirected. Google's site move guidance calls for a URL map, permanent redirects, updated canonicals and sitemaps, and monitoring. Rankings may fluctuate while Google recrawls, and a new CMS does not improve them on its own.

What This Means for You

Cloudflare's EmDash 1.0 is a free, MIT-licensed CMS with a real WordPress import path, and it is worth a look if your site is mostly content and someone can own the technical side. It does not bring your plugins, themes, page builders, forms or store with it, and the free license does not make the finished website free. Lock-in is a smaller question than the headlines suggest, because it can run off Cloudflare and has export tools, but where your accounts live and how easily you can leave are still worth asking.

The value of the ten-minute inventory is that it turns a vague worry into a decision. Some sites will do best with cleanup and steady maintenance. Some will do well with a proof of concept. Some should wait until the pieces they depend on have tested replacements. Any of those outcomes is a good one when it is reached with your own site's facts in front of you.

If you would like a second set of eyes, Web Leveling can go through your plugin list and features with you and tell you which route fits, whether that is cleanup, a test build or staying put. Our web design work covers rebuilds when they are the right call, and our content management work covers keeping the site easy for you to edit. We work with small and medium businesses across the country and overseas. Tell us what your site depends on, and we will help you read the options.

Terms