Match the repair to the finding
The stored record distinguishes a wrong URL from a redirect. Use that distinction to choose the operation that fits the finding.
01
Start with the problem your site recorded
Ask the AI assistant to inspect the Broken Link Checker tables so the repair stays tied to the stored finding that needs attention.
02
Correct a URL that points to the wrong place
Use URL repair when the recorded address is wrong, so the finding points to the address visitors should reach.
03
Handle a link that reaches its destination through a redirect
Use redirect auto-fix when the recorded link resolves through a redirect, so you can resolve that finding without treating it as a wrong URL.
04
Clear the record when the repair is done
Clear the local queue item once the repair is complete.
Know the boundary before you act
The add-on supplies the connection; the companion product retains the underlying responsibility.
Interface role
The add-on connects an assistant to the site’s WordPress operations.
State owner
The companion plugin remains responsible for scanner status and the items that require action.
What must already be in place
These are the named prerequisites for the runtime and data this add-on uses.
WordPress 6.9 or newer with the Abilities API
WordPress Abilities APIRegisters the link-checking operations.
PHP 8.0 or newer on the server
PHP 8.0 or newerProvides the server runtime required by the plugin.
Installed and enabled
WordPress MCP AdapterExposes the registered abilities to MCP clients.
Installed and enabled
Broken Link CheckerOwns the local link data, scanner state, and repair records used by this add-on.
Choose the stable ZIP
Download the stable ZIP to give an MCP client access to this add-on. That makes the site’s existing local data available for a focused repair decision.