WordPress moved to the Gutenberg block editor in 2018. It was a big shift: instead of writing in a single rich text field, content is now composed of discrete blocks — paragraphs, headings, images, columns, buttons, galleries, embeds, and custom blocks.

This was great for content layout. It was terrible for every tool that tried to work with WordPress content from the outside.

The block problem

When you write a blog post in ChatGPT, Jasper, or any other AI writing tool, the output is plain text or markdown. It doesn't contain Gutenberg block markup.

Here's what a simple two-column layout looks like in Gutenberg:

<!-- wp:columns -->
<div class="wp-block-columns">
  <!-- wp:column -->
  <div class="wp-block-column">
    <p>Left column content</p>
  </div>
  <!-- /wp:column -->
  <!-- wp:column -->
  <div class="wp-block-column">
    <p>Right column content</p>
  </div>
  <!-- /wp:column -->
</div>
<!-- /wp:columns -->

When you paste plain text over this, the block structure vanishes. Your columns become a single column. Your button blocks become text. Your carefully designed layout becomes a wall of paragraphs.

Why this matters more than you think

For simple blog posts (just paragraphs and headings), the copy-paste approach works okay. But modern WordPress content isn't simple:

• Product pages use columns, feature grids, and CTA blocks
• Landing pages have hero sections, pricing tables, and testimonials
• Blog posts include callout boxes, code blocks, and embedded media
• Documentation uses custom blocks for warnings, tips, and examples

If your content strategy involves anything beyond basic paragraphs, the disconnect between AI tools and Gutenberg blocks is a real problem.

Shortcodes: the other casualty

Many WordPress sites rely on shortcodes — [contact-form], [gallery ids="1,2,3"], [pricing-table]. These are processed by WordPress and plugins to render dynamic content.

When you edit content outside WordPress and paste it back in, shortcodes can get corrupted, deleted, or duplicated. This is especially problematic when AI tools try to "help" by reformatting or removing what they don't understand.

What a WordPress-native approach looks like

The fundamental problem is that most AI writing tools treat content as text. WordPress treats content as a tree of typed blocks. These are fundamentally different data structures, and converting between them loses information.

A WordPress-native AI tool would:

1. Understand block structure. Know what Gutenberg blocks are and preserve them during editing. If your post has columns, they should still be columns after the AI makes changes.

2. Handle shortcodes. Recognize shortcodes as functional elements and leave them intact, even when surrounding content changes.

3. Publish in block format. Send content to WordPress as proper Gutenberg blocks, not as HTML that WordPress has to interpret.

4. Support round-trip editing. Pull an existing WordPress post (with all its blocks), edit it with AI assistance, and push it back — with the block structure preserved.

The practical impact

Teams that publish content with complex layouts face a choice:

Option A: Use AI tools for text, then spend time rebuilding the layout in WordPress manually. This works but adds significant time to every piece of content.

Option B: Skip AI tools for layout-heavy content and write everything in WordPress directly. This works but gives up the productivity benefits of AI assistance.

Option C: Use a tool that understands Gutenberg blocks natively. This preserves both the AI productivity gains and your content's structure.

Most teams end up with Option A by default. They accept the formatting tax as a cost of doing business with AI. But it doesn't have to be that way.

---

Karyla preserves your Gutenberg blocks, shortcodes, and SEO fields during round-trip editing. Write with AI in your brand voice, publish to WordPress — layout intact. Start free.