AI for WordPress: The Complete 2026 Guide for Agencies

Every client conversation now has an AI question in it. Can the site write its own product descriptions? Can it answer customer questions? Should we be worried that AI search will stop sending us traffic? For WordPress agencies, 2026 is the year those questions stopped being hypothetical, because AI is no longer something you bolt on with a plugin. Since WordPress 7.0, the foundations are part of core.

This guide is the map. It explains what AI for WordPress actually means today, in plain terms: what ships in core, what sits in optional plugins, how AI agents connect to a site, where AI-written content helps and where it hurts, and which AI services agencies can realistically sell. Each section links to a deeper post as we publish them.

The short version

• WordPress 7.0 (released 20 May 2026) added AI infrastructure to core: an AI Client, an expanded Abilities API and a Connectors screen for AI providers.
• Nothing switches on by itself. AI features are opt-in. A site owner has to connect a provider and enable features before anything calls a model.
• The visible features — title suggestions, excerpts, alt text, image generation — live in the official AI plugin, not in core.
• AI agents (Claude, Cursor, Codex and others) can work on a site through the official MCP Adapter plugin, but only with the abilities a site explicitly exposes.
• For agencies, the opportunity is less “add a chatbot” and more: faster delivery, better content operations, and carefully scoped AI features where they pay for themselves.

Layer 1: what is now in WordPress core

Core does not ship a chatbot or an AI writer. It ships plumbing, which is the right decision for a platform that runs a large share of the web. There are three pieces worth understanding.

The AI Client

The AI Client is a provider-agnostic interface that lets plugins ask a generative model to do something without caring which company’s model answers. Before 7.0, every AI plugin shipped its own API integration, its own settings screen and its own way of storing keys. Now a plugin can describe what it needs and WordPress routes the request to whichever provider the site owner has configured.

For agencies that matters in two ways. Custom functionality you build for a client is no longer tied to one AI vendor, and a client can switch provider later without a rebuild. And you stop managing five different API keys across five plugins.

Connectors

Connectors is where a site administrator authenticates AI providers, found under Settings → Connectors. Anthropic, Google and OpenAI are supported out of the box, and the whole thing is opt-in. This is also the screen that answers the client question “is our site sending data to AI companies?” — if nothing is connected, the answer is no.

The Abilities API

The Abilities API arrived in WordPress 6.9 and was expanded in 7.0. It gives plugins and core a standard way to describe what they can do — “create a post”, “update a product price”, “list form submissions” — in a format that AI systems can read and call. Think of it as a menu of actions a site offers, with permissions attached to each item.

It sounds abstract, but it is the piece with the longest tail. Once your custom plugins register abilities properly, they become usable by AI features inside WordPress and by external agents, without separate integration work for each.

Layer 2: the features editors actually see

The user-facing features live in the official AI plugin from the WordPress AI team, developed in the open at make.wordpress.org/ai. At the time of writing it offers title suggestions, excerpt generation, alt text generation, and image and featured image generation inside the block editor. All of them use whichever provider is connected through Connectors.

Our view on these for client sites:

• Alt text generation is the easiest win. Most client sites have hundreds of images with empty or useless alt text. A generated first draft, reviewed by an editor, is a real accessibility improvement.
• Excerpt and title suggestions are useful as brainstorming tools for busy editorial teams. They should suggest, not publish.
• Image generation is fine for illustrations and abstract featured images. It is not a replacement for real product or team photography, and clients should know which is which.

We will cover the 7.0 release in more depth, including what was cut — real-time collaboration was pulled shortly before release and postponed — in a dedicated post next week.

Layer 3: AI agents working on the site

The bigger shift for development teams is agents. The official MCP Adapter plugin turns a WordPress site into a Model Context Protocol server, so AI tools such as Claude, Cursor and Codex can discover the site’s abilities and run them. It installs from the WordPress.org plugin directory and exposes nothing until you opt in: an ability has to be explicitly marked public before an agent can call it.

In practice, agents are already useful for content operations: auditing internal links, fixing metadata in bulk, restructuring categories, producing reports. We used exactly this approach to fix ten orphaned posts on our own blog with AI-assisted internal linking, and the write-up covers the guardrails we used.

