Publish to WordPress Without the Block Editor

Gutenberg divides people. Some find the drag-and-drop block editor intuitive. Plenty of developers, technical writers, and content teams find it gets in the way — whether that's because it mangles markdown, doesn't work well with code-heavy posts, or simply doesn't fit into an existing review workflow. The good news is that WordPress has a REST API, and there are several legitimate ways to publish content without ever opening the block editor.

This guide covers each option in detail: what it does, where it falls short, and what kind of publisher it works best for.

Why People Skip Gutenberg

The block editor isn't bad for everyone. If you're building landing pages with custom layouts, or you enjoy clicking through block settings, it works well enough. But for writers and developers who live in other tools, it creates real friction:

• Markdown gets mangled. Paste a well-formatted markdown document into Gutenberg and watch it turn into a mix of blocks, raw text, and stray formatting. There's no reliable one-step conversion.
• You can't write in your own editor. If your workflow starts in VS Code, Obsidian, iA Writer, or Notion, you have to switch contexts every time you publish. That context switch breaks flow and adds time.
• Code-heavy posts are painful. Gutenberg's code block is basic. Syntax highlighting, line numbers, and copy buttons all require extra plugins. Fenced code blocks from markdown don't convert cleanly.
• No SEO automation from external tools. If you're generating content elsewhere and want to set Rank Math or Yoast metadata programmatically, Gutenberg isn't part of that pipeline.
• Slow for teams with external review workflows. If your drafts live in Notion, Google Docs, or a Git repository, manually copying them into Gutenberg for final publishing is an error-prone extra step that doesn't scale.

None of these are reasons to abandon WordPress entirely. The platform has too much going for it — SEO plugins, hosting options, media management, plugin ecosystem. The fix is publishing through a different interface, not switching platforms.

Option 1 — Classic Editor Plugin

The simplest escape hatch: install the Classic Editor pluginfrom the WordPress repository. This replaces Gutenberg with the old TinyMCE-based editor that WordPress used before version 5.0. It's free, officially supported by the WordPress team, and takes about 30 seconds to set up.

Once active, you get a plain rich-text editing area and a sidebar with post settings. You can also switch individual posts between classic and block editor if you want to keep Gutenberg for some content.

Pros: Free, one-click install, officially supported, well understood. Pasted HTML is less likely to get scrambled than in Gutenberg. Familiar to anyone who used WordPress before 2018.

Cons:You're still inside WordPress. Writing still happens in a browser textarea, not your preferred editor. No image automation, no SEO metadata from external sources, no code highlighting. The Classic Editor will remain supported until at least 2025, but it's a tool with a sunset horizon.

Best for: Teams or individuals who want to eliminate Gutenberg entirely without changing their existing WordPress workflow.

Option 2 — WordPress REST API

WordPress ships with a REST API at /wp-json/wp/v2/. You can create, update, and publish posts via standard HTTP requests — no browser required. This opens the door to automation: CI/CD pipelines, scripts triggered on Git push, scheduled publishing jobs, or any tool that can make HTTP calls.

Here's a minimal example using curl to create a draft post with Application Passwords authentication (available in WordPress 5.6+):

curl -X POST https://yourblog.com/wp-json/wp/v2/posts \
  -H "Content-Type: application/json" \
  -u "your-username:xxxx xxxx xxxx xxxx xxxx xxxx" \
  -d '{
    "title": "My Blog Post",
    "content": "<p>Post content as HTML.</p>",
    "status": "draft",
    "categories": [5],
    "tags": [12, 18]
  }'

The response includes the new post's ID, which you can use for follow-up requests. That's where the complexity begins: publishing a real post via the REST API isn't just one call. It's several:

• Image uploads — each image in the post body must be uploaded to /wp-json/wp/v2/media first, then the returned URL replaces the original reference in the content.
• Featured image — upload the image as media, get back a media ID, then set featured_media on the post.
• SEO metadata — neither Rank Math nor Yoast expose standard REST fields by default. Both have their own custom endpoints or post meta fields that require additional configuration.
• Code highlighting — the API accepts HTML, but styled code blocks require a client-side library (Prism.js, Highlight.js) loaded by the theme. You need to output the right HTML structure for your theme's highlighter.

Pros: Platform-agnostic, automatable, works in any language, free.

Cons:You're building and maintaining a publishing tool. Every edge case (images in tables, caption blocks, embeds) requires custom handling. Authentication needs to be kept secure. Updates to the Rank Math or Yoast API can break your script.

Best for: Developers who want full control over the pipeline and are comfortable building and maintaining tooling.

Option 3 — Desktop Markdown Editors (Ulysses, iA Writer, MarsEdit)

Several native Mac apps let you write in markdown and publish to WordPress directly. Ulysses and iA Writer are writing-focused apps with WordPress publishing built in. MarsEdit is a dedicated blog editor for macOS. All three connect to your WordPress site via XML-RPC or the REST API and handle basic publishing from within the app.

The writing experience in these apps is genuinely good. Ulysses has a clean distraction-free interface with typeface controls and export options. iA Writer is minimal and focused. MarsEdit is built specifically for bloggers and understands categories, tags, and post status natively.

