WordPress AI: Do You Need to Turn It On?

Should I turn on the AI connection built into WordPress?

WordPress 7 added AI connection infrastructure, but that does not mean AI is running on your site—or that you need to enable it. Check the layer, job, access, and review process before deciding.

You logged in to write a post, or check an order, or figure out why a form email didn’t arrive. Somewhere between the dashboard and the thing you actually came to do, there it is. A sparkle icon in the editor. A settings screen called Connectors that you don’t remember seeing before. Maybe an email from your hosting company announcing an AI assistant, included free with your plan.

Your site was fine yesterday. Nothing broke. But the screen seems to be asking you a question you didn’t plan on answering this week: do I need to do something about this?

Short answer: no. Not because AI in WordPress is fake or useless, but because a new option appearing in your dashboard is an invitation to look, not a deadline to act. And before you can decide anything useful about it, you need one distinction that the announcements tend to skip.

“WordPress AI” is not one thing

The phrase sounds like a single feature with a single switch. It’s actually several separate layers that often get bundled together in conversation:

WordPress core now includes connection infrastructure. Think plumbing: a standard way for the software to talk to AI services. Plumbing doesn’t do anything on its own.
The official AI plugin is a separate, optional install that adds visible jobs like generating titles, excerpts, and image alt text.
An AI provider (Anthropic, Google, OpenAI, and others) is the outside company that actually runs the model. Your site would connect to one through its own account, with its own billing and its own data policies.
WordPress.com is a different product with its own separately managed AI tools. What you read about WordPress.com does not describe a self-hosted site, and vice versa.
Hosting companies and plugin makers can package their own AI assistants, with their own defaults, on top of everything above.

Five layers, one nickname. That’s why the question “is AI on my site now?” doesn’t have one universal answer. It has your site’s answer, and that’s something you can actually check.

What actually changed in May

WordPress 7.0 came out on May 20, 2026. It added two relevant pieces to self-hosted WordPress: an AI Client that lets WordPress communicate with AI models, and a Connectors screen that centralizes outside connections.

What it did not add is a working assistant. WordPress’s own documentation lays out what a self-hosted site needs before any of the useful jobs exist: install the official AI plugin, install and activate a connector for a provider, add that provider’s API key, then go into the settings and enable the specific features you want. Several deliberate steps, each one a choice someone has to make.

So for a stock self-hosted site, updating to WordPress 7 did not quietly connect your content to an AI company or start generating anything. The plumbing arrived. Nothing is flowing through it until someone hooks it up. That is also why you usually do not need to rebuild your WordPress site for AI.

That said, “stock” is doing real work in that sentence. Your host or a plugin can add its own layer with its own defaults. SiteGround, for example, documents that its clients get an AI Studio plan activated by default, which includes access to its WordPress agent. And WordPress.com manages its AI tools separately, as opt-in switches in its Hosting Dashboard, with the editor assistant available on its paid plans.

Which means the honest version of “is it already running on my site?” is: probably not from the WordPress update itself, but the only way to know is to look.

How to look

You don’t need to change anything to find out what’s there. You’re just reading labels.

On a self-hosted site: check Settings → Connectors to see whether any provider is configured. Check your Plugins list for anything AI-related, and note who made it: the WordPress project, your host, or a plugin company. If the official AI plugin is installed, Settings → AI shows which features are enabled.

On WordPress.com: check Hosting Dashboard → Settings → AI tools and read each toggle. If external AI agents might be involved, there’s a separate AI and MCP area under account settings worth reviewing too.

If what you’re seeing is branded by your hosting company, the WordPress settings won’t tell you the whole story. The host’s own account dashboard and documentation describe what their tool can do.

One caution: if you find a plugin you don’t recognize, resist the urge to delete it on the spot. Find out what installed it and what depends on it first. Inspection is a reading exercise, not a purge.

The better question: what job would it do?

Once you know what’s actually present, the pressure question (“am I falling behind?”) can be traded for a more useful one: what would I actually use this for?

The official plugin’s current jobs are bounded and modest. Title suggestions for a draft. An excerpt. Alt text for images. A summary, a meta description, a generated featured image. These are suggestion-level tasks: the tool proposes, you read the proposal, you accept it or toss it. If a title suggestion is bad, the cost is the ten seconds you spent reading it.