The risk is equally practical. An agent with an administrator account and no review step can do a lot of damage quickly. The rules we apply are simple: a dedicated user with the minimum role needed, application passwords rather than real credentials, only the abilities the task requires, staging before production, revisions on, and a human approving the plan before anything runs.

Layer 4: AI-written content and search

Clients will ask whether they can use AI to write their blog. The honest answer is yes, with conditions. Google’s position is that it cares about whether content is helpful and original, not how it was produced. What it does penalise is “scaled content abuse”: publishing large numbers of pages mainly to rank, with little added value — whether a model, a freelancer or a spreadsheet produced them.

That gives a workable rule for client content: use AI to research and draft, then add what only the business knows — real examples, real numbers, a clear point of view — and publish at a steady pace rather than in bursts. Volume without expertise is the pattern that gets sites into trouble.

Layer 5: what agencies can sell

Most “AI services” pitched to small businesses are a chatbot widget with a monthly fee. There are better, more defensible offers, roughly in order of how often they pay for themselves:

Offer	Who it suits	Why it works
Accessibility clean-up with AI alt text	Any site with a large media library	Measurable, low risk, ties into accessibility obligations
Content operations: audits, linking, metadata	Blogs and publishers with years of content	Saves hours every month; results show in Search Console
Smarter on-site search	Large catalogues, documentation, knowledge bases	Visitors find answers; fewer support emails
Editorial assistance in the editor	Teams publishing several times a week	Faster drafting, with humans keeping control
Custom abilities for business workflows	Clients with bespoke plugins or WooCommerce logic	Makes their own processes usable by AI tools safely

The common thread is that each one solves a problem the client already has. If a feature only exists because AI is fashionable, it will be switched off within a year.

How to prepare your client sites

1. Get every site onto a supported version. WordPress 7.0 requires PHP 7.4 or newer. Sites stuck on old PHP cannot use any of this.
2. Write an AI policy with each client. Which providers, which data, which features, who reviews output. One page is enough.
3. Register abilities in custom plugins you build from now on. It costs little during development and future-proofs the work. Our guidance on when to build a custom plugin applies doubly here.
4. Start with internal use. Use AI for audits, content operations and development support on your own sites before selling it.
5. Put AI work under a maintenance agreement. Providers change models and pricing. Someone needs to own that, which is exactly what a maintenance retainer is for.

What this guide will cover next

This page is the hub for our AI series. Over the coming weeks we are publishing deeper guides on what WordPress 7.0’s AI features mean for agencies, connecting AI assistants to WordPress safely with MCP, using AI in development without shipping bad code, AI-written content and SEO, and which AI features are worth selling to clients. Each one will be linked from here as it goes live.

Frequently asked questions

Does WordPress 7.0 send my content to AI companies?

Not by default. The AI infrastructure is opt-in. Nothing calls an AI provider until an administrator connects one under Settings → Connectors and enables a feature that uses it.

Do I need the official AI plugin?

Only if you want its editor features: title and excerpt suggestions, alt text and image generation. Core provides the infrastructure; the plugin provides features built on it. Other plugins can use the same infrastructure.

Is it safe to let an AI agent edit a live site?

It can be, with guardrails: a least-privilege user, only the abilities the task needs, a test on staging, revisions enabled and a human approving the plan. Without those, no.

Will AI replace WordPress developers?

It is changing what developers spend their time on. Boilerplate gets faster; architecture, review, security and client judgement matter more. Teams that use AI well deliver more in the same hours, which is the point.

How should agencies price AI work?

Price the outcome and the ongoing ownership, not the model calls. Build costs are normal development hours; the recurring part is monitoring, provider changes and review, which belongs in a retainer.

Need help putting AI to work on client sites?

We build custom plugins, abilities and AI-assisted workflows for agencies, delivered under your brand. If you want capacity to explore this without hiring, our dedicated monthly plans give you a fixed block of senior hours each month, and our white label development guide explains how the arrangement works. Or tell us what a client is asking for and we will scope it.