Goldnat Plugins
← Back to documentation home

Managing Many WordPress Sites with an AI Agent

A practical guide for agencies and freelancers who look after several WordPress sites — how to connect one AI agent to all of them with the Goldnat plugins, what it can check and change on each site, how permissions and confirmations keep it safe, and a weekly routine you can copy.

📅 Updated: 2026-11-16

More videos on our YouTube channel →

Who this is for

You look after more than one WordPress site — your own, your clients’, or both. Every week the same small jobs come back on every site: check updates, look at Site Health, moderate comments, fix a title, answer “is the shop OK?”. Each job is simple. Doing it across many dashboards is what eats the day.

This guide shows how to hand those jobs to an AI agent (Claude, ChatGPT, goldnat.ai or any MCP client) using the Goldnat plugins for WordPress, while keeping control of what the agent is allowed to do on each site.

It describes what the plugins actually do today. Where something is not possible, it says so.

How it works in one paragraph

Each WordPress site gets the free plugin, Goldnat for WordPress. It turns that site into a tool server for AI agents over the Servio Protocol: the agent reads the site’s manifest, sees which tools exist, and calls them over HTTPS. The agent logs in with OAuth 2.0 + PKCE and acts as the WordPress user who approved the connection — never as a super-user, and never with a shared admin password. Paid add-ons add more tools to the same site (content writing, administration, WooCommerce, Elementor, Rank Math). Your agent then holds one connection per site, and you talk to all of them from one conversation.

The important consequence: the plugins work per site. There is no hidden “control centre” that reaches into your sites. The “many sites” part comes from your agent holding several connections at once — see Step 2.

Step 1 — Install the free plugin on every site

On each site:

  1. In wp-admin go to Plugins → Add New, search the WordPress.org directory for the plugin (directory page: wordpress.org/plugins/goldt-webmcp-bridge), install and activate it.
  2. Make sure permalinks are not set to “Plain” — the manifest is a REST route and needs pretty permalinks.
  3. Use HTTPS. The connection uses OAuth; goldnat.ai requires HTTPS.

Requirements and screenshots are in the WordPress installation guide. The free plugin alone gives the agent 22 read-only tools: search and read posts and pages, list comments, media, menus, categories, tags, taxonomies, post types, users, site info and settings, and “who am I on this site”. It cannot create, change or delete anything — a good way to start with a client site before you give any write access.

Step 2 — Connect every site to one agent

You have two ways to keep many sites in one agent.

Option A: goldnat.ai (hosted, no local setup)

In goldnat.ai you add each site by its address. You are sent to that WordPress site to log in and approve what the agent may do — read only, or read and write. Repeat for each site. goldnat.ai keeps all your site connections in one place and adds granular tool controls and approval of write actions on top of what the plugins enforce.

Option B: any MCP client, with the open-source bridge

If you work in Claude Desktop, Cursor, Cline, Continue.dev, Windsurf, Zed or another MCP stdio client, install the MIT-licensed bridge described on the open-source client page (source: github.com/chgold/webmcp-client). It is configured once in your client and then manages any number of sites without a restart:

  • webmcp_addSite — add or update a site (a name you choose, its manifest URL, and the token you generated on that site, plus a refresh token so it can renew itself).
  • webmcp_listSites — list your sites, their tool counts and auth state.
  • webmcp_removeSite — remove a site and its tools.

Once added, every tool appears under the site name you chose, for example client-bakery/wordpress.listPosts and client-gym/wordpress.listPosts. That prefix is what lets you say “on the bakery site…” and have the agent call the right site. The bridge runs on your machine; tokens live in your local config.

Naming tip: give sites short, unambiguous names (acme-shop, acme-blog, dentist-main). You will type them in every request.

Which WordPress user should approve the connection?

The agent can do exactly what the approving user can do in wp-admin — no more. For each site, decide on purpose:

  • Read-only reporting (status checks, content audits): connect with an Editor or a dedicated low-privilege user, and approve read only.
  • Content work (drafts, comments, media): an Editor-level user with read and write.
  • Administration (updates, plugins, Site Health, roles): an Administrator — only on sites where you really want the agent to do that work.

You can see and revoke every connection from the plugin’s token screen in wp-admin on that site. Revoking takes effect immediately.

Step 3 — Add only the tools each site needs

Add-ons install on top of the free plugin, per site. Buy only what a given site uses.

