Connect an Assistant to Your WordPress SEO

WP Visibility can give a supported assistant tools to read and change the site’s SEO settings. You supply the assistant separately, choose the WordPress account it uses, and configure which abilities are available.

Connecting an assistant is optional. You can also manage the plugin’s SEO fields yourself. If you do connect one, start with a read operation and verify the permissions before asking it to make changes.

What an ability is

WordPress’s Abilities API provides a registry of named actions, with defined inputs, outputs, and permission checks. It is available in WordPress 6.9 and later. WordPress’s Abilities API documentation, checked September 13, 2026.

The registry gives software a consistent way to discover what a site exposes. The plugin implementing an ability still determines the action and its checks. The presence of the API alone does not mean an assistant has permission to edit your site.

WP Visibility registers SEO abilities for tasks such as reading a post’s metadata, auditing a page, updating supported fields, and working with redirects. Which ones are available depends on the enabled modules, ability settings, and connected user’s permissions.

The API’s version history is separate from WP Visibility’s installation requirements. Check the current requirements before installing.

How the assistant connects

An assistant needs a compatible way to call those tools. WP Visibility includes an MCP endpoint at:

https://example.com/wp-json/wp-visibility/mcp

MCP is a protocol through which a client discovers and calls tools. The plugin’s built-in endpoint provides that connection without requiring an additional adapter plugin. Client configuration still varies, so use a supported setup from the connection documentation.

For sites managed through the command line, this command prints the plugin’s connection configuration:

wp visibility mcp-config

Use your own site URL and keep credentials out of shared examples. Access to an assistant subscription does not by itself confirm support for the required connection and authentication method.

Create access deliberately

Use a dedicated WordPress user with the permissions needed for the job. Create an Application Password for that integration.

WordPress documents Application Passwords as separate, revocable credentials used with HTTP Basic Authentication over HTTPS. They are associated with a user, so that user’s authority still matters. WordPress’s Application Passwords guide, checked September 13, 2026.

Do not assume that creating a new password for an administrator makes the resulting access narrow. Review the role and capabilities as well as the abilities available in the assistant’s tool list.

Enable the Agent module, then enable only the abilities required for the first task. Keep the account and credential owner recorded so access can be withdrawn later.

Begin by reading one page

Choose a page you know and ask the assistant to read its current SEO title and description. Compare the returned values with the plugin’s fields. Then ask for a page audit, if the account has the required permission.

This checks the site connection, selected page, and returned data without asking for a write.

An audit result is a set of checks to investigate. A missing description is observable; the best replacement wording still requires an understanding of the page and business. Do not treat the audit as a ranking forecast.

A useful first instruction is:

Read the SEO title and description for this page. Report their current values and any audit findings. Do not change anything.

Verify that the enabled tools and account permissions match the work you intended, even though the prompt itself asks for a read.

Test a reviewed change

For supported writes to become proposals, enable both Agent and Autopilot and set the guard mode to propose.

The guarded abilities cover single and bulk post SEO updates, supported settings changes, redirect creation and deletion, llms.txt updates, and AI crawler policy updates. Start with one title or description change, inspect the resulting proposal, and approve it through the review workflow after checking the wording.

Then inspect the published page and confirm that the expected value changed.

This control covers the supported ability path. It is not a universal approval requirement for every WordPress route. A credential with broader authority can still access other permitted metadata, settings, or approval routes. The approval ability is off by default, but that setting alone does not remove those other permissions.

Read the review queue documentation before relying on the configuration for client work.

Expand only after checking the result

Keep a record of the initial page, proposed value, approval, and published result. Add more pages when the process is understood and review remains manageable.

Use the plugin’s ability pause control when you need to stop that surface. Revoke the Application Password when the integration should lose access; pausing abilities is not credential revocation.

If authentication or permissions fail, inspect the configuration rather than granting administrator access as a routine workaround. The setup documentation is the place to work through the connection details.