What It Means That Your AI Assistant Can Now Run Your WordPress SEO

AI assistants such as Claude have moved beyond answering questions: they can now take actions inside other software. On WordPress, that includes your SEO. Given permission, an assistant can read your page titles and descriptions and change them, through the same channels you would use in the admin screens.

This piece sets out what that means for a site owner: what changed in WordPress, what an assistant can and cannot touch, and how you remain in control throughout.

What changed in WordPress

For years, every SEO plugin did its work in its own way, and an outside tool had no reliable means of knowing what a plugin could do. In late 2025, WordPress added a standard way for a plugin to list the actions it can perform and to describe each one: what it needs, what it changes, and who is allowed to run it.

Because the list is standard, an AI assistant can read it, see which actions exist, and run the ones it has permission for. WordPress 7.0, released in 2026, built this into the editor and added the tools to connect an assistant to your site.

The nearest precedent is schema.org, which years ago gave websites a shared vocabulary for describing their content to search engines; a good deal of modern search was built on it. This is the same idea one step over: instead of describing what a page is, it describes what a site can do.

Nor is it a one-off. WooCommerce, the popular store plugin, added the same kind of actions in 2026.

Why SEO work suits this well

Of the work an assistant could take on inside a WordPress site, routine SEO maintenance fits unusually well, for four reasons.

Most of it is find-and-fix: find the posts missing a description and write one, find the redirect chains and shorten them, find the pages set to hide from search by mistake and correct them. The work is bounded and repeatable, the sort of thing people put off and an assistant can do steadily.

The data is small and predictable. A description is a short piece of text, a visibility setting is one of a few known options, and a redirect is an old address, a new address, and a type. Because the shape of the data is known, the site can check what an assistant sends before saving anything.

The permission system already exists. WordPress knows who is allowed to edit a post and who is allowed to change site settings, and these actions run under the same rules. An assistant can do no more than the account behind it already could.

And mistakes are recoverable. A poor description is a nuisance rather than a disaster. With previews, before-and-after logging, and a clear warning on the one action that removes anything, the room for harm stays small. The alternative carries its own cost: a tool that can find the posts missing a description but cannot fix them leaves all the work with you.

What your assistant can read and change

WP Visibility registers 30 of these actions. Of those, 29 are active the moment you turn the feature on; one ships turned off and stays off until you enable it yourself.

Broadly, they cover:

• Read and write a post’s title, description, and search visibility settings.
• Edit many posts at once, with a preview shown first by default.
• Run an audit of your whole site or a single post.
• Manage redirects.
• Read and change your settings.
• Manage the llms.txt file and your rules for AI crawlers.
• Suggest internal links between your posts.
• Read the log of what the assistant has done.

Whatever an assistant can read (your titles, descriptions, settings, redirects, the llms.txt file, and the AI-crawler rules) it can also change through a matching action. The rest only look: a site audit or a report reads your site, tells you what it found, and changes nothing.

One note on llms.txt: WP Visibility ships it but marks it Experimental, because no major AI crawler fetches the file yet.

Connecting an assistant to your site is a one-time step. WP Visibility works with the official WordPress connector, with WordPress’s built-in connection system, or from the command line.

How you stay in control

None of this happens without your say-so, and the controls are layered.

• Any single action can be turned off.
• A limit caps how many changes one person’s assistant can make in a set time, so a mistake cannot run away.
• An off switch stops every action at once. Turning it back on takes a person; the assistant cannot do it.
• A propose mode turns every change the assistant wants to make into a pending item that waits for your approval. Nothing is written until you approve it.

What you could ask it to do

Once connected, a number of workflows stop being projects and become requests.

Moving from another plugin. On Yoast or Rank Math, you can ask the assistant to bring your titles and descriptions across, with every change shown as a preview before anything is written. WP Visibility imports from Yoast, Rank Math, SEOPress, The SEO Framework, and AIOSEO, and stores the result as normal WordPress content. Redirects move separately: export the old plugin’s redirects to a CSV file, turn on the Redirects module, and import the file there.

Internal linking. Ask it to suggest links between related posts. With propose mode on, each suggestion waits for your approval rather than going live on its own.

A standing audit. Set one up to check the site on a schedule and report what it finds, then fix the routine items after you review them.

Cleanup after a redesign. After a site move or a batch of new URLs, ask it to create redirects for the changed addresses and log every change, so a record exists.

What other plugins do today

The other SEO plugins are not standing still. Yoast has stayed on the reading side: its actions return a content score, a readability score, and an inclusive language score, and nothing more. Rank Math and AIOSEO have gone further, and in their free versions, not behind a paid tier. Rank Math lets an assistant change site settings and fix failed audit tests. AIOSEO lets it update post metadata and create redirects. Reading was the first phase, and it is over.

The caveats

The fair objection is that all of this is new. In part it is: the standard itself, the way WordPress lists and runs actions, is built into WordPress and stable, while the assistant tools on top of it are newer and still changing. The sensible course is to start small, keep propose mode on at first, and watch how it goes. Sitting it out entirely would mean ignoring where WordPress and search are heading.

The next step

Nothing has to be decided today in order to learn where you stand. Run the free scanner at wpvisibility.com to see how your site looks to AI assistants; it grades your AI visibility in about a minute.

If you want the plugin, WP Visibility is $99 a year for unlimited sites, with client sites included and a 30-day refund. The license covers updates, so the plugin keeps working either way.