Launch offer
20% off every Pro tier — and every renewal — for a limited time. Use the code at checkout:
SiteHelm connects your WordPress site to Claude and gives it 115 real jobs it can do — pages, images, menus, Elementor layouts, SEO, WooCommerce. You describe the change. It makes it, shows you what it did, and puts it back if you don’t like it.
Free, open source, and no account to create. You don’t need a developer, and you don’t need to know what any of it is called.
Ask for a change and nothing changes yet. The preview comes back with the exact field-level before and after, plus a single-use plan token. Applying means re-sending the same arguments with that token, so a change you did not read cannot slip through.
Once it has run, the site is read again — not the return value of the write, the site itself, freshly queried — and what persisted is compared against what was promised. Most tools report what they sent. SiteHelm reports what actually landed, and says so when a theme or another plugin quietly altered it.
The old state is kept before the write, not after it. That snapshot is what rollback restores from.
Illustrative. Nothing is written until this exact plan is re-sent with its token.
Rollback restores from the snapshot taken before the write. Not a re-edit, and not an undo stack the agent controls — the state that existed a moment earlier, returned by you from the console.
Six tabs in wp-admin do the human half of the job: Home, Connect an app, History, Health, Permissions and Tools, with rollback, a write pause, and credential revoke reachable in one click. Per-operation and per-module switches mean you hand over exactly as much as you meant to, and no more.
Permission comes from the authenticating WordPress user’s own capabilities, and every handler re-checks them itself. If you can’t do it in wp-admin, neither can the agent. A refusal is a first-class outcome with a reason and a remedy, logged in the same register as a success — never a stack trace, a file path, or a SQL string.
Synthetic rows, shown to illustrate the log’s shape.
Start with the hardest one. Elementor keeps a whole page as a single serialised tree — the reason a page builder is the one part of your site you cannot sensibly edit by hand, and the reason most tools stop at the page title.
SiteHelm reads and writes that tree: 37 operations covering documents and elements, individual widget settings, global colour and typography tokens, and theme-builder display conditions. Ask for a new section, a different heading, a swapped image, a colour that runs across the whole site — and every one of them re-serialises from a snapshot of the entire document, so rollback returns the page, not a half-repaired widget.
Same for the rest of the builder-adjacent work most owners pay for by the hour: custom fields in ACF and Meta Box, menus, media, titles and descriptions in whichever SEO plugin you already run.
Added into an existing layout, in place, at the position you name.
Read against Elementor’s own live control schema, never a guessed list of keys.
The tokens the whole site inherits, changed once instead of widget by widget.
The snapshot is the entire tree, so putting it back cannot leave a page half-written.
And 11 modules in all, across 11 areas of the site. Rewrite a page, swap a hero image, reorder a menu, fix your titles and descriptions, moderate a comment, update a product — each one a job you can ask for by name.
Requires PHP 8.1 or newer and WordPress 6.6 or newer. Elementor, ACF, Meta Box, an SEO plugin and WooCommerce are all optional — SiteHelm reports which of them it found rather than requiring any.
Posts, pages, custom post types, blocks, terms and redirects — the operations an editor would otherwise perform by hand.
The library: attachment details, uploads, alt text and captions, and import from a URL behind a guarded fetch.
Navigation menus, their items, their order, and which theme location each one is assigned to.
Documents and elements, widget settings, global colour and typography tokens, and theme-builder display conditions.
ACF and Meta Box field groups, their fields, and their values — read and written through each plugin’s own API.
Titles, descriptions and robots directives, read and written through whichever SEO plugin the site already runs — one post at a time, or fifty under a single preview.
The moderation queue: list by status, approve, hold, spam or trash, and reply beneath a comment.
Read only: which forms the site holds, each form’s fields and embed shortcode, and its most recent entries.
The roster, and one write: replacing a user’s roles with a single role the site has actually registered.
Thirteen fields, allowlisted: title, tagline, timezone, date and time formats, posts per page, front-page geometry, permalinks, default discussion settings, and search-engine visibility.
What the site runs: every installed plugin and theme, its version, whether it is active, and whether an update is waiting.
Everything above this line — the two-phase write, read-back verification, the capability model, the activity log, rollback and the write pause — is in the free plugin, and it is the complete product, not a sampler. Nothing about safety sits behind the paywall.
Pro adds reach, not safety: 51 further operations for site-wide SEO settings, schema, WooCommerce products and plugin management. Every one of them inherits the same preview, snapshot, verification and rollback.
Nothing free moves into Pro later, and a lapsed licence stops the Pro operations without stopping anything else — your site keeps working, and so does everything the free plugin does.
The tier is how many sites the licence activates on. Every tier gets every Pro operation — there is no feature held back for the expensive one.
The prices below are what checkout charges — and for a limited time, code LAUNCH20 takes a further 20% off the first payment and every renewal. What every licence carries.
Single site
1 site. Your own site, or one you look after.
5 sites
Up to 5 sites. A small book of client work.
Unlimited
Every site you run. An agency, or a freelancer with a full roster.
Unlimited, monthly
Every site you run. The same unlimited licence, paid month to month.
The free plugin is developed in public — source, tests and operation reference all live in one repository, and the roadmap is built from public, votable requests. If you run it on a host, a theme or a plugin combination nobody has tried yet, you already have something worth contributing.
An approved contribution earns a free Pro licence — from one month for a reproducible bug report up to 12 months for the biggest bands. A maintainer reads every contribution and decides the band; keep contributing and the licence keeps renewing.
A reproducible bug report is a contribution — the most valuable kind comes from a setup nobody has tried yet.
Pull requests against the public repository, test included. CONTRIBUTING.md has the full standard.
Requests are public and votable, and the votes are read. The roadmap is built from them.
An ordinary WordPress plugin. Nothing to configure first.
It carries you through the whole handshake. You do not need to know what MCP, JSON-RPC, or an application password is.
Claude, Claude Code, Cursor, VS Code, or any other MCP client. The agent discovers what it is allowed to do at runtime.
Where SiteHelm and the open-shell tools genuinely differ, and which of them fits what you are actually doing.
comparisonIncluding the ones where the honest answer is no.
FAQYearly for one, five or unlimited sites — or monthly — every tier with every Pro operation.
pricing