Awesome Connect
Edit WordPress by prompt.
Ship only what you approve.
Connect your WordPress site to Claude and describe the change you want. Awesome Connect stages it, shows you a preview of your real site with the change applied, and publishes it only when you press approve.
Works with Claude on the web, desktop, and Claude Code. No password or application password is ever shared.
The problem
Letting AI touch a live site is the scary part.
Plenty of tools will now let an AI agent write straight into your WordPress database. That's fine right up until it rewrites the wrong page, mangles a template, or publishes a half-finished draft to every visitor you have. There's no undo on a live site — only an apology and a scramble.
Awesome Connect takes the opposite approach. Nothing an AI proposes touches your live site until a human approves it. Not the content, not the settings, not the theme files. Everything is staged, previewed, and applied as one reviewable batch — or thrown away.
How it works
Prompt, preview, approve.
You describe the change
“Rewrite the homepage hero for our new pricing, add an FAQ section, and tighten the mobile spacing.” Plain language, in Claude — no dashboard to learn.
Claude stages a changeset
Every edit — pages, posts, categories, settings, theme files — goes into one named changeset. Your live site is untouched at this point.
You see the real thing
You get a link that renders your actual site with every change applied, on a real URL you can click around and share with a client. Visitors still see production.
You approve, or you don't
Approve and the whole batch publishes at once. Decline and it evaporates. Change your mind after the fact and one click rolls it back to exactly how it was.
What Claude can change
A real editor, not a chatbot with a text box.
Content, at any scale
Write, rewrite, and restructure posts and pages. Fix a typo on one page or re-tone forty of them. Assign categories and tags, set excerpts, reorder menus.
Theme and templates
Edit the active theme's PHP, CSS, and JavaScript. Every PHP file is syntax-checked before it can even be staged, so a bad edit can't white-screen your site.
Understands your site first
Reads your posts, pages, taxonomies, plugin data, and template files before it proposes anything — so changes match how your site is actually built.
Maintenance, when you allow it
Plugin and theme updates, cache flushes, and health checks through an allowlist you switch on. Off by default.
Platforms
What we connect — and what we don't.
Every platform stages and approves the same way. What differs is how much of a preview it can give you, because that depends on what the platform itself allows.
| Platform | Preview | What Claude can change |
|---|---|---|
| WordPress | Full site preview | Content, theme files, settings, taxonomies. The complete surface. |
| Netlify, Lovable & AI-built sites | Full site preview | Anything in the repository. Changeset is a branch, preview is a deploy preview. |
| Shopify | Full site preview | Theme files preview on the real storefront. Products and pages are diffable, not previewable. |
| Webflow | Full site preview | CMS items, staged then published to your domains on approval. |
| HubSpot CMS | Preview needs a login | Pages and blog posts. Previews need a HubSpot seat. |
| Wix | Preview needs a login | Blog posts only — Wix Editor pages are not reachable by any API. |
| Contentful | Diff only | Entries staged as drafts. Live preview needs your frontend wired up. |
| Sanity | Diff only | Documents staged as drafts. Live preview needs your frontend wired up. |
Platforms we can't connect
We manage sites on these, but they can't support the approval guarantee — so we don't sell you Connect for them.
Framer
Framer's Server API can read and write CMS collections and publish a site, which is everything the approval workflow needs. It is in open beta and is WebSocket-first rather than a conventional REST surface, so it has to be built against a real Framer account rather than from documentation.
Ask us to prioritise it if you have Framer sites — it is a small piece of work once there is an account to build against.
Squarespace
Squarespace publishes no API for reading or writing page content. Its public APIs cover commerce — orders, products, inventory — and nothing that would let a change be staged, previewed, and approved. Developer Mode does expose a site's template as a git repository, but only on 7.0 templates, only on Business plans and above, and enabling it is a one-way door that stops the site receiving template updates. Even then it reaches template code, never content.
Connect is not available for Squarespace. If prompt-driven editing matters to the client, moving the site is the honest answer — and that is a migration we do.
Weebly
Weebly's developer platform has been frozen since Square stopped accepting new developer accounts in 2020. There is no content editing API, the developer documentation is no longer maintained, and the product receives no meaningful feature work.
Connect is not available for Weebly, and the platform's trajectory makes it a poor place to keep a business website regardless. Worth a migration conversation on its own merits.
Security
The guarantees, in plain terms.
No password is shared
Connecting generates a signing key that your site hands to us over a direct server-to-server call. It never passes through a browser, and disconnecting deletes it instantly.
It can't exceed your own permissions
Every request runs as the WordPress administrator who connected the site, so WordPress's own capability checks apply to everything Claude tries to do.
Nothing is deleted permanently
Removing a post moves it to trash. Approving a change snapshots every value it overwrites, so a rollback restores the exact prior state.
Off-limits stays off-limits
Authentication keys and salts can't be read or written, files outside the active theme can't be touched, and database access is read-only, single-statement, and capped.
Every action is logged
A per-site activity log records what was staged, what was approved, by whom, and when — readable from your portal or from WordPress itself.
You can always approve in WordPress
Approval controls live in your own wp-admin as well as our portal, so the safety net never depends on our service being reachable.
Setup
Five minutes, once.
Install the plugin
Download the plugin zip, upload it under Plugins → Add New → Upload Plugin, and activate. It's GPL, and it's the only thing that ever runs on your server.
Press Connect
Under Settings → Awesome Connect, press Connect this site and confirm while signed in to your Awesome Connect account.
Add the connector in Claude
In Claude's connector settings, add a custom connector pointing at ${SITE.url}/mcp. Claude handles the sign-in itself.
Managing sites for clients? We'll do the install and connection for every site on your list as part of onboarding — just ask.
Connect pricing
Priced per connected site.
Solo
billed annually — you get 2 months free
One WordPress site, edited by prompt.
- 1 connected site
- Unlimited changesets
- Full-site change previews
- One-click approve & roll back
- Theme + content editing
- Email support
Studio
billed annually — you get 2 months free
For the freelancer or studio running a handful of client sites.
- 5 connected sites
- Everything in Solo
- Shareable client preview links
- Full activity log per site
- Allowlisted maintenance commands
- Priority support
Agency
billed annually — you get 2 months free
Every client site connected, with approvals your team controls.
- 25 connected sites
- Everything in Studio
- Per-site approval policies
- White-labelled preview links
- Onboarding & migration help
- Same-day response target
Every plan includes unlimited changesets, full previews, approvals, rollback, and the activity log. Already on a Care or Optimize plan? Ask about bundling — Connect is included on Agency-tier care.
Reach out to our team
Talk to a real human about your website.
Tell us what you're running and where it hurts. We'll reply the same business day with a straight answer.