How to Manage Multiple WordPress Sites with AI (Claude, ChatGPT or Any AI IDE)

Watch the video tutorial

The video runs a little under 10 minutes. The written guide below covers the same steps, plus a few details that are easier to read than to watch.

What "managing sites with AI" actually means

An AI chat on its own can't touch your website. It can only talk. To let it read and change a WordPress site, you need a bridge between the two. That bridge is usually the Model Context Protocol (MCP), an open standard that lets AI apps call tools on other systems.

GoBuildWP is a WordPress plugin that turns your site into an MCP server. It gives the AI a list of clear, typed actions it is allowed to take, such as "list plugin updates" or "edit this heading". WordPress calls these actions abilities, after the Abilities API that arrived in WordPress 6.9. You can read more about that foundation on our WordPress Abilities API page.

The AI doesn't get your password, and it doesn't click around wp-admin. It calls those abilities, one at a time, and every change it makes is logged.

One more thing before we start: this is not the same as WordPress Multisite. Multisite is one WordPress install that runs a network of sites. This guide is about separate WordPress sites, each with its own install, host and admin, which is how most freelancers and agencies work.

What you need

• Two or more WordPress sites where you are an administrator.
• The free GoBuildWP plugin on each site. You can download the latest version or install it from WordPress admin.
• An AI app that supports MCP connectors. Claude and ChatGPT both do, and so do code editors like Cursor, VS Code, Windsurf and Claude Code.
• A free GoBuildWP Cloud account, if you want one connection for all your sites.

You don't need to write code, set up a server or edit any config files.

Three ways to connect your sites

GoBuildWP gives you three routes. Pick the one that fits how many sites you have and where you like to work.

GoBuildWP has ready-made setups for 27 AI apps, so you rarely have to work anything out yourself. If you manage more than one site, Cloud is the easiest route. That's what we use in the video and in the rest of this guide. For a single site, the connect an AI client guide covers the direct route.

Step 1: Connect each site to GoBuildWP Cloud

On your first site, install and activate the free GoBuildWP plugin. Open GoBuildWP in the WordPress menu, go to Connect a client, and choose Connect to GoBuildWP Cloud.

You're sent to Cloud, which asks you to approve the site. Give it a name you'll recognise, then choose how much your AI may do on this site:

• Read only: the AI can look things up and run audits, but it can't change anything. This is a good start for a client site you're nervous about.
• Production safe: the AI can make everyday edits, while risky actions stay blocked or need a confirmation, and every change can be undone.

Click approve, and you're sent back to WordPress, which confirms the site is connected. Repeat this on your other sites. Each site keeps its own safety profile, so a busy shop can stay on read only while your own blog is open for edits. The safety profiles guide explains each level in detail.

The free Cloud plan connects three sites for one person, at no cost and with no card.

Once your sites are in, the Cloud Sites list shows each one with its WordPress version, plugin version, pending updates and last backup.

In our video, two of the three are real client sites, so their names are blurred. All changes in this guide ran on the third one, our demo site.

Step 2: Add one connector to Claude or ChatGPT

Now you connect your AI app. You only do this once, however many sites you add later.

1. In Cloud, open Connect your AI, choose Claude, and copy the connector link.
2. In Claude, open your connector settings (Customize, then Connectors) and choose Add custom connector.
3. Name it GoBuildWP, paste the link and click Add.
4. Sign in to Cloud when Claude asks. The GoBuildWP tools then appear in Claude.

Claude's menus move around from time to time, so if the names look different, Anthropic's guide to custom connectors using remote MCP has the current path. In ChatGPT you add the same link as an app. Our ChatGPT setup page and Claude setup page show each screen. The full Cloud walkthrough is in connect AI to GoBuildWP Cloud.

Step 3: Ask which sites need updates

Start a new chat, make sure the GoBuildWP connector is switched on, and ask:

List my WordPress sites and tell me which ones need updates.

Claude reads every connected site and answers in one reply. For each site you get the WordPress and plugin versions and how many plugin, theme and core updates are waiting. In our test it also pointed out details we hadn't asked about, such as an inactive plugin with known security issues that could simply be deleted, and a site whose old GoBuildWP version needed an update before Claude could see its full plugin list.

This is the part that saves the most time. Instead of three logins, you read one answer.

Step 4: Check backups and update readiness

Before you update anything, you want to know you can get back. So the next question is:

When was each site last backed up, and is it ready for a safe update?

