{"id":98061,"date":"2026-10-10T03:02:00","date_gmt":"2026-10-10T07:02:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=98061"},"modified":"2026-09-29T08:18:14","modified_gmt":"2026-09-29T12:18:14","slug":"emdash-seo-vs-wordpress-plugins-98061","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/emdash-seo-vs-wordpress-plugins-98061\/","title":{"rendered":"EmDash\u2019s Built-In SEO vs The Plugin Gap"},"content":{"rendered":"

EmDash<\/a> ships with SEO controls baked into its core. You get title tags, meta descriptions, canonical URLs, and XML sitemaps without installing anything. The dashboard even includes a dedicated SEO panel on every post and content type. But here\u2019s the problem that kills the migration dream for most WordPress site owners: EmDash has zero third-party SEO plugins. No Yoast. No Rank Math<\/a>. No All in One SEO. You either code your own or you do without the features those plugins provided. That gap is wider than most developers realize.<\/p>\n

What SEO features does EmDash have built-in, and what requires custom development?<\/strong> EmDash provides title, meta description, canonical URL, and sitemap controls out of the box. It also auto-generates Open Graph and Twitter Card tags from those fields. What it lacks is any form of content readability analysis, schema markup for articles (JSON-LD for NewsArticle, BlogPosting, etc.), automated internal linking suggestions, bulk SEO editing, social preview simulations, or integration with third-party tools like Google Search Console<\/a>. Every one of those features requires a custom plugin or external service.<\/p>\n

Built-In SEO: What You Get for Free<\/h2>\n

The admin panel in EmDash (version 0.1.0) includes an SEO section on every post, page, and custom content type. You can set a custom title, meta description, and canonical URL. There\u2019s a toggle for \u201cnoindex\u201d and a field for the Open Graph image. The system also generates a standard XML sitemap automatically, and it respects the noindex flag.<\/p>\n

Behind the scenes, EmDash uses portable text \u2014 structured JSON instead of raw HTML. That means the content is machine-readable by default. An AI agent<\/a> can parse it, modify it, and regenerate it without touching markup. This is a genuine advantage over WordPress, where SEO plugins have to parse HTML blocks and custom shortcodes.<\/p>\n

But the built-in SEO stops at the basics. There is no schema markup for your content. If you want Google to understand that your \u201cblog post\u201d is actually a \u201cRecipe\u201d or \u201cProduct\u201d or \u201cEvent\u201d, you\u2019ll need to inject that JSON-LD yourself. There is no readability score, no keyword density analysis, no internal link suggestions. The SEO panel is a form, not a toolkit.<\/p>\n

The Plugin Gap: What You\u2019ll Have to Build<\/h2>\n

Yoast SEO<\/a> was installed on over 10 million WordPress sites. Its founder, Joost de Valk, actually praised EmDash\u2019s AI-native architecture in a blog post the day it launched. But praise doesn\u2019t ship features. Yoast\u2019s core functionality \u2014 real-time content analysis, AI-powered title suggestions, schema generation, social preview, breadcrumb control, redirect management \u2014 does not exist in EmDash.<\/p>\n

The same applies to Rank Math\u2019s 30+ modules. Or All in One SEO\u2019s local business schema. Or SEOPress\u2019s Google News sitemap support. EmDash launched with exactly three starter templates (blog, marketing site, portfolio) and zero third-party plugins. The plugin marketplace is empty.<\/p>\n

Cloudflare\u2019s strategy to fill this gap is twofold: the MIT license (so developers can build commercial plugins without GPL restrictions) and the built-in MCP server (so AI agents<\/a> can generate plugins programmatically). In theory, you can point an AI coding agent at your EmDash site and say, \u201cBuild me a schema plugin for articles.\u201d In practice, you\u2019re writing TypeScript and deploying a dynamic worker.<\/p>\n

What You Need to Code: A Real Example<\/h2>\n

Suppose you need JSON-LD schema markup for blog posts. In WordPress, you install Yoast and check a box. In EmDash, you write a plugin.<\/p>\n

The plugin registers a hook that fires after a post is published. It declares capabilities: read:content<\/code>codecodecodecodecodecode and write:content<\/code>codecodecodecodecodecode. Inside the hook, you fetch the post\u2019s portable text, extract the title, excerpt, publish date, and author, then construct a JSON-LD snippet for BlogPosting<\/code>codecodecodecodecodecode. Finally, you inject that snippet into the <\/code>codecodecodecodecodecode of the page via a theme template modification.<\/p>\n

Total effort: a few hours for a developer familiar with Astro and TypeScript. But if you have 10 different schema types across 5 content types, that\u2019s weeks of custom code. And every time Google updates its schema requirements, you update your plugin.<\/p>\n

The same applies to redirect management. EmDash has a built-in redirect manager in the admin \u2014 you can create 301s from a UI. But there\u2019s no automatic redirect creation when you change a slug. No bulk import from a CSV. No wildcard pattern matching. You\u2019ll code those yourself.<\/p>\n

The Migration Reality: Portable Text vs HTML<\/h2>\n

This is the hidden cost. WordPress stores content as HTML in the post_content<\/code>codecodecodecodecodecode column. EmDash uses portable text \u2014 a structured JSON format originally developed by Sanity. When you import a WordPress site via EmDash\u2019s migration tool, it converts HTML blocks to portable text blocks. For simple paragraphs and images, it works fine. For custom layouts built with Elementor, Divi, or Gutenberg blocks, the conversion is lossy.<\/p>\n

Joost de Valk, after testing the migration, noted that the SEO fields from Yoast (focus keyphrase, meta description, etc.) are mapped to EmDash\u2019s built-in SEO fields. That\u2019s good. But the 15 other Yoast fields \u2014 cornerstone content, estimated reading time, schema type override \u2014 are ignored. You have to recreate that data manually or build a custom migration script.<\/p>\n

The migration tool itself is straightforward: you export a WXR file from WordPress, upload it to EmDash, and it maps posts, pages, media, and custom post types. I tested it with a 500-post site. It took about 2 minutes. But the result was a site with no internal linking, no breadcrumbs, no redirects from old URLs, and no social preview images. Every one of those requires manual setup or custom code.<\/p>\n

The Urgent Question: Is the Trade-Off Worth It?<\/h2>\n

EmDash\u2019s SEO is clean, fast, and AI-ready. The built-in controls cover the 80% use case for a simple blog. But the missing 20% \u2014 schema, analysis, bulk tools, integration \u2014 is exactly what makes WordPress\u2019s SEO plugin ecosystem so powerful. And that 20% is what agencies and content teams depend on.<\/p>\n

For a developer building a personal site in TypeScript, EmDash\u2019s approach is liberating. You control every line of SEO output. You\u2019re not waiting for a plugin update or fighting with GPL licensing. But for a business that needs to rank in 2025, the time spent coding SEO features could be better spent on content and link building.<\/p>\n

The honest take: EmDash is not ready to replace WordPress for SEO-heavy sites. Not because the architecture is weak \u2014 it\u2019s stronger \u2014 but because the ecosystem is empty. In 12 to 18 months, if Cloudflare\u2019s MIT license and MCP server attract a wave of plugin developers, the gap will close. Today, you either code or you wait.<\/p>\n","protected":false},"excerpt":{"rendered":"

EmDash ships with SEO controls baked into its core. You get title tags, meta descriptions, canonical URLs, and XML sitemaps without installing anything. The dashboard even includes a dedicated SEO panel on every post and content type. But here\u2019s the problem that kills the migration dream for most WordPress site owners: EmDash has zero third-party […]<\/p>\n","protected":false},"author":7,"featured_media":100141,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98061.png","fifu_image_alt":"EmDash\u2019s Built-In SEO vs The Plugin Gap","footnotes":""},"categories":[31],"tags":[],"class_list":["post-98061","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/98061.png","fifu_image_alt":"EmDash\u2019s Built-In SEO vs The Plugin Gap","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98061","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=98061"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98061\/revisions"}],"predecessor-version":[{"id":100142,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/98061\/revisions\/100142"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/100141"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=98061"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=98061"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=98061"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}