Add-onWhat it addsTools
Goldnat for WordPress ProCreate, update, schedule, duplicate, trash and restore posts and pages; revisions; comment moderation (approve, spam, reply); media upload and featured images; menus; terms; users; bulk post updates50
Goldnat for WordPress — AdminSite Health, system info, plugin/theme/core/translation updates (with dry run), managed options, roles and capabilities, application passwords, WP-Cron, cache, maintenance mode, PHP error log, database clean-up and trash, WXR export/import, privacy requests, audit log65
Goldnat for WooCommerceProducts, variations, stock, orders, notes, tracking, refunds, coupons, customers, reviews, shipping zones, taxes, webhooks, sales/revenue/low-stock reports84
Goldnat for ElementorRead and edit Elementor pages element by element, global colours and fonts, templates, revisions, custom CSS, widget usage search, CSS regeneration68
Goldnat for WordPress — Rank Math SEOSEO titles/descriptions/focus keywords (one post or many), scores, content analysis, schema, redirections, 404 log, sitemap, robots.txt, llms.txt, site audit and fixes39

Each has plans for a single site or several sites — see the plugin page for the current plans. Other add-ons (Yoast SEO, ACF, forms plugins, The Events Calendar, Easy Digital Downloads, Wordfence, Elementor Pro) are listed on the WordPress page.

A tool that depends on another plugin only works where that plugin is present. For example, the Rank Math add-on needs Rank Math SEO (the free version is enough) on that site.

What a multi-site workflow looks like

Below are requests that map to real tools. The agent picks the tools; you can always ask it “which tools will you use?” before it starts.

Monday morning: status of all sites

“For every site, give me: WordPress version and whether a core update is waiting, how many plugin and theme updates are waiting, and anything Site Health marks as critical. One line per site.”

With the Admin add-on the agent calls wordpress_admin.getCoreUpdateStatus and wordpress_admin.getSiteHealth on each site and merges the answers. On a site with only the free plugin it can still report wordpress.getSiteInfo (name, URL, WordPress version, language, timezone) — and will tell you it has no update or health tools there.

Updates, carefully

“On acme-blog, which plugins have updates? Do a dry run first.”

wordpress_admin.listPlugins shows versions and available updates. wordpress_admin.updatePlugin and wordpress_admin.bulkUpdatePlugins accept dry_run=true to show the current and target versions before anything changes. A real update requires an explicit confirmation. Installing, updating and deleting code is off by default in the Admin add-on until an administrator switches it on for that site, and a site-wide report-only mode turns every update request into a report. Use that mode on client sites where updates must go through your normal change process.

”Why is this site slow since yesterday?”

wordpress_admin.getErrorLog reads the end of the debug log (filterable), wordpress_admin.listCronEvents shows overdue scheduled events, and wordpress_admin.getDatabaseCleanupStats counts revisions, auto-drafts, spam and expired transients. The agent can then suggest wordpress_admin.optimizeDatabase, which shows what would be deleted and runs only after you confirm.

Comment moderation across blogs

“On all three blogs, show me comments waiting for moderation. Approve the real ones, mark obvious spam as spam, and list the ones you’re unsure about.”

With Pro: wordpress.listComments, then wordpress.approveComment, wordpress.spamComment, and wordpress.replyToComment if you want replies. Permanent deletion (wordpress.deleteComment) is a separate destructive tool that needs an explicit confirmation flag; trashing is restorable.

Content: drafts and scheduling

“Write a draft post on dentist-main from these notes, add it to the ‘News’ category and schedule it for Monday 9:00.”

Pro: wordpress.createPost (as a draft), then wordpress.schedulePost. Nothing goes live before the time you set. wordpress.duplicatePage, wordpress.restoreRevision and wordpress.bulkUpdatePosts cover the usual “copy this page”, “roll it back” and “move these 20 posts to another category” jobs.

SEO check-ups

“On each site with Rank Math, list the posts with a weak SEO score and the 404s from this week.”

rankmath.getSeoScores and rankmath.list404Logs. The agent can propose titles and descriptions and save them with rankmath.updateSeoMeta after you agree, and turn a 404 into a redirection with rankmath.redirect404Log. Deleting redirections, schema entries or 404 log entries answers with a preview first.

Shops

“Which products are low on stock in each shop, and what were the top sellers this month?”

