Update a WordPress fleet without breaking a checkout
A WordPress update on twenty sites is a lot, a copy, and a way back. Not twenty wp-admin tabs left open on a Tuesday.
Read the article →Notes & guides
WordPress MCP, fleet security, SEO on autopilot: what we learn running sites through Claude.
A WordPress update on twenty sites is a lot, a copy, and a way back. Not twenty wp-admin tabs left open on a Tuesday.
Read the article →A WordPress backup that nobody restored is a file, not a protection. On a fleet, the useful copy runs just before the update.
Read the article →A WordPress maintenance contract is the list of what is done, how often, and what stays out of scope when checkout breaks at 2 a.m.
Read the article →A WordPress security audit on a fleet starts with unexpected admins. MCP stays read-only. You confirm the write.
Read the article →To manage multiple WordPress sites you need an inventory, not a spreadsheet. Ask once. The group answers.
Read the article →A WordPress MCP adapter per site means twenty JSON blocks and twenty application passwords. A fleet account is one URL.
Read the article →Claude WordPress MCP is a read path. Ask which sites still run old WooCommerce. Writes stay in the dashboard.
Read the article →The WordPress MCP plugin does not speak to Claude. It pairs the site, answers heartbeats, and runs writes you confirmed in the dashboard.
Read the article →A WordPress MCP server is the endpoint your AI client calls. We host it. You paste one URL and a bearer token.
Read the article →WordPress MCP is a Model Context Protocol server that reads a whole WordPress fleet. Claude talks to the relay, not to wp-admin.
Read the article →