WordPress Broken Link Checkers: WPMU DEV and AIOSEO Compared

Compare Broken Link Checker by WPMU DEV and Broken Link Checker by AIOSEO for maintaining links in articles and external references. WPMU DEV offers local and cloud modes; AIOSEO centers on account-connected cloud checks and monthly allowances. Treat either product’s findings as a queue for checking actual access and content, not a confirmed list of links to delete.

How does link checking differ from a 404 log?

A link checker finds addresses your content or menus point to and tests their destinations. A 404 access log records requests to missing addresses on your own site. A checker can find a typo nobody has clicked yet, while a scanner’s request may concern a path that no article ever linked to.

For example, an old installation tutorial may cite a removed official document. Link checking helps identify the destination and the article containing it. If you move an article within your own site, update internal references and separately configure any needed redirect for the old address. Your redirects cannot repair an external server outage.

Decide whether you need images, videos, menus, and custom-field URLs checked as well as internal and external text links. A body-content scan is not necessarily a whole-site review. Some resources also require more than a status code: a video’s page may load while the video has become private.

Compare execution, accounts, and allowances

WPMU DEV: local and cloud coverage differ

The official WPMU DEV guide distinguishes Local and Cloud. Cloud requires a Hub connection, but not necessarily paid membership. A free account still has conditions affecting scanning and rechecks; review the free Hub restrictions instead of treating both modes as identical unlimited services.

Local checks use your hosting resources, so watch workload and frequency on larger sites. Cloud crawling depends on public access: membership-protected pages, maintenance screens, and orphaned content not reached through site navigation can limit coverage. The documentation acknowledges differences between modes. For multisite, also check the conditions applying to subsites.

AIOSEO: distinguish allowance from external-link eligibility

AIOSEO uses an account-connected service. Its pricing information and plugin listing describe a free monthly allowance of 250, with paid plans varying by monthly volume and sites. Links are not articles: one article with many URLs can create many checkable items. Do not assume a small article count means every full-site recheck fits the allowance.

Free external-link coverage needs confirmation. The WordPress.org description says “250 internal links” monthly, while the official 1.2.6 changelog says all plans, including free, support external links. Because the descriptions conflict, do not assume free is always internal-only or promise unlimited external checks. If references are your priority, verify your connected account’s scope and remaining allowance and test one internal and one external example before choosing.

The current listing also covers links in menus, custom fields, synced patterns, and supported page builders. Finding a link and safely rewriting it from the report are separate capabilities. Some builder content must be changed in its own editor; use the reported location to identify the correct place.

Start with a limited first scan

Install from the official distribution channel and begin with important published content. Prepare a backup and recovery method before actions that rewrite content. When connecting an external account, check which addresses and results are transmitted and retained.

1. Choose the mode. In WPMU DEV’s Link Checker menu, distinguish Local and Cloud and follow connection instructions if selecting Cloud. In AIOSEO, confirm the connected account and plan.
2. Set content and resource coverage. Include required posts, pages, menus, and images. Treat protected addresses and external service links separately from public references.
3. Establish whether scanning finished. Distinguish queued, scanning, and failed states. Zero findings do not establish a completed, error-free scan. Check connection, quota, public access, and local job execution.
4. Record the destination and occurrence. Keep the URL, article/menu location, response or failure reason, and last-check time. Identify addresses repeated across many articles to prioritize work.
5. Review and fix one item manually. Apply the checks below before changing the relevant occurrence. Before a bulk replacement, inspect its affected items and count.

For a removed document cited in several articles, first look for a current official document addressing the same subject. Replace the URL only if it still supports your explanation, and reread the claim too. Substituting any working page may clear the error while leaving the evidence wrong.

Distinguish a flagged result from an actual removal

HEAD requests response information without the page body; GET retrieves the actual content. Automated requests may fail while an ordinary browser works. The reverse is possible too: a checker can report a response while visitors encounter a certificate warning. Do not infer validity or safety from a number alone, and do not bypass certificate warnings or disable validation to make a check succeed.

If a resource opens only for a logged-in operator, assess access for ordinary readers. Restricted access is not necessarily a broken resource, but an article describing a free public guide may need revision if the destination becomes subscriber-only. The AIOSEO failure descriptions distinguish blocking, timeouts, login requirements, and certificate issues; read the reason before deciding.

Recheck edits and choose a maintenance interval

Correct your own typos and use a new official location when equivalent material has moved. If the source disappeared with no replacement, review claims relying on it rather than merely removing the hyperlink. When a working resource only rejects automated checks, document the reason, use a suitable exclusion, and revisit it occasionally.

Open the edited public article and verify link text, destination content, images, and video playback before rechecking the item. For replacements across several locations, inspect shared menus and synced patterns as well as posts. Preserve the earlier URL and wording so an incorrect change can be reversed.

A small blog can check when publishing or substantially editing content, adding periodic reviews for reference-heavy articles. There is no need to scan everything repeatedly each day. Consider hosting resources, cloud allowances, and external rate limits, and verify scheduled jobs actually run. If using email reports, test notification delivery too.

Start with important visitor-facing links, dead addresses repeated widely, and external sources supporting key claims. Link maintenance helps readers reach information; lowering an error count does not guarantee higher search rankings. Combine automated findings with editorial review of the actual content.