SEO use case
Fix broken links in WordPress with AI, from audit to the fixes you choose.
Fix broken links in WordPress with AI by reviewing GoBuildWP Free's audit and Pro's proposed changes. The plan shows before/after values and applies only selected items. Ledger records do not guarantee undo: inspect each item's recovery support, irreversible flags and later-edit conflicts before approval.
GoBuildWP Free + Pro, Works in Claude Desktop, Runs under Production Safe, Pricing
Illustrative ability sequence for GoBuildWP Free 1.18.6 and Pro 1.12.4. IDs, results and recovery outcomes are examples, not a recorded client or WordPress test. Select Read Only explicitly for the initial reads; Production Safe is the default. Connection management requires manage_options on a single site or superadmin on multisite.
The problem
Why broken links outlive the audit that found them
Every site accumulates dead internal links: a service page renamed, a post trashed, a slug tidied. An audit lists them in a minute. Then the list sits there, because each fix means opening the post, finding the link, guessing the right new target and hoping nothing else on the page moved.
The fix is mechanical once the target is known, which is exactly where AI helps and where it can do damage. A plan with a confidence per item keeps the guessing visible, and a fix that changes only the href, byte for byte inside Elementor's data as well, keeps the damage out.
What Claude Desktop can do here
- Audit published posts and pages for broken internal links, orphans, thin content, missing descriptions and schema problems (Free)
- Retarget a dead link to where WordPress already redirects it, the post renamed from the dead slug, a post titled like the trashed page, or the clearly closest slug
- Propose one 301 in Redirection or Rank Math instead, when three or more posts link to the same dead URL
- Suggest related links for an orphan page, appended as one paragraph to block-editor posts only
- Draft a 120 to 160 character meta description from the post's excerpt or opening prose, written through the active SEO plugin
- Apply reviewed item IDs and inspect applied, skipped and failed results, ledger entries and per-item undo support; sharing a group does not guarantee group recovery
What it cannot do
- Determine a visitor's intent from a matching slug alone. Candidate destinations use defined signals and still need human review; with no confident match, stop and list candidates
- Touch page-builder layouts when adding related links; those go into block-editor content only
- Write redirects in Yoast Premium, SEOPress Pro or AIOSEO Pro; the plan names their ability for a manual fix
- Fix structured-data findings, which stay report-only
- See links a theme, menu or shortcode prints; the audit reads post content and Elementor data
The prompt
The prompt to paste into Claude Desktop
Paste this into Claude Desktop. Creating the plan persists proposal data for review; it does not apply the proposed target changes. Pick exact item IDs and review recovery limits before authorizing application.
- Step 3 is where a person earns their keep: a redirect changes where every visitor lands, not one link.
- Step 5's cap mirrors the plugin's own rule: more than 20 items in one call needs an explicit confirmation.
- Descriptions are drafted from the post's own words. Read them; a good draft is still a draft.
Find and fix broken internal links on this WordPress site, carefully.
1. Run audit-content with checks broken_links, orphans and seo_meta, and wait for it to finish.
2. Run content-fix-plan on that job. Show me every item as a table: post, what changes, before, after, confidence.
3. Mark anything below 0.8 confidence, and every redirect, as "needs my review". Show irreversible items and restoration limits before asking me to approve; preserve their original values. A confidence score is a review signal, not proof of visitor intent.
4. Wait for me to reply with the item ids to apply.
5. Apply exactly those with content-fix-apply. Never more than 20 at once.
6. Check every changed destination's HTTP status and final URL, inspect redirect chains, and load three representative rendered pages. Report each failed or skipped item.
7. If a fix is wrong, inspect its actual undo support and before-image before requesting rollback-change. Report unsupported or conflicting items for manual recovery instead of promising undo.Under the prompt
The abilities Claude Desktop will call
Registered GoBuildWP abilities, each with its own schema and permission check. The live ability list on your site is the final word; the tool map lists every group.
audit-contentSite-wide findings as a background job; changes nothing
audit-content-statusThe job's progress and its findings when done
content-fix-planOne item per exact change, with a preview and a confidence; kept 24 hours
content-fix-applyWrites only the chosen items, skipping any post that changed since the plan
verify-rendered-pageReads the served page to confirm the fix
rollback-changeRequests supported recovery after inspecting irreversible items, before-images and later-edit conflicts; a group is not universally undoable
Safety and recovery
Every fix is its own change
- Safety profile
- The audit reads content; creating the plan persists proposal data without applying the proposed target changes. Its source classification allows the Read Only planning route. Applying needs Production Safe; more than 20 items also needs confirm=true. That API flag is not proof of a person's approval.
- Change ledger
- Each applied item has a ledger row and calls can share a group. Inspect the undo plan, before-image availability, irreversible items and conflicts before requesting individual or grouped recovery.
- Rollback
- A link undo puts the field back exactly while it still holds what the fix wrote; after later edits it swaps back only that fix's own attribute and refuses when it cannot tell them apart. Supported redirect recovery deletes the created redirect through its owning plugin and checks removal. Inspect the exact item's recovery support; not every description/redirect writer is reversible.
- #4410Link retargeted in "Boiler servicing" (group g-58)Rollback available
- #4415301 /old-offers/ to /offers/ in RedirectionRollback available
- #4416Meta description drafted for "Contact"Rollback available
Where the plan stops
- A plan is kept for 24 hours and only for the person who made it; an item whose post changed since is refused.
- Rank Math redirects are refused until its setup wizard is finished or skipped, because Rank Math serves none before that.
- Descriptions go through the active SEO plugin; an AIOSEO description is recorded as irreversible, since AIOSEO keeps its own table.
- External links are checked only when asked for, and at most a set number per run.
How profiles, confirmations and rollback fit together: safety profiles and the change ledger.
Setup
Connect Claude Desktop
The audit runs on Free alone; the plan and the fixes need Pro.
GoBuildWP Free runs the content audit, reads its findings and verifies rendered pages. You can fix what it lists by hand, or with the free post and search-and-replace abilities.
Pro adds plans with confidence signals, selected link/redirect fixes, related-link suggestions and description drafts. Recovery is per supported item; AIOSEO description writes are irreversible in this route, and later changes can prevent undo.
Install GoBuildWP Free, then Pro
Run the audit on Free first if you only want the list. Add Pro for the plan and the fixes.
Add the connector
In Claude Desktop, Settings, then Connectors, then Add custom connector, with your site's GoBuildWP MCP URL.
Read Only for the plan
Run steps 1 to 4 on the source-classified Read Only planning route. The plan is stored for 24 hours; proposed target changes are not applied. Read Only here is not a promise that no proposal metadata is persisted.
Production Safe to apply
Switch the profile only when you have picked the items.
Check a redirect plugin
If you use Rank Math for redirects, finish or skip its setup wizard first: until then it stores redirects and serves none.
Choosing a useful destination
Repair the link, add a redirect, or leave the item for review?
A broken internal link report identifies a problem; it does not establish the intended destination. Open the source page, read the anchor in context and compare the candidate destination with the content the visitor expected. A similar title alone is not enough to approve a replacement.
If the destination still exists under a new URL, update the link to that exact page. A redirect may also be appropriate when the old URL still has visitors or other referring links. When content has no relevant replacement, remove or rewrite the obsolete reference after editorial review instead of sending everyone to the home page.
- Check whether the failure is a typo, renamed page, removed content or a temporary access error before choosing a fix.
- Review each proposed source field, old URL, new URL and explanation. Leave uncertain matches unselected in the Pro plan.
- After applying selected items, open the source page and follow the link. For a redirect, inspect the old URL response and final destination for loops or unnecessary chains.
- Rerun the relevant audit and preserve unresolved findings. Use scheduled site audits to notice future regressions; scheduling a report does not repair its findings.
FAQ
Questions about how to fix broken links in WordPress with AI
Can AI fix broken links in WordPress?
Yes, with reviewed targets and selected items. Free audits content; Pro proposes before/after changes and applies the chosen items. Inspect returned failures, verify every changed destination and check per-item recovery support. An AIOSEO description write in this route is irreversible; a ledger entry alone does not promise undo.
Will it break Elementor pages?
It is built not to. Inside Elementor's data the JSON is never decoded and re-encoded whole: each string holding the link is re-encoded so its escaping stays byte for byte, and a string that cannot be reproduced exactly is refused. Elementor's element cache for that post is cleared so the page renders from the data.
When does it add a redirect instead of editing links?
When three or more posts link to the same dead URL and a redirect plugin is available, one 301 in Redirection or Rank Math is proposed instead of editing every post. After creating it, the site requests the old URL once to report whether the redirect is really served.
Does it work with my SEO plugin?
Description drafts are written through whichever supported SEO plugin is active: Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework, Slim SEO or SmartCrawl. The audit itself reads all seven.
Try it on staging first.
Install the free plugin, connect Claude Desktop, and run the read-only half of this prompt before anything on the site changes.