Claude answers with a small table: the last backup for each site, whether a restore point exists and whether the site is ready. On our sites, one was ready, and two had no recorded backup. Claude didn't just say "no backup". It explained what to do first on each site, such as creating a backup from that site's own admin before updating.

GoBuildWP reads backups from common backup plugins. If a site has no backup plugin, it says so plainly rather than guessing. That matters later, in the guarded update.

Step 5: Preview, publish and undo a change

Now a change, on the demo site only. Our prompt:

On the demo site only: change the homepage hero heading to "Analytics your whole team can read". Show me a preview before you save it.

Claude didn't touch the live page. It made a draft copy of the homepage, changed the heading there, and showed the live text and the draft text side by side, with a link to preview the draft. It also flagged something useful: the text under the heading still described a workflow tool, not analytics, so the new heading and the old subheading didn't quite match.

The draft looked right, so we told it to publish. Claude wrote the change to the live page and then read the live page back to confirm the new heading was there. A refresh of the real site showed the new heading.

Then we changed our minds and asked:

Undo that change so the homepage is back to the original heading.

Every change GoBuildWP makes is logged, and supported changes can be undone. Claude reversed that exact change, checked that the page matched its saved state from before, and confirmed the original heading, line break included, was back.

If you prefer buttons, you can do the same from the Changes screen in WordPress. Our undo and rollback guide explains what can and can't be reversed.

Step 6: Run an accessibility audit

Checks are a great fit for AI because they don't change anything. Our prompt:

Run an accessibility audit of the demo site's homepage and list the top issues to fix.

Claude ran the audit against the WCAG guidelines and gave the page a score of 97 out of 100. It found one real issue: there was no main landmark or skip link, so keyboard and screen reader users had to move through the whole header to reach the content (WCAG 2.4.1, Bypass Blocks). It explained the fix in plain words.

What we liked most was the honesty. Claude said the audit reads the page's HTML, so some things need a real browser and a person: colour contrast, keyboard use, visible focus and tap target size. It listed those as manual checks instead of pretending they passed. Treat any automated audit the same way. It catches a lot, but not everything.

Step 7: Run a guarded plugin update

Updates are where most site breakages start, so this is the most important task in the video. First we asked a question without changing anything:

Which plugins have updates waiting on the demo site, and is a guarded update safe? Don't run it yet.

Claude listed each update and whether a guarded update was allowed. GoBuildWP Pro itself was held back, because a plugin shouldn't replace itself in the middle of an update. The other two were eligible.

A guarded update is a Pro feature that always runs in the same order:

1. Confirm a recent backup.
2. Save a rollback copy of the plugin.
3. Check key pages before the update.
4. Install the update.
5. Check the same pages again and compare.
6. Roll back automatically if anything broke.

We asked Claude to run a guarded update of FluentCRM. It stopped at step one. The demo site has no backup plugin, so the backup check failed, and nothing on the site changed. Claude didn't skip the step on its own. It explained what failed, said the decision was ours, and listed our options.

This is exactly the behaviour you want on a client site. An AI that quietly works around a failed safety check is worse than no AI at all.

It's a demo site, so we told it to skip the backup check this once and keep the rollback copy and the page checks. FluentCRM then updated. The rollback copy was saved (about 1,180 files), all five key pages loaded the same before and after, and the REST API and admin-ajax both still responded. No rollback was needed. Claude also listed the limits of its own checks, for example that it couldn't read the server's PHP error log.

If you change your mind later, the old version can be restored from the Changes screen. On a real site, set up a backup plugin first so step one passes. Even with rollback copies, a full backup is your real safety net. The WordPress handbook page on backing up WordPress is a good place to start. More on how guarded updates work is on our AI safe updates page.

How you stay in control

Handing an AI the keys to client sites should make you a little nervous. These are the controls that matter:

• Safety profile per site. Read only, production safe or developer. You choose per site, and you can make it stricter at any time.
• Preview before writing. Ask for a preview and the AI drafts a change without touching the live page.
• A change log with undo. Every change is grouped by AI session, with who made it, what changed and undo or redo buttons.
• Conflict checks. If someone edited the same thing after the AI did, GoBuildWP shows the conflict instead of overwriting their work.
• An off switch. Agent access can be switched off in one click in Settings.

Our WordPress MCP security page goes deeper on how connections are signed and limited.

What the free plugin gives you

Everything you saw above, apart from the guarded update, works with the free plugin. Here's the rest of what's inside, in WordPress admin under GoBuildWP:

