Get the plugin
WP MCP/Integrations/SEO

SEO integration

Redirection MCP

WP MCP reads and writes the Redirection plugin's own redirects as ops on the theme dispatcher pair: list groups, list and read redirects by group, status or search, and create, update, enable, disable or delete them. Before anything is saved it refuses unsafe sources and targets, a source another plain redirect already owns, and any redirect that would loop through the site's enabled redirects, reporting the cycle. Every write is snapshotted as a row image, so an edit goes back in place, a deleted redirect returns at its own id, and a created one is removed again. Writes cover plain URL matches; conditional redirects are listed and can be enabled, disabled or deleted, but not rewritten.

theme-readtheme-write

In practice

How Redirection work goes with an agent.

The Redirection plugin keeps its rules in its own tables, with a row per redirect and a group for each set of rules. A redirect is more than a source and target. It has a match type, an action type, a status code, a regex flag, an enabled flag and a hit counter. WP MCP reads all of that, but writes only the plain case: a site-relative source, matched as a URL, redirecting to a URL or answering an HTTP error. Before anything is saved it checks for loops and for a source another redirect already owns.

List the redirects in the Old Blog group that have never been hit, then disable them.

Runs list-redirection-groups for the group id, list-redirection-redirects filtered by group_id, then disable-redirection-redirect for each one that has no hits. Each disable is snapshotted, and the hit counts are kept.

Redirect /old-pricing to /pricing with a 301, and tell me if that would create a chain.

Runs create-redirection-redirect with source, target and action_code 301. The plan is checked against the site's enabled redirects first, and a loop is refused with the cycle named. The new row is snapshotted, so rollback-operation removes it.

The 2019 campaign pages are gone for good. Make /promo-2019 return 410.

Runs create-redirection-redirect with action_type error and action_code 410. Allowed error codes include 404, 410 and 451. The create is snapshotted and undoable.

Delete redirect 318, I created it by mistake.

Runs delete-redirection-redirect, which needs confirm:true. The whole row is snapshotted first, and rollback-operation brings it back at the same id.

What your AI can do

Real Redirection operations, every write reversible.

  • List Redirection groups and redirects, filtered and paged
  • Create redirects to a URL or an HTTP error
  • Edit, enable, disable or delete a redirect
  • Refuse redirect loops, duplicate sources and unsafe targets before saving
  • Roll back any redirect change exactly

Example prompts

Example Redirection prompts.

List every disabled redirect in Redirection.

Redirect /old-pricing to /pricing with a 301.

Delete the redirects that point at pages that no longer exist.

Under the hood

The Redirection calls, under the hood.

wpmcp, redirection

theme-read({ operation: "list-redirection-redirects", args: { status: "enabled" } })

theme-write({ operation: "create-redirection-redirect", args: { source: "/old-pricing", target: "/pricing" } }), loop-checked, snapshotted

Safety and access

What can be undone on Redirection, and what costs what.

Recoverable on Redirection

  • Every write is stored as a row image of the redirect, so rollback-operation restores it exactly.
  • An edited redirect goes back in place, a deleted one returns at its own id, and a created one is removed.
  • Undoing a create never removes a different redirect that has since taken its place.

Redirection limits and opt-ins

  • Writes cover plain URL-matched redirects only. A regex redirect or a conditional one (login state, referrer, cookie) can be listed, enabled, disabled or deleted, but update refuses it.
  • Redirect codes for the URL action are 301, 302, 303, 307 and 308. Error codes are 400, 401, 403, 404, 410, 418, 451, 500, 501, 502, 503 and 504.
  • Sources must be site-relative paths, never the site root. Targets are a site-relative path or an absolute http or https URL.
  • Deleting needs confirm:true.

Free or Pro: All Redirection operations are free. They run on the theme dispatcher pair as theme-read and theme-write, so they add no extra tools to your client's list. Every operation requires manage_options, the capability Redirection gates its own screens behind. Nothing here is opt-in. There is no Pro-only part of this integration, and the snapshot and undo behaviour is the same on every install.

In the free plugin

The Redirection integration is in the free plugin.

The core Redirection tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.

Frequently asked

Redirection MCP: questions, answered.

With Redirection, can the agent edit a conditional redirect?

It can list, enable, disable or delete one, but update refuses it rather than flattening conditions (login state, referrer, cookie) it cannot represent.

Is delete reversible?

Yes. Delete needs confirm:true, and the redirect comes back at its own id with rollback-operation.

Does this touch the redirects WP MCP manages itself?

No. WP MCP has its own managed redirect tools (create-redirect, delete-redirect and others) that keep their own list. The Redirection integration reads and writes the Redirection plugin's tables only. If both are active, the agent chooses by which plugin your site actually serves redirects from.

Which group does a new redirect go into?

The group_id you pass. If you leave it out, the redirect goes into the first group of Redirection's WordPress module. The agent can list groups first with list-redirection-groups, which shows each group's module, enabled flag and redirect count.

What does the loop check actually follow?

It follows the target through the site's enabled plain redirects, up to ten hops, and counts the redirect being written or enabled. If the chain returns to a source it has already passed, the write is refused and the cycle is reported, so nothing is saved and no undo point is left behind.

Point your AI at Redirection.