JavaScript is off. The country switcher and the demos need it; everything else on this page works.

WebCrew
Start free

Plugins · Content & admin tools

Classic Editor with AI, on every WordPress site you look after

Content and admin tools are the plugins nobody thinks about until one of them breaks the editor or has a published vulnerability across half your sites. WebCrew monitors the site 24/7, matches Classic Editor's installed version against the vulnerability databases, and updates it with a restore point when you say go.

Start free Two ways to connect

Free for one site. Connect it in five minutes. No card.

Classic Editor belongs to its publisher; WebCrew is not affiliated with it.

Classic Editor8M+ active installs · version 1.7.0
Monitoring 24/7uptime from two regions, health scoreIncluded
Vulnerability checkClassic Editor's version matched against the databasesIncluded
UpdatesOn your schedule; restore point first, code difference kept, rolled back when a check failsIncluded
Assistant actions in Classic Editorchanges made for you, logged, one click to undoComing soon

Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc.…

What goes wrong

Three things that go wrong on sites running Classic Editor, and what you see instead

Each card is one conversation: what happened, what WebCrew did, and the moment you stepped in.

We want to move to the block editor, but I have no idea which sites and pages still depend on Classic Editor.

  • WebCrew lists the 14 sites with Classic Editor active and how many pages each one edits with it.
  • You pick three low-risk sites to try first; the setting change waits for your go with a restore point.
  • Two weeks later the log shows no complaints, and you roll the rest.

A migration in steps, per site, with a way back at each one.

The editor broke after an update.

  • Classic Editor update approved, restore point first.
  • Difference kept.
  • Editor blank. Restore: one click.

One click back.

A vulnerability is published; which sites run that version?

  • Advisory for Classic Editor.
  • 7 sites listed.
  • Approved on all seven.

Matched per site, with the fixing version.

What you can ask

Questions and changes about Classic Editor, in plain words

Ask from the WebCrew dashboard, from your own AI tool over MCP, or, as it rolls out, from the assistant inside wp-admin Coming soon. Reading is instant; every change is logged and can be undone in one click first.

  • Which of my sites still use the Classic Editor, and which theme do they run?
  • Switch this site to the block editor for new posts only, and keep existing pages as they are.
  • List the pages that were last edited in the classic editor before we migrate.

Included on every site

What WebCrew does for a site running Classic Editor

Every change WebCrew makes takes a restore point first and can be undone in one click; you choose where it should ask you first. Monitoring reads; every change is logged and waits for a person.

Everything in site management

Uptime 24/7 from two regions

A site that stops answering, or answers with something else, reaches you within minutes with the response it gave.

Security scan and vulnerability match

Core-file integrity, unknown administrators, and Classic Editor's installed version matched against the public vulnerability databases.

Updates with a restore point

On your schedule; restore point first, code difference kept, rolled back when a check fails.

Ask for changes in plain words

The assistant makes the change in Classic Editor, shows you what it did, and keeps a restore point so one click undoes it Coming soon. Your own AI tools connect today over MCP.

Connecting

How to connect a site that runs Classic Editor, and what we recommend

Where the host allows SSH keys, we recommend SSH: every file compared, not only what WordPress reports, and cleanup help when a site is compromised. Where it does not, the connector plugin covers monitoring, updates and Classic Editor's version check in five minutes.

Connector plugin

Upload in wp-admin. No server access needed.
  • 24/7 uptime, health score, versions, administrators
  • Vulnerability matching and updates with a restore point
  • One-click login, DNS and mail settings

Five minutes. Remove the plugin and the site is disconnected.

Recommended

SSH

One key, scoped to the site's user on the server.
  • Everything the connector does
  • File-level integrity checks and faster updates with a full restore point
  • Malware cleanup and staging copies, when a site needs them

Ten minutes. The key is revoked from your dashboard at any time.

How connecting works, step by step

Questions

Before you connect a Classic Editor site

Does WebCrew change content on its own?

No. Every change is a draft that waits for a person.

Can it update Classic Editor safely?

Every update runs on the schedule you set, takes a restore point first and keeps the code difference; if the check afterwards fails, it rolls back on its own. Running the update on a copy first is coming soon.

Does it work with a premium licence?

Yes. Premium plugins update through their own licence; WebCrew shows the pending version and keeps the restore point.

Does it see my drafts and private content?

No. It reads versions, settings and administrators.

Do I have to install anything besides Classic Editor?

One of two things: the WebCrew connector plugin, uploaded in wp-admin like any plugin, or one SSH key for the site's own user. Nothing else changes on the site.

Can I use my own Claude or ChatGPT with a site that runs Classic Editor?

Yes. Connect your tool to WebCrew over MCP and ask about the site from your own chat. Reading is instant; changes are made for you, logged, and undone in one click.

What does it cost for a site running Classic Editor?

The first site is free, for as long as you like. Every site after that is billed per site per day, monthly, for the days it was on. Plugins are never counted.

Is my content or Classic Editor's data used to train anything?

No. Your content is never sold and never used to train a model, by WebCrew or by a provider it uses.

What if Classic Editor is a premium plugin with a licence?

It updates through its own licence. WebCrew shows the pending version, takes the restore point first and keeps the code difference, the same as for any other plugin.

Related

Plugins that often run next to content & admin tools

All plugins in the catalogue

Connect the Classic Editor site now. The first check is done within the hour.

Start free How to connect

Free for one site. No card.

Start free