• Dashboard. Whether agents can act, which AI clients are connected, every change from the last day and anything waiting for approval.
• Settings. Switch agent access on or off, pick a safety profile and choose what context the AI can see about your site.
• Abilities. 236 abilities grouped by area: posts, pages, menus, media, users, plugins and themes, Elementor, blocks, SEO, WooCommerce, diagnostics, files and more. Each group can be switched off on its own.
• Changes. Your history, with undo, redo and conflict checks.
• Memory. Facts the AI should remember about the site, such as brand rules or the target audience.
• Routines. Tasks on a schedule, like a weekly accessibility check.
• Diagnostics and Connection Doctor. Find out why an AI client can't connect.
• Prompts. A library of ready-made briefs across many industries. Ten come free.
• Design. The site's colours, type and spacing, so the AI builds pages that match your brand instead of guessing.
• Skills. Saved instructions the AI can follow, such as a content audit.
• Preview. Any change an agent proposes, shown before it is written, so you can approve it or throw it away.

Plugin updates still appear where you expect them in WordPress. The AI simply sees and runs the same updates through GoBuildWP. The free plugin page lists every module.

What GoBuildWP Pro adds

Pro is for sites where you want the AI to do bigger work. It adds 1,247 abilities on top of the free 236, across 97 plugin integrations in 14 categories. The main additions:

• Approval queue. Hold writes until a person signs off, with a policy per AI client: off, writes only, or destructive actions only.
• Page builders. Full Elementor pages built from a plan, plus global classes, variables, colours, fonts, templates, popups, headers and footers. Pro also works with Bricks, Divi, Breakdance, Oxygen, Beaver Builder, WPBakery and more, and can convert a page from one builder to another.
• Working copies. The AI edits a draft of a live page, you preview it, and it publishes back.
• Guarded updates with backup checks and rollback, as in Step 7.
• Speed. Cache and page speed settings across 26 cache layers.
• Redirects and 404 logs.
• Content fixes with before and after views.
• Custom fields in ACF, Meta Box, Pods and JetEngine.
• Translations, courses, memberships, events, funnels and deeper WooCommerce work.

Pro comes as a licence for 1, 10, 100 or unlimited sites. Our Free vs Pro comparison breaks the abilities down by area, so you can see if the free plugin already covers what you need.

Using ChatGPT, Cursor or VS Code instead

The steps are the same in other apps. You use the same Cloud link; only the place you paste it changes.

• ChatGPT: add the link as an app, then turn it on in a chat.
• Cursor and VS Code: add GoBuildWP as an MCP server. Our Cursor guide and VS Code guide show the exact settings.
• Claude Code, Codex, Windsurf, Gemini and others: pick the app in Cloud's Connect your AI screen and follow its setup.

Developers often like the IDE route because they can ask the AI to check a site while they work on its theme in the same window.

Limits worth knowing

AI site management is useful, but it isn't magic. A few honest limits:

• Backups are still your job. GoBuildWP checks for them and won't skip that step on its own, but it doesn't replace a proper backup plugin or host backups.
• AI can misread a request. That's why previews and undo exist. Use them, especially on client sites.
• Automated audits miss things. Contrast, keyboard use and focus still need a person.
• Some changes can't be undone. A deleted file or an outside service call may not be reversible. The change log marks these clearly.
• Your AI app's limits apply. Plans, connector limits and usage caps come from Claude or ChatGPT, not from GoBuildWP.

If something isn't connecting, the troubleshooting guide and the Connection Doctor in the plugin are the fastest fixes.

A simple weekly routine

Here's a routine that works well for a small set of sites, using only the steps above:

1. Monday: "List my sites and tell me which need updates."
2. Same chat: "Which sites have no backup from the last 24 hours?" Fix those first.
3. Run guarded updates on the sites that are ready, one site at a time.
4. Once a month: "Run an accessibility audit of each homepage and list the top issues."

It takes a few minutes of reading instead of an hour of logging in. If you look after sites for clients, our page for agencies has more ideas.

Wrapping up

To manage multiple WordPress sites with AI, install the free GoBuildWP plugin on each site, connect them to GoBuildWP Cloud and add one connector to Claude, ChatGPT or your code editor. The free Cloud plan covers three sites, with their updates and backups in one place. Then just ask: check updates, change a heading, audit a page or run a guarded update.

Start with read only on the sites you care about most, try a few questions, and open them up once you trust the setup.