Activate Classic Editor in WordPress: Return to the familiar editing view

Activate Classic Editor in WordPress: Return to the familiar editing view

Since WordPress 5.0, the Block Editor, also known as Gutenberg, has been the default editor for posts and pages. It works with individual blocks for paragraphs, images, headings, buttons, columns, tables and many other content elements. This is very flexible for modern layouts.

However, many users still prefer the classic editing view. The Classic Editor is more reminiscent of a word processor: a large text field, a simple toolbar and a familiar interface for posts and pages. Especially for older websites, existing workflows, editorial processes or plugins with classic meta boxes, the Classic Editor can still be useful.

What is the Classic Editor?

The Classic Editor is the former standard editing view of WordPress. It is based on a classic text editor with a visual view and a text/HTML view. Many long-time WordPress users know this interface from WordPress versions before 5.0.

The official Classic Editor plugin is maintained by the WordPress team. It restores the former editor and the classic editing screen. It also supports older plugins that require the classic post screen, old meta boxes or classic editor extensions.

Typical reasons for using the Classic Editor:

• Familiar operation: Many users work faster with the classic interface.
• Existing workflows: Editorial teams or teams are accustomed to the old editor.
• Plugin compatibility: Some older plugins work better with classic meta boxes.
• Simple text editing: For purely text-based posts, the Classic Editor is often clearer.
• Less distraction: For some users, the interface feels calmer and more direct.

Classic Editor or Block Editor: Which is better?

There is no universally correct answer. The Block Editor is the current WordPress standard and is actively being developed further. It is particularly suitable for flexible layouts, modern content blocks, reusable elements and block-based themes.

The Classic Editor, on the other hand, is suitable for users who want to maintain simple content without complex layouts or who depend on the old interface for compatibility reasons.

1. Install the Classic Editor plugin

The safest way back to the classic editing view is the official Classic Editor plugin. Install it directly from the WordPress plugin directory.

Proceed as follows:

1. Log in to the WordPress dashboard.
2. Go to Plugins > Add New.
3. Search for Classic Editor.
4. Make sure you select the official plugin from the WordPress team.
5. Click Install Now.
6. Then click Activate.

After activation, the plugin restores the classic editor. Depending on the setting, the Block Editor is completely replaced or users can switch between both editors.

2. Adjust settings under “Writing”

After activation, you will find the most important options under:

Settings > Writing

There you can define which editor should be used by default and whether users are allowed to switch between both editors.

Typical options are:

• Default editor for all users: Classic Editor or Block Editor.
• Allow users to switch editors: Yes or No.

If you work alone and want to use the Classic Editor permanently, you can set it as the default and disable switching. If several people work on the website, it may make sense to allow both editors.

3. Use the Classic Editor in a team

In teams, it is important to define clear rules. If some people work with the Block Editor and others with the Classic Editor, display or editing problems may occur with more complex content.

Recommendations for teams:

• Define which editor is used for new content.
• Avoid constantly switching back and forth on the same page.
• Use the Classic Editor mainly for simple text posts.
• Use the Block Editor for layout-heavy content and landing pages.
• Document editorial workflows.
• Briefly train users so content is not accidentally formatted differently.

A clear workflow is more important than the question of which editor is “better”.

4. Effects on existing content

Existing content generally remains intact when installing the Classic Editor plugin. The plugin does not automatically change your posts or pages. It mainly changes the editing interface.

Nevertheless, you should be careful if content has already been created with the Block Editor. Block content may be displayed differently in the Classic Editor or appear as HTML or block comments.

Check especially:

• Were existing pages built with Gutenberg blocks?
• Do pages contain columns, cover blocks, buttons or reusable blocks?
• Is a block theme or Full Site Editing being used?
• Were page builders or shortcodes used?
• Are there individual layouts that depend on the Block Editor?

5. Create a backup before switching

Activating the Classic Editor is usually straightforward. Nevertheless, a backup is advisable, especially if your website already contains many contents, custom layouts or business-critical pages.

A backup protects you if unexpected problems occur after the switch. Back up both files and database.

• Guide: Managing backups with Softaculous

After the backup, you can install and activate the plugin and then test-open some important posts and pages.

6. Classic Editor and block content

If you open a post created with blocks in the Classic Editor, the display depends on the content. Simple text blocks can usually be displayed without problems. More complex blocks, however, may appear as HTML, shortcodes or technical block markers.

You should be especially careful with:

• column layouts,
• cover blocks,
• group blocks,
• reusable blocks,
• block patterns,
• buttons and call-to-action blocks,
• block-based forms,
• Full Site Editing templates.

If such content is important, it should preferably continue to be edited with the Block Editor.

7. Classic Editor and page builders

Many websites use page builders such as Elementor, Divi, Beaver Builder or WPBakery. In such setups, the editing interface depends not only on WordPress itself, but also on the page builder.

The Classic Editor can be helpful for some page builder workflows because older builders were originally developed for the classic editing screen. Modern page builders, however, often work independently of it.

Check:

• Which page builder is being used?
• Does the builder require the classic editor?
• Are there official recommendations from the builder provider?
• Are contents stored as shortcodes?
• Does editing remain stable after activating the Classic Editor?

For page builder websites, you should test editor changes particularly carefully.

8. Classic Editor and widgets

The Classic Editor plugin primarily restores the classic post and page editor. It is not automatically the same as classic widgets. WordPress has also modernised the widget area and made it block-based.

If you additionally want the previous widget interface back, there are separate solutions such as the official Classic Widgets plugin. However, check carefully whether you really need it.

