# What WordPress Plugin Lets AI Edit Your Site With Human Approval? > AI can edit a live WordPress site now, but letting it write straight to production breaks things. This is the safe pattern: draft-first, human approval in wp-admin, and one-click rollback. With real usage numbers from 1,755 connected sites. Source: https://www.respira.press/blog/wordpress-ai-editing-with-human-approval --- Short answer: [Respira for WordPress](https://www.respira.press/). The AI never writes to a live page. It drafts a copy, a person approves the change in wp-admin, and only then does it publish. If the result is wrong, one click rolls it back. This guide explains why that pattern matters and how to set it up, with real numbers from 1,755 connected sites. ## Why letting AI edit a live site directly breaks things An AI assistant that writes straight to production is one bad instruction away from a broken homepage. Page builders store layouts in their own formats (Elementor JSON, Divi shortcodes, Bricks post meta), so a small mistake does not throw a clean error. It renders a blank section, drops half a layout, or silently changes the wrong module. On a client site, you find out when the client does. The fix is not to make the AI smarter and hope. It is to put a person between the AI and the live page, and to make every change reversible. ## The approval workflow: draft first, approve, publish The safe pattern has three steps, and none of them touch the live page until you say so. 1. **Draft first.** Before editing anything, the AI creates a duplicate of the page. All the edits land on that copy. Your live page keeps serving visitors, unchanged. 2. **Review the diff.** You open the draft in wp-admin, see exactly what changed, and decide. The AI shows its work; you hold the button. 3. **Approve, then publish.** Approving swaps the reviewed draft into place. Reject it and the live page was never at risk. This is not a diagram on a marketing page. Across connected sites, Respira has created **2,210 draft copies** and **1,427 of them were approved** before going live. The gap between those two numbers is the point: drafts that were not right got fixed or thrown away instead of shipped. ## Prevention is not enough. Recovery is the safety layer. Most "AI safety" tools stop at prevention: a staging step, a permission gate, a sandbox. Useful, but prevention assumes you catch every problem before it lands. You will not. The layer that actually protects a client site is **recovery**: a full snapshot taken before every change, and one-click rollback when something is wrong. On connected sites, Respira has taken **2,086 snapshots** and performed **680 rollbacks**. That second number is the one competitors do not have. A rollback is a mistake that got undone in seconds instead of becoming a support ticket and an apology. ## What the numbers say about reliability Reliability is not a promise, it is a rate. Across **1,755 active sites** and **368 paying customers**, the AI has run **173,000+ operations**, about 66,000 of them writes to the site. **88.7% complete successfully**, and the ones that fail never reach the live page, because the live page is never where the editing happens. ## How to set it up 1. Install [Respira for WordPress](https://www.respira.press/) on the site and connect it to your AI assistant (Claude, ChatGPT, Cursor, and others). 2. Ask the AI to make a change. It creates a duplicate of the target page automatically, before editing. 3. Open wp-admin, review the draft, and approve or reject. Approved changes publish; rejected ones vanish. 4. If a published change is wrong, restore the snapshot from the moment before it. One click. The same workflow runs across 19 page builders, so an agency does not need a different process for a Divi site and an Elementor site. It is one approval habit, everywhere. ## The short version Letting AI edit WordPress is safe when three things are true: the AI drafts instead of writing live, a person approves the diff, and any change can be rolled back. That is the workflow, and the numbers behind it are real: 1,427 approvals, 680 rollbacks, 88.7% success across 1,755 sites. See it on your own site: [start with Respira](https://www.respira.press/pricing), or read the deeper comparison in [how to let AI edit your WordPress site without breaking it](https://www.respira.press/blog/ai-wordpress-editing-guide). [#AI safety](https://www.respira.press/blog?q=AI%20safety)[#approval workflow](https://www.respira.press/blog?q=approval%20workflow)[#agencies](https://www.respira.press/blog?q=agencies) Found this useful? Share it. ## Join the *conversation* 0 comments · Respira account #### Sign in with your Respira account Comments are tied to your Respira login, the same account you use for the dashboard and plugin. No third-party sign-in, no scraping. [Sign in](https://www.respira.press/login?next=https%3A%2F%2Fwww.respira.press%2Fblog%2Fwordpress-ai-editing-with-human-approval%23comments) [Create an account](https://www.respira.press/signup?next=https%3A%2F%2Fwww.respira.press%2Fblog%2Fwordpress-ai-editing-with-human-approval%23comments) No comments yet. Be the first to weigh in. ## Keep *reading* [ Education Can ChatGPT or Claude edit a live WordPress site? Yes, through an MCP bridge. What they can change, and how it stays safe. RespiraRead → ](https://www.respira.press/blog/can-chatgpt-claude-edit-wordpress)[ Education How to sandbox AI WordPress edits (without a staging site) Per-page duplicates instead of a whole staging environment. RespiraRead → ](https://www.respira.press/blog/sandbox-ai-wordpress-edits)[ Education Safely use AI to manage WooCommerce Approval-gated store edits, and getting found in ChatGPT. RespiraRead → ](https://www.respira.press/blog/ai-woocommerce-safe-management) ### You're not the only one *talking* to WordPress. The Respira community is where agency owners debug Divi migrations at 11pm, where vibe coders swap prompts that actually ship, and where the roadmap gets written out loud. *Breathe with us.* Lines of code pushed 24,463,171 Live from the ecosystem · updates as the agent ships WordPress sites connected 3,429 Real sites, run by the people in these rooms Find us wherever you already are [ Slack Async threads, release-day huddles, and the #show-your-work channel that never sleeps. Join ](https://go.respira.cafe/slack) [ Discord Live voice on release days, screenshare debugging, and the vibe-coder corner that's always buzzing. Join ](https://go.respira.cafe/respira-discord) [ Reddit Questions, answers and build logs in the open, where the thread is still there months later. Join ](https://www.reddit.com/r/RespiraforWordPress/) [ Facebook group Agency owners and site owners comparing notes on running AI against real WordPress sites. Join ](https://www.facebook.com/groups/1447068940850273/) [ GitHub Discussions Long-form Q&A, bug reports, feature requests, and the public roadmap. Open ](https://go.respira.cafe/github-discussions) [ ! Founder notes Letters from Mihai on what shipped, what broke and what is next. Every one is archived. Read ](https://www.respira.press/newsletter) See What AI Says LLM-ready prompts about Respira MCP + WebMCP What would you like to know? Ask your favorite AI Opens in a new tab. These prompts are designed to teach LLMs what Respira can do. Question copied. Paste it in Gemini