Pros: Native app performance, beautiful writing environments, no browser required, direct publish to WordPress.

Cons: Mac and iOS only — no Windows, no Linux, no web interface. Images are uploaded as-is with no optimization or automation — you manage filenames and alt text manually. Code blocks are published as plain <pre>tags with no syntax highlighting. No SEO metadata automation — you set the title and that's about it. No featured image generation. Pricing ranges from $30 one-time (MarsEdit) to $50/year (Ulysses) to $50/year (iA Writer).

Best for: Non-technical writers on Apple devices who value a premium writing experience and publish mostly text content without code examples or complex SEO requirements.

Option 4 — Static Site Generators with WordPress Headless

A more architectural approach: decouple the WordPress backend from the frontend entirely. Use WordPress purely as a headless CMS — content management, user roles, REST API — while building the public-facing site in Next.js, Astro, Hugo, or another static site generator. Your content team writes in markdown files committed to a Git repository, a build process converts them to HTML, and WordPress stores the structured content.

This setup gives developers complete control over the front end. The Gutenberg editor might still exist in the WordPress admin for less technical users, but technical contributors never touch it. Everything goes through version-controlled markdown files and a CI/CD pipeline.

Pros: Developers work entirely in their existing tools (VS Code, Git). Full control over rendering, performance, and code highlighting. Content is version-controlled. Great for documentation-heavy or technically complex sites.

Cons:Significant upfront engineering investment. Non-technical contributors still need a way to publish. Image optimization, SEO metadata, and featured images all need to be solved at the pipeline level. This is the right architecture for a small engineering team running a technical blog — it's overkill for a content site or a solo blogger.

Best for: Developer teams running technical documentation or engineering blogs who want full control over the front end and are comfortable building and maintaining a custom publishing pipeline.

Option 5 — Notipo (Write Markdown, Publish Everything)

Notipois a markdown editor built specifically for WordPress publishing. You write in the built-in editor — or sync content from Notion — and Notipo handles the entire publishing pipeline via the WordPress REST API. You never open Gutenberg.

What gets handled automatically on each publish:

• Markdown to HTML — your markdown is converted to clean, well-structured HTML before it reaches WordPress. Headings, lists, blockquotes, and links all render correctly.
• Image uploads — every image in your post is uploaded to your WordPress media library automatically. No broken external links, no manual upload steps.
• Featured image — set a featured image from the editor and Notipo uploads it and sets it as the post thumbnail. Or leave it blank and Notipo generates one based on your title and category.
• SEO metadata — set your meta description, focus keyword, and SEO title in Notipo. These are written to Rank Math or Yoast via their APIs on publish.
• Code highlighting — fenced code blocks are converted to syntax-highlighted HTML. Works with any theme that loads Prism.js or Highlight.js.
• Categories and tags — set from the Notipo editor, applied to the WordPress post on publish.

The key difference from the REST API approach: Notipo is a complete tool, not a starting point. You don't build the image upload logic, the SEO connector, or the featured image pipeline yourself. It's already there.

The key difference from desktop apps like Ulysses: Notipo works on any platform (Mac, Windows, Linux, browser), handles code syntax highlighting, and automates SEO metadata. It's built for technical and content teams, not just writers on Apple devices.

Pricing: Free for up to 5 posts per month. Pro plan is $19/month for unlimited posts and all features.

Comparison Table

Which One Should You Pick?

The right choice depends on what you're optimizing for:

• You just want a simpler editor inside WordPress: Install the Classic Editor plugin. It's free, takes a minute, and removes all Gutenberg friction without changing anything else.
• You want to automate publishing from a script or CI/CD pipeline: Use the WordPress REST API directly. Expect to spend time on image handling and SEO integration, but you'll own the full pipeline.
• You write on a Mac and want a beautiful writing app: iA Writer or Ulysses are excellent — as long as you don't need code blocks, SEO metadata, or Windows support.
• You run a developer-oriented technical blog with a small engineering team: A headless WordPress setup with a static site generator is worth the investment. Your content lives in Git, your front end is yours, and Gutenberg is irrelevant.
• You want the full pipeline automated without building anything: Notipo is the only option that covers images, code highlighting, SEO metadata, featured images, and publishing in a single step — without writing any code and without opening Gutenberg.

If you publish once a month, any of these approaches works. If you're publishing weekly or running a team, the time lost to manual image uploads, formatting fixes, and metadata entry adds up quickly. A tool that handles the pipeline end-to-end starts paying for itself in the first week.

The Bottom Line

Gutenberg is optional. WordPress's REST API has been stable for years, and there are mature tools at every level of the stack — from a simple plugin swap to a fully automated publishing pipeline. The block editor is a good choice for some users. For writers who prefer markdown, developers who want automation, and teams who have review workflows outside WordPress, there are better options.

If you want to skip Gutenberg entirely and publish from a markdown editor with images, SEO, and featured images handled automatically, try Notipo free— up to 5 posts per month, no credit card required.