How to Convert Classic Editor Pages to Gutenberg in WordPress with AI

TL;DR

To convert Classic Editor pages to Gutenberg with AI, ask the AI to convert the pages into Gutenberg/block editor pages while preserving the existing content, layout, and front-end appearance. Review the plan first, approve the conversion, then check each page in the editor and on the front end.

A 3-minute, 7-second walkthrough showing how WPadmin.AI Premium converts multiple Classic Editor WordPress pages into Gutenberg blocks and verifies the result.

Key Takeaways

• AI can reduce repetitive manual work when converting multiple Classic Editor pages into Gutenberg blocks.
• A good prompt should name the pages or site area and ask to preserve content, layout, and front-end appearance.
• Reviewing the plan before implementation helps confirm what pages will be converted.
• After conversion, verify the editor view, front-end appearance, and completion report.

Classic Editor is still active on many WordPress websites. If your pages were built before Gutenberg became the default editor, converting those pages into blocks can make future editing easier. The problem is that rebuilding every page by hand can take a long time. This walkthrough shows how AI can help convert Classic Editor pages into Gutenberg/block editor pages while preserving the existing content and front-end look.

Why Classic Editor to Gutenberg conversion can take time

A Classic Editor page may look simple on the front end, but converting several pages still means reviewing content, page structure, headings, images, spacing, and links. If you have Services, Pricing, About, Team, and Contact pages, manual conversion can quickly turn into repetitive work.

Using an AI plugin like WPadmin.AI Premium helps because the task can be planned first, then applied across multiple pages. In the video, the request is to convert the whole website into Gutenberg, and WPadmin.AI Premium reviews the site before presenting a plan.

How to prompt the conversion task

The prompt should explain what needs to be converted and what must stay the same. If the task covers more than one page, it is better to scope the request first. See the guide on how to scope a WordPress task correctly.

Convert my Classic Editor pages into Gutenberg/block editor pages while preserving the existing content, layout, and front-end appearance.

In the demo, WPadmin.AI Premium spends about two and a half minutes reviewing the site and preparing a plan. After the plan is approved, it starts the actual conversion and reports which pages were converted.

What to check after conversion

1. Open each converted page in the WordPress editor and confirm it now uses Gutenberg blocks.
2. Compare the front-end page with the original version to confirm the content still looks right.
3. Check important pages such as Services, Pricing, About, Team, and Contact.
4. Review the completion report so you know which pages were converted.

You might also like: How to Convert Gutenberg to Elementor in WordPress with AI.

Plain-English glossary

Need a quick definition? Read the short glossary entry for Gutenberg / Block Editor.

Video chapters and transcript

0:00 – Why Classic Editor sites still matter

The video opens by explaining that Gutenberg launched in December 2018, but many WordPress websites still use Classic Editor. The walkthrough focuses on converting those older pages into Gutenberg or the block editor with AI.

0:35 – Demo site with Classic Editor pages

The demo website includes several pages, including Services, Pricing, About, Team, and Contact. These pages were built with Classic Editor.

0:55 – Starting WPadmin.AI Premium

WPadmin.AI Premium is opened and ready to work. The task starts in planning mode with a simple request to convert the whole website into Gutenberg.

1:20 – Reviewing the conversion plan

WPadmin.AI Premium reviews the site for about two and a half minutes, identifies the pages, and presents a plan. The plan can be reviewed before choosing to implement it.

1:50 – Running the conversion

After approval, WPadmin.AI Premium starts the actual conversion. It finishes the work and gives a report of the pages it converted and the changes it made.

2:15 – Checking pages in Gutenberg

The converted pages are opened in the editor. The Classic Editor view is gone, and the content is now shown as Gutenberg blocks.

2:45 – Reviewing the front end

The pages are refreshed on the front end to confirm they still look similar to the original Classic Editor pages while now being editable with Gutenberg blocks.

Want WPadmin.AI Premium to convert WordPress pages for you?

Download now