Now put that next to what some of the newer agents can do. SiteGround’s connected agent, per its own documentation, can update WordPress, install or remove plugins and themes, manage users, create or delete content, work with WooCommerce data, and change settings. WordPress.com’s external-agent access, once enabled, turns on both read and write tool groups by default, which you can then narrow.

Both of those get called “WordPress AI.” They are not the same decision. One drafts a sentence you can ignore. The other holds keys to rooms you’d want to know about. The word “AI” on the label tells you almost nothing about how much responsibility you’d be handing over, and that difference, not the technology, is what your caution should scale with.

Comparison of a suggestion tool requiring human review with a site-changing agent that has broader access and responsibility.

Four things to check before you flip any switch

When you’re weighing a specific AI feature, on your site, this is the whole evaluation:

Four-step decision path showing Layer, Job, Access, and Review with papers, a checklist, a key, and a notebook.

Layer. What product is this, exactly? WordPress core support, the official plugin, a WordPress.com tool, your host’s assistant, something a plugin added? Who made it and where do its settings live?

Job. What specific problem on your site would it solve? Not “it can generate content” in general. A real task you actually do and would rather not: writing alt text, drafting excerpts, whatever it is. If you can’t name the job, that’s your answer for now.

Access. What can it read, send, create, change, publish, or delete? And what does it cost, on whose account? Provider accounts and billing sit outside WordPress, while credentials may be configured and stored through the site. A key stored through the WordPress admin screen is masked on screen but not encrypted in the database. Plain-language version: you should know who owns that account, where charges show up, and what the provider says it does with what your site sends. Those terms vary by provider. OpenAI, for instance, documents usage-based API pricing and says API data isn’t used for training by default, but that’s OpenAI’s policy, not a rule of the ecosystem.

Review. Who checks the output, and who can undo the change? WordPress.com’s own documentation warns that generated content can be inaccurate or biased, and its assistant makes you accept, regenerate, or discard each result. That accept step is not a formality. It’s the job you keep. For a title suggestion, review means reading it. For an agent that can touch plugins, users, or settings, review means backups, a way to test changes before they’re live, and knowing how you’d roll something back. Prudent boundaries, not guarantees. That same human-review boundary guides how WP Site Success uses AI-assisted content.

Three honest answers

Run a feature through those four checks and you land in one of three places. All three are fine.

Use it. The job is real, the access matches the job, and you know how you’ll review the output. Letting a tool draft alt text or excerpt options, with you reading every one before it publishes, is a small, contained decision. You don’t need anyone’s permission to make it.

Test it carefully. The job seems plausible but you’re not sure the output will be worth it. So you try it on low-stakes work: a draft nobody sees, one post’s excerpts for a couple of weeks. With anything that can change your site rather than suggest things to you, the bar goes up: current backup, tighter permissions, a way to check what it actually did.

Ignore it for now. There’s no job on your list it would take over, or the supervision it needs costs more than the task it saves. This is not falling behind. Leaving the documented stock setup unconfigured does not stop your existing site from continuing to work as before. You can revisit the decision later. A deliberate “not now” is a decision, not a deferral.

Notice what’s missing from that list: “turn everything off in a panic” and “turn everything on to stay current.” Neither survives contact with the four checks.

Your site doesn’t owe the feature anything

The change is real. WordPress did add an AI layer, the ecosystem is building on it, and some of the bounded jobs may end up genuinely useful to you. But a capability showing up in your dashboard has never once been evidence that your site needs it. Your site needs what serves the people who visit it and the business it holds up. That was true before the sparkle icon and it’s still true now.

You’re allowed to look at the new screen, understand what it is, and close the tab.

And if the thing you’re looking at doesn’t match anything in this article—a host offer you can’t parse, a plugin that appeared after an update, a toggle you can’t tell is on or off—that’s exactly the kind of thing worth handing to someone instead of decoding alone. Send me the screenshot, the plugin name, or the email. We’ll figure out what it actually is, whether it’s connected to anything, and whether it solves a problem you actually have, before anything changes on your live site.

That part hasn’t changed either.

WordPress Has AI Now. Do I Need to Turn It On?