Yes, AI can now edit a WordPress site directly. Modern AI assistants can connect through the WordPress REST API, through WP-CLI on a copy of the site, or through the newer MCP connections built into recent WordPress versions, and then update pages, products, settings, and code. It’s fast and genuinely useful, but it’s only safe with guardrails: work on a copy or draft first, back up before every change, limit each change to one page or field, and have a person verify the result before it goes live.
At Penner Web Design we use this every week on client sites. Here’s what it looks like in practice, and what we do to make sure it never costs a client their website.
How AI connects to WordPress
There are a few ways an AI assistant can reach inside a WordPress site. Each has a different level of risk.
- The WordPress REST API. WordPress has a built-in API that lets approved software read and update content. With an application password (a separate, revocable password just for this purpose), an AI tool can pull a page, change it, and push it back.
- WP-CLI on a local copy. WP-CLI is WordPress’s command-line tool. We pull a full copy of a site onto our own computer, and the AI works there with complete access to the files and database, with zero risk to the live site.
- MCP and the Abilities API. Newer WordPress versions include the building blocks for the Model Context Protocol, a standard way for AI assistants to discover what a site can do and take actions. Some plugins now ship MCP support, sometimes without the site owner realizing it.
- Browser automation. An AI can also drive a web browser and click through wp-admin like a person would. It’s slower and more fragile, so we use it mostly for checking results, not making changes.
What AI is great at on a WordPress site
- Writing unique page titles and meta descriptions for every page on a site.
- Adding descriptive alt text to hundreds of images.
- Adding structured data (schema) so search engines and AI understand the business.
- Converting old plugin tables, shortcodes, and page-builder leftovers into native blocks the client can edit.
- Auditing every page for a problem, like inconsistent mobile spacing or broken links, instead of spot-checking a few.
- Reading error logs and plugin code to find the cause of a crash.
Where it goes wrong
AI is confident even when it’s wrong, and WordPress is full of small traps. A few we’ve seen firsthand:
- Invisible corruption. WordPress page layouts store settings as code inside the page content. An automated edit that handles that code slightly wrong can strip characters and break a layout, and the page might look fine in one place and broken in another.
- “Attempt block recovery” errors. If AI-generated content doesn’t match exactly what the WordPress editor expects, the editor flags the block as invalid the next time someone opens the page.
- Caching surprises. On a store running a caching plugin, changes can look finished when the cache is still serving the old version, or worse, a cache setting can serve private data to the wrong visitor.
- Overreach. Ask an AI to fix one thing and it may “helpfully” rewrite three others.
Our rules for letting AI touch a client site
- Work on a local copy or a draft first. Live sites are the last step, never the first.
- Back up before every change: the database for big jobs, the individual page for small ones.
- Keep each change narrow: one page, one field, one setting at a time.
- Verify every change with our own eyes, in the editor and on the front end, on desktop and phone.
- Purge caches and check again as a logged-out visitor.
- Keep passwords in the computer’s secure keychain, never in files, chats, or scripts.
- A person approves anything that goes live. That’s me.
These rules exist because of real mistakes, not theory. The one time an automated edit broke a page layout on our watch, the backup from step 2 had it restored in minutes, and step 4 got stricter.
What to ask your web person
If someone is using AI on your website, and more of them are than will say so, it’s fair to ask:
- Do you test changes on a copy of my site before the live one?
- Do you back up before AI makes changes?
- Who reviews the changes, and how?
- Where are my passwords stored?
- If something breaks, how fast can you roll it back?
Good answers to those questions matter much more than whether AI is involved at all.
Frequently Asked Questions
Yes, if they are connected to it. AI assistants can edit WordPress through the REST API with an application password, through WP-CLI on a copy of the site, or through MCP connections in newer WordPress versions. They cannot change your site unless someone gives them access.
It is safe with guardrails: use a separate, revocable application password, work on a staging copy or draft first, back up before changes, and have a person verify every change. Giving an AI tool your admin password and letting it edit the live site unsupervised is not safe.
MCP (Model Context Protocol) is a standard that lets AI assistants discover and use a website’s capabilities. WordPress has been adding support through the Abilities API and an MCP adapter, and some plugins bundle it. If you do not use AI tools with your site, you can leave it inactive.
AI replaces some of the repetitive work, not the judgment. Someone still has to decide what should change, catch the mistakes AI makes, and take responsibility when something breaks. The best results come from an experienced person using AI well.
Need a hand with your WordPress site?
Penner Web Design is a WordPress studio in Durham, NC, and we use AI carefully to make updates, fixes, and maintenance faster and more affordable. See our WordPress maintenance and security plans, read how I use AI in my business, or send us a note about what you need.
