Find and fix broken links in WordPress without the guesswork
Broken Link Scanner checks links in posts, pages and supported page-builder layouts, shows what failed and why, and lets you replace a broken URL from one clear dashboard dialog.
- Scan one page, selected content or all visible items on the current list page.
- Detect links in Bricks, Elementor and other stored layouts.
- Distinguish broken links from warnings and redirects.
- Fix URLs in place or schedule recurring scans.
What is Broken Link Scanner for WordPress?
Broken Link Scanner is a TheOneWP module that discovers stored hyperlinks inside enabled WordPress posts, pages and public custom post types. It checks internal destinations against WordPress where possible, tests other URLs over HTTP, and separates working, broken, warning and not checked results. Scans can run from visible content list rows or on a configurable WP-Cron schedule. Each affected URL can be corrected from the results dialog, while optional list highlighting and filtering make problem pages easier to revisit. The module is a content-level scanner, not an unrestricted site crawler.
Links break quietly. Visitors notice first.
A page can look perfect while its buttons, resources and external references lead nowhere.
URLs change after the page is published
Someone deletes an article, renames a path or shuts down a service. Your existing page does not receive a warning, so the obsolete link remains visible.
An HTTP response does not always tell the full story
A 404 and a 403 are not the same problem. Anti-bot protection, unpublished internal content and redirect chains need different treatment.
Page builders hide links outside the normal editor content
A link inside Bricks or Elementor may live in saved layout metadata, not in post_content. Looking only at ordinary post HTML misses part of the picture.
From a dead URL to a clear next action
Scan content from the familiar WordPress list, read the reason behind each result, and repair the address without hunting through the page.
Find problems before visitors do
See dead destinations, unavailable internal pages and suspicious responses without opening every link manually.
Scan where you already work
Run Check Links on a post row, a selected batch of items, or all visible rows on the current content list page.
Correct the address in place
Replace a stored URL from the results dialog, including matching occurrences in supported builder layouts.
More than a list of HTTP errors
Each capability below is implemented in the supplied Broken Link Scanner class, dialog JavaScript or module settings.
Single-item and bulk scans
Use the Check Links action beside a content item, or the list badge to scan selected rows or all visible list items.
Optional scheduled scanning
Scan enabled post types periodically using a resumable WordPress cron queue rather than one open-ended request.
Builder-aware link discovery
Reads stored content, expanded blocks, common shortcode formats and saved layouts from Bricks, Elementor, Beaver Builder and Oxygen.
Meaningful link status
Distinguishes working, broken, warning and skipped links, including redirects and unpublished internal destinations.
Inline URL replacement
Change an address throughout the current content item and the supported builder data that stores it.
Highlight, filter and trust rules
Optionally mark broken items in content lists, filter to those items and trust URLs or domains that block automated checking.
Where a broken link check saves the most work
Not every problem appears in a search console or a visitor report. Content-level scans provide another way to find it.
Reviewing a site after migration
Spot old internal paths and external resources that may no longer resolve after moving or restructuring a site.
Maintaining a content-heavy website
Periodically revisit resource pages, tutorials and older articles where third-party destinations change over time.
Auditing a page-builder project
Inspect links saved in visual layouts and shortcode attributes without relying only on the content editor's text field.
Fix the right link. Not every flagged link.
A useful scanner helps you decide which URLs genuinely need replacing rather than treating every unusual server response as a dead destination.
Work in small batches, not one giant timeout
The module places explicit bounds on checks, cached results and scheduled work.
Five URLs per request
On-demand scans send a maximum of five distinct addresses per checking request. An individual remote request has an eight-second timeout.
Six-hour answer cache
Previously checked addresses reuse a stored verdict for six hours unless you explicitly choose Scan Again.
Scheduled work has limits
Each scheduled pass processes at most five content items with a 25-second time budget. A scheduled run includes up to 500 recently modified published or private items.
Controlled requests, careful link handling
Scanning URLs means contacting outside servers. The module includes permission checks and bounded network behavior for that work.
Authenticated, nonce-protected AJAX
Scan and replacement requests require a logged-in WordPress user, a valid module nonce and sufficient capabilities.
Permission checks on the exact post
Reading or rewriting an individual content item's links additionally requires the user's edit_post capability for that item.
Safe requests for external addresses
External URL checks use wp_safe_remote_head() and, when needed, wp_safe_remote_get(). Redirects are followed explicitly with a five-hop cap.
Only explicit URL corrections
The module validates the replacement address before writing it. It updates supported stored fields and invalidates relevant cached builder output; it does not invent destinations.
Reads where WordPress content actually keeps links
Support is based on specific stored formats in the supplied implementation, not an assumption that every widget from every builder is detectable.
Posts, pages, public custom post types
Select public content types in settings. The scanner reads stored HTML and expands blocks before collecting links.
Bricks, Elementor, Beaver Builder, Oxygen
Reads known builder metadata keys and nested link settings, including builder elements that store links away from regular post content.
Divi, WPBakery, Avada and other shortcode links
Extracts URL attributes and addresses from common shortcode structures. It does not guarantee coverage of proprietary or runtime-generated links.
TheOneWP versus checking links manually
A straightforward comparison with opening and testing URLs one at a time, rather than unverified claims about competing plugins.
| Task | TheOneWP Broken Link Scanner | Checking manually |
|---|---|---|
| Collecting links | Reads stored page links and supported builder data | Find each link in the rendered page or its editor |
| Testing destinations | HTTP results and WordPress-aware internal checks | Open and interpret each destination yourself |
| Investigating warnings | Separates broken, warning, working and skipped | Infer why a website refused, redirected or failed |
| Replacing old URLs | Correct a stored address from the scan dialog | Locate and edit the address where it was saved |
| Rechecking over time | Optional scheduled scans with stored summaries | Repeat the same checks whenever you remember |
Find, inspect and repair links in four steps
Start with the types of content that matter most, then review the status and destination before changing anything.
Enable the module
Open TheOneWP's SEO settings, activate Broken Link Scanner and select which public post types can be checked.
Run a scan
Choose Check Links on one item, use the badge to scan selected rows or all items visible on that list page, or enable a recurring WP-Cron scan.
Review the results
Read working, broken and warning statuses. Look at link text, source context and HTTP details before deciding what requires a fix.
Correct and verify
Use Correct this address for a real error. Scan Again to request a fresh verdict, then check the updated page.
Treat scan results as diagnostics, not guesses
Use the results to make informed corrections and keep scans proportionate to the size and activity of your site.
Start with high-value content types
Select the pages, posts and public custom post types your visitors use. Expand scan coverage only where you need it.
Investigate warnings before replacing a link
A protected external website may work normally for visitors while returning 403 or 429 to automated requests. Verify it in your browser first.
Choose a realistic scan interval
The default is weekly. On sites with many links, give WP-Cron time to complete queued work before scheduling another run.
Use trusted-address rules sparingly
A whitelisted domain is counted as working without a request. Reserve trust rules for known false positives rather than hiding real errors.
Three assumptions that cause bad fixes
A link status tells you where to investigate, not automatically how to repair it.
Calling every 403 a dead link
A firewall may block automated requests. The module treats these responses as warnings, not proof the page has disappeared.
Expecting a full crawler
Broken Link Scanner checks links found in selected stored content. It does not crawl every reachable frontend route or a whole site's scripts.
Assuming scheduled scans are unlimited
A scheduled run is capped at 500 recently modified published or private items and depends on WordPress cron execution.
Broken Link Scanner FAQ
Practical answers based on the actual TheOneWP module implementation and settings.
What does Broken Link Scanner do?
It finds links stored in enabled WordPress content, checks whether their destinations respond, and displays working, broken, warning and not-checked results. You can correct a URL directly from the scan dialog.
Can it check an entire WordPress site?
You can scan all items visible on the current list page or choose individual rows. Scheduled scans cover up to the 500 most recently modified published or private items across enabled post types per scheduled run. It is a content-link scanner, not a full-site crawler.
Does it work with WordPress page builders?
It reads saved layout data for Bricks, Elementor, Beaver Builder and Oxygen, and it can extract link addresses from shortcode content used by Divi, WPBakery and Avada. Coverage depends on how the builder or widget stores its links.
Does it check internal and external links?
Yes. For internal URLs that resolve to a WordPress post, it checks the post record and publication status. Other URLs are checked through HTTP requests, including external links.
What does Worth a look mean?
A link may need attention without being confirmed broken: for example, a destination returns 403 or 429, points to unpublished content, or follows a long redirect chain.
Can I fix a broken link without editing the whole page?
Yes. The Correct this address action replaces that URL throughout the selected content item and supported saved builder layouts. Check builder-managed references separately if they are not stored as literal addresses.
Will it automatically repair broken links?
No. It identifies issues and provides a manual URL replacement action. It does not guess a new destination or rewrite addresses without your confirmation.
How often can automatic scans run?
Scheduled scanning is optional. When enabled, the default interval is seven days (604800 seconds); you can enter another interval in seconds, with a minimum of 60.
Can a protected website cause a false positive?
Yes. A firewall, anti-bot rule or rate limit may deny automated checks even when the page works in a browser. Such HTTP responses can be classified as warnings. Trusted addresses or domains can also be excluded from HTTP checking.
Are link results cached?
Yes. URL-check verdicts are cached for six hours. Scan Again asks the destinations again rather than using the cached verdicts.
Will it slow down my WordPress dashboard?
On-demand checks run in batches of up to five addresses. Scheduled scans process no more than five content items per pass, with a 25-second time budget, then queue another pass when needed. External network response times still vary.
Which permissions are required?
The AJAX requests require a logged-in user, a valid nonce and edit permissions. Scanning or changing a particular content item additionally requires edit_post permission for that item.
Broken links should not be invisible.Find them. Fix them.
Check WordPress content links, see why a destination failed, and correct stored URLs without adding another single-purpose tool to your workflow.