WooCommerce add-on: woocommerce.getLowStockReport, woocommerce.getTopSellers, woocommerce.getSalesReport. Order work (woocommerce.updateOrderStatus, woocommerce.setOrderTracking, woocommerce.createRefund) is per shop and runs as the connected user.

Elementor sites

“Which pages on acme-shop still use the old testimonial widget?”

elementor.findWidgetUsage. Edits are element-level (elementor.updateElement), so “change the hero headline” changes that text and nothing else. Global colour and font changes (elementor.updateGlobalColors, elementor.updateGlobalFonts) apply site-wide, so say clearly which site you mean.

A weekly routine you can copy

Paste this to your agent once, then just say “run the weekly check”:

Weekly check for all my WordPress sites. For each site, one short block:

  1. WordPress version and waiting core/plugin/theme/translation updates (dry run only — do not update anything).
  2. Site Health items marked critical.
  3. New PHP errors in the last 7 days (count and the most frequent message).
  4. Comments waiting for moderation (count only).
  5. If WooCommerce is there: low-stock products. If Rank Math is there: new 404s. Say which items you could not check on a site because the tool is not installed there. Do not change anything. At the end, list what you recommend I approve.

The last two instructions matter: they make gaps visible instead of silently skipped, and they keep the routine read-only until you decide.

Safety: what protects your sites

These are enforced by the plugins on each site, whatever agent you use:

  • Real WordPress permissions. Every tool checks the same capability as the matching wp-admin screen and uses WordPress’s own functions. The agent can never see or change more than the user who connected it.
  • Access level chosen at connect time. Read only, or read and write. Revocable at any time from wp-admin.
  • Confirmation before destructive actions. Deleting, switching themes, erasing personal data, updating code and similar actions require an explicit confirmation; many support a dry run.
  • Guard rails in the Admin add-on. The agent cannot deactivate or delete the plugins it is connected through, cannot delete the active theme, cannot strip the administrator role, and cannot remove WordPress core scheduled tasks without an explicit force. Privacy erasure runs only after the person confirmed by e-mail.
  • Audit log. The Admin add-on writes each action that changes the site to an audit log (who asked, what, outcome) that no tool can edit or clear; read it with wordpress_admin.getAdminAuditLog.
  • Tokens you can see. The token screen shows when each connection was created and last used, from which IP and which client, with immediate revoke.
  • Your content stays on your site. The plugins answer the agent’s requests directly; they do not copy your site anywhere. What the agent sends to its AI model is up to the agent you choose.

More detail: Security guide.

Practical rules for agencies

  • Start every new client site read only for a week. Add write access when you know what you want the agent to do there.
  • Keep code updates behind the Admin add-on’s report-only mode on sites with a change-approval process.
  • Use one WordPress user per person or per agent, not a shared admin account — the audit log and token list are only useful if they name the right person.
  • When a client relationship ends, revoke the tokens on that site and remove it from your agent (webmcp_removeSite, or remove it in goldnat.ai).

What it does not do (today)

  • No cross-site bulk tool. “Update all plugins on all 30 sites” is the agent calling each site in turn, with the confirmations each site requires — not one command that fans out on its own.
  • No WordPress Multisite network administration. The tools work within one site. wordpress_admin.listPlugins reports network-active plugins, but there is no tool for managing a network’s sites.
  • No backups. None of the tools create or restore backups. Keep your existing backup solution and take a backup before large changes.
  • No scheduler of its own. The plugins answer requests; they do not run your weekly check by themselves. Running a routine on a schedule is up to your agent or your own automation.
  • Add-ons are per site. A tool exists only on sites where its add-on (and, where relevant, the plugin it works with) is installed.

Bonus: an assistant for your clients’ visitors

The AI Assistant for WordPress is a different product: it puts commands in front of visitors — summarise a post and its comments, ask the site, translate a post, find related posts, what’s new, and with WooCommerce “ask about this product” and “ask about my orders”. It runs on the site owner’s own AI provider key and reads content as the visitor who clicked, so drafts, private posts and other customers’ orders never reach the answer. It is not a site-management tool, but on client sites with a lot of content it is often the next thing clients ask for.

Next steps

  1. Install the free plugin on one site and connect it: installation guide.
  2. Add a second site in your agent and run the read-only weekly check above.
  3. Add the add-on that matches the work you do most: all WordPress plugins.

Questions: contact us.

This page is informational and non-binding. It describes the general design of the AI Connect plugins; actual behavior can vary between platforms and plugin versions. For the binding terms, see the Terms & Conditions.