Repair the link your reader needs
MCP Abilities – Broken Link Checker helps your AI client inspect recorded link failures, find their source pages and preview a repair.
A working page is not always the right destination
Suppose a bicycle repair guide links to a supplier’s old sizing chart. The address no longer works. Sending readers to the supplier’s homepage would remove one error, but still leave them without the chart.
Start with the sentence around the link. Find the current chart, check that it belongs to the right supplier and product, and open it before changing the address.
A redirect recorded by Broken Link Checker can suggest a destination. It does not prove that the destination is current or answers the reader’s question.
The guide needs the sizing chart. A general shop page may load correctly and still be the wrong replacement.
Fixing a link and clearing a report are different jobs
Replacing a URL changes the content a visitor follows. Clearing the local queue removes pending scan work. Deleting a stale finding removes its BLC record. Only the content change repairs the link on the page.
Use the saved page as the test: open it and follow the link. A shorter error list cannot establish that the repair worked.
This add-on reads findings already stored by the local Broken Link Checker scanner. It does not run a new scan. Queue cleanup can affect all detected local queues, not just the finding being reviewed.
On the left, the link reaches a page. On the right, the report is cleared while the broken link remains.
From a recorded finding to a checked link
1. Find the source
Name the exact site. List a small set of recorded broken links and request source references. Read each affected page to understand what the link promises.
2. Preview a verified replacement
Check the destination, then supply the old and new URLs with a dry run. Select the post types and publication statuses. Review the affected content and excerpts before choosing a write.
3. Read the individual results
A replacement can affect several pages. Inspect each post’s result for permission or save errors; an overall success response does not mean every post was updated.
4. Check the visitor’s route
Open the saved pages on desktop and mobile. Follow the repaired links and check the surrounding text. Let Broken Link Checker check again before removing stale records.
Know the reach of a replacement
The replacement operation matches literal text in the selected posts’ content and excerpts. It can also match part of a longer URL. Inspect the complete affected content rather than relying on the replacement count.
Menus, custom fields and other storage locations are outside that operation. The add-on also provides separate notification and record-maintenance functions. Adding a notification recipient changes who may receive BLC email and needs an explicit decision.
What you need
Install the add-on on the site you want to inspect. It requires WordPress 6.9 or newer with its built-in Abilities API, PHP 8.0 or newer, Broken Link Checker with local scanner data, and the WordPress MCP Adapter for the client connection.
The connected account needs the permissions for the selected operation. Inspection and queue maintenance generally require site-administration rights. Content writes also check permission for each affected post.
The core operations use WordPress and local BLC data. They do not require an external repair service or provide access to the separate cloud scanner. Your MCP client supplies the AI connection.
Start with one recorded link
Install the add-on and ask your client to show the finding, its source pages and a replacement preview. Decide what the reader needs before changing an address.