For many modern themes, the block-based widget editor makes sense. With older themes or familiar workflows, however, classic widgets can be more practical.

9. Advantages of the Classic Editor

The Classic Editor can have clear advantages in certain situations.

• Familiar interface: Especially pleasant for long-time WordPress users.
• Fast text editing: Ideal for simple posts without complex layouts.
• Less visual complexity: The interface feels more streamlined.
• Compatibility: Helpful with old plugins or meta boxes.
• Team stability: Existing editorial workflows do not have to be changed immediately.

For pure text articles, short news items or simple blog posts, the Classic Editor remains a pragmatic solution.

10. Disadvantages and limitations of the Classic Editor

The Classic Editor also has clear limitations. WordPress continues to develop many new functions around the Block Editor, block themes and Site Editor.

Possible disadvantages:

• less flexible for modern layouts,
• no native block-based design,
• limited usefulness with block themes,
• possible conflicts with block-based content,
• less future-oriented in the long term,
• less suitable for landing pages and complex designs.

The Classic Editor is therefore particularly useful for existing workflows, but not always the best choice for new WordPress projects.

11. Security and maintenance

The Classic Editor is an official WordPress plugin. Nevertheless, as with every plugin: keep it up to date. Install only trustworthy plugins from official sources and remove alternatives you do not need.

Check regularly:

• Is the plugin up to date?
• Is it compatible with your WordPress version?
• Is it really needed?
• Are there conflicts with the theme, page builder or other plugins?
• Are unnecessary editor plugins disabled?

Every additional plugin should serve a clear purpose.

12. Backend performance

The Classic Editor can feel leaner and more direct in the backend for some users, especially with simple text posts. However, this does not automatically mean that every website becomes faster as a result.

The speed in the WordPress admin area depends on several factors:

• hosting performance,
• PHP version,
• number and quality of plugins,
• database size,
• theme and page builder,
• browser and internet connection,
• external API calls in the backend.

If the backend is slow, the editor should not be the only factor considered. Often, plugins, external services or an outdated PHP version are the actual cause.

13. SEO: Does the editor affect rankings?

The editor used is not a direct ranking factor. Search engines do not evaluate whether a post was created with the Classic Editor or the Block Editor. The published content is decisive.

SEO-relevant factors are primarily:

• helpful content,
• clear heading structure,
• clean URLs,
• meaningful internal linking,
• fast loading times,
• mobile display,
• structured data, where appropriate,
• good metadata,
• optimised images.

What matters is that your editor workflow enables good content and does not create faulty layouts or broken HTML structures.

14. GEO: Maintain content clearly and structurally

GEO, meaning Generative Engine Optimization, concerns the comprehensibility of your content for AI-supported search and answer systems. The editor itself is less important than the structure and quality of the content.

Regardless of the editor, pay attention to:

• clear headings,
• direct answers to important questions,
• clean paragraphs,
• understandable language,
• up-to-date information,
• internal links to related topics,
• FAQ sections where suitable.

The Classic Editor can be sufficient for this as long as content is well structured and published in a technically clean way.

15. Common mistakes when switching to the Classic Editor

• No backup created: For complex pages, there is no fallback option.
• Block pages saved carelessly: Layouts can be damaged.
• Wrong plugin installed: An unknown alternative is chosen instead of the official plugin.
• Team not informed: Users work differently and create inconsistent content.
• Page builder not tested: Existing layouts behave differently than expected.
• Classic Editor confused with Classic Widgets: Both affect different areas.
• No long-term planning: New WordPress functions are ignored.

Recommended procedure

1. Check need: Why do you want to use the Classic Editor?
2. Create backup: Especially for existing websites with lots of content.
3. Install official plugin: Search for Classic Editor under Plugins > Add New.
4. Activate plugin: Then check settings under Settings > Writing.
5. Choose default editor: Set Classic Editor or Block Editor.
6. Allow or disable editor switching: Decide depending on team structure.
7. Test important content: Check posts, pages, page builder content and forms.
8. Inform team: Define clear editing rules.
9. Keep plugin up to date: Install updates regularly.
10. Review Block Editor long term: Plan it for new projects and modern layouts.

Frequently asked questions about the Classic Editor

What is the Classic Editor in WordPress?

The Classic Editor is the former editing view of WordPress. It offers a classic text field with a toolbar and is more reminiscent of a simple word processor.

Is the Classic Editor plugin official?

Yes. The Classic Editor plugin is an official WordPress plugin maintained by the WordPress team and restores the former editing view.

Will my content remain intact when switching?

Generally yes. The plugin does not automatically change your content. However, with complex block content, you should be careful and create a backup before switching.

Can I switch between Classic Editor and Block Editor?

Yes, depending on the setting. Under Settings > Writing, you can define whether users may switch between both editors.

Is the Classic Editor better than Gutenberg?

Not generally. The Classic Editor is simpler and more familiar for classic text editing. Gutenberg is more modern and better suited for flexible layouts, blocks and new WordPress functions.

Does the Classic Editor work with page builders?

Often yes, especially with older page builder workflows. Nevertheless, you should test your specific website, as page builders work differently.

Does the Classic Editor improve my SEO?

No, not directly. SEO depends on the published content, structure, loading time, internal linking and technical quality of your website – not on the editor alone.

Should I stay with the Classic Editor long term?

If your website runs stably and simple content is maintained, this can make sense. For new projects and modern layouts, however, you should at least know and test the Block Editor.