WordPress AI Was Built to Ask First

WordPress 7.0, released in May, introduced AI into the CMS core for the first time. But its most consequential decision may have been what the release did not do: turn the capability on automatically.

The infrastructure is present in the codebase, yet no AI service is contacted until the site owner connects a provider and enables it. A site upgraded to version 7.0 without further configuration behaves exactly as it did before. The activation switch belongs to the person who owns the site.

That opt-in, plugin-based approach was a deliberate statement: powerful new capabilities should not appear on a customer’s website without permission.

SiteGround’s default AI rollout

Within days, SiteGround took the opposite approach. The managed WordPress host pre-installed and activated its own AI product across its customer base, configured it as the default connector, and included a substantial allowance of free usage.

The product’s active-install count passed one million almost immediately. Many site owners logged in to discover new software already running on websites they had not chosen to modify.

Recommended reading

Signal tests Android secondary-device support

The reasoning was understandable. Setting up native AI can involve multiple steps, and many customers might never complete them. Pre-installing the tool and attaching free usage removes that friction. From a hosting operator’s perspective, it looks like a straightforward way to deliver value faster.

But the backlash was not primarily about AI or the quality of SiteGround’s product. It was about consent. Many critics already use AI regularly; they objected to finding it enabled without having made that choice.

Convenience is not consent

A feature can be useful and still feel imposed when it is installed without approval. The argument that customers can remove it later is not equivalent to asking first. It shifts the burden of noticing, understanding, and reversing the change onto the customer.

A one-click setup prompt offers the same convenience while preserving the customer’s decision. That difference matters because it separates the quality of a change from the consent given for it.

Hosting companies routinely make changes without asking customers. The distinction is whether the change is defensive or additive. Patching a vulnerability, blocking a malicious request, or disabling an actively exploited plugin protects the customer and the wider platform. Installing a new product changes what the website is.

The principle is simple: maintain the platform freely; change the product only with a yes.

Hosts can still make adoption easy. They can keep new capabilities off by default, put them one click away, give multisite administrators a central control panel, and make any pushed change as easy to remove as it was to install. Clear notices should explain what is changing and how customers can decline.

None of this is anti-AI. In fact, clear consent may help hosting companies adopt AI more confidently because customers know that nothing will appear uninvited.

The customer owns the site

As AI becomes a standard feature across the web, every host will face the same choice: activate a useful capability for everyone or let customers decide. The fastest option will not always be the right one.

The asymmetry is easy to miss. A host makes a change and moves on to the next support ticket. The site owner remains responsible when visitors encounter unexpected behavior, when an inbox fills with complaints, or when a business’s public presence changes.

That is why asking first is more than a courtesy. A host’s authority extends to the edge of the customer’s ownership—and stops there. The role is stewardship, not possession.

The trust customers buy is the confidence that nothing will happen to their site without their approval, except when intervention is necessary to protect it. That trust can take years to build and an afternoon to spend. The difference between an AI feature that is welcomed and one that feels taken is whether anyone thought to ask.