Este plugin não foi testado com as 3 últimas grandes versões do WordPress. Pode já não ser suportado e pode ter problemas de compatibilidade quando usado com versões mais recentes do WordPress.

WP Broken Link Status Checker


This plugin is a broken link checker utility organized through entities called scans, each one containing its own configuration and results.

Start creating a new scan and configure it, and once a scan is configured you can start the crawler from the same scan edit page, or run it later from the scans list screen.

Knowing that these crawling processes can hurt your server perfomance, we have tried to put the focus on performance impacts, without performing massive data queries or updates, and not prioritizing crawler activity ahead of real visits.

Once started, you can see results inmediately without having to wait for the scan to be completed. You can access to the results page doing a click in the scan name, or clicking the “Show results” link from the scan actions row.

The crawler results page shows all links checked according to the scan configuration, allowing basic filtering options.


– There are links not checked

Note that this plugin works only with the editable content of your posts, pages or post types, it does not scan the entire HTML page, it just extract the links and images from the entry content (the content you usually edit via the WP Editor for posts and pages).

– Firewall plugins

If you are using the Wordfence plugin, in order to work properly you need to deactivate their Firewall module (even temporarily). Go to the Wordfence menu Firewall, and from the Firewall Status pick Disabled and click the save button. After the scan is complete, you can activate the firewall again.

In the same way, we have detected a conflict with All In One WP Security & Firewall plugin and its Brute Force module, so it is necessary to deactivate these options before play this plugin.

Another issue also detected with the WP Secure plugin, you need to deactivate this plugin in order to run the scan properly.

– Hosting restrictions

Some users have reported issues for GoDaddy hosting due restrictions for sites with HTTPS enabled and the cURL module (an internal server module used to make HTTP requests to check the links) for some hosting configurations. It seems that GoDaddy applies limits for this module via proxy or similar. This is a hosting-level problem, so this plugin have nothing to do to solve it.

– WordPress MultiSite

This plugin does not support network activation for WordPress Multisite, so in case of multisite installs it needs to be activated per each blog individually. Also it is recommended to run only one scan per blog at the same time to prevent server performance issues.

– File permissions

This plugin just creates one file called wp-link-status-salt.php directly into the wp-content directory, so that directory must be writable by the web server (recommended 755 permissions). The CHMOD is used to ensure the right permissions 0644 to the file (not the directory) according the WordPress permissions scheme:

– Support and documentation

Pro version provides extended search filters and the possibility to edit the post content links directly from the search results without using the WP editor, including bulk actions mode for most operations:

You can read a detailed user guide documentation from the plugin page that describes also the Pro version features:


  • Scan basic configuration
  • Scan content options
  • Scan URL filters
  • Scan HTTP status selection
  • Scan advanced options
  • Main scans list
  • Crawler results page


Install from WordPress

  1. Visit the Plugins page from your WordPress main menu and select Add New link
  2. Click on Upload plugin, next Browse, choose and press Install Now.
  3. Once uploaded and install click Activate Plugin
  4. Get started from the WP Link Status menu

Or upload via FTP

  1. Unzip and upload wp-link-status folder to the /wp-content/plugins/ directory
  2. Active o plugin no menu Plugins
  3. Get started from the WP Link Status menu

Perguntas frequentes

Do I need to keep the browser opened, or a WordPress user session active during the crawling process?

No, it is not necessary. The crawler module runs in background and it is intended to work in unattended mode.

How the crawling process affects to server performance?

There are several mechanisms to avoid constant database access. When a URL is found, the crawler stops extracting URLs from content and check the detected URL. In addition, in the settings page you can manage many parameters related to performance. Let me known if you experience any issue.

Why the crawler does not work and show “Waiting…”?

The crawler module works submitting HTTP requests through internal plugin scripts. So if you are running this plugin under an environment outside the Internet (e.g. local or development server) you need to add the involved hosts names or domains into your hosts file, both the client and server where this plugin is executed.

In the same way, if the site you are crawling implements browser password protection, you need to remove this password restriction in order to work properly.

Another issue happens with security plugins, we have detected problems with plugins like Wordfence, All In One WP Security & Firewall, and WP Secure (there maybe others). So if you have issues you need to deactivate these plugins in order to run the crawler properly.

I have activated this plugin from a multisite but seems that it does not work.

Currently there is no support for network activation in multisite installs. The plugin needs to be activated locally for each single blog of your multisite. Otherwise, it is advisable to run only one scan at the same time per each blog or web server.

This plugin works for ACF or Advanced Custom Fields as well?

Yes, at the end ACF works the same way that normal custom fields, as long as the ACF value for a custom field does not use special data structures (like serialized array values, per example).

You can add the custom field name in the “Content options” tab of the scan, selecting if it is an expected full URL or a content with links.


18 de Setembro, 2019
I've tested several similar plugins. All were rubbish. Either they did not work, or the UI was not useful for my needs. It seems to do a great job of finding links. I really like the ability to Filter results. Also Settings allow you to check only certain post types, or "status codes", if you like. It's a great group of settings. It's also nice to be able to change settings and save the results under a different name. You can then go back and look at results from past "runs", or delete any "run" that you no longer need to reference. That is a useful touch. There is no text file output that I saw, though perhaps looking in the database could yield the same, or one could copy/paste the results from any search into a text file, I presume. However, given the results format, and the fact that past "runs" are always accessible, I do not find a text file to necessary. The only feature that some other plugins offer, that is not available in this plugin, is the ability to edit the "bad url" directly from the list. Clicking on the listed broken url will not allow one to edit it, and have it saved directly inside the page that the url was listed. However, the page containing the url is listed next to the page, alongside links to edit that page or simpy view that page. Since the full "broken" url is visible in the list, it's easy to Copy the bad url, then FIND it inside the source page. This is makes it easy enough to update links! Given the overall design of this plugin, this feature thatt's offered elsewhere is not really missed. So Far, I am really enjoying this plugin. It's well designed, and works well. Even though this plugin hasn't been updated in 6months, and is not certified to work with recent versions of WordPress, I've run into no issues. I'm not yet tested it on WP 5.2.3 - this particular dev server is a couple versions out of date, yet it works well so far. Thanks Devs!
29 de Julho, 2019
13 de Julho, 2019
This would not run scans for me, the error was unhelpful and generic, something like "that didn't work, try again" I couldn't get much of an understanding for how good this plugin would actually be if it had run, so I am unable to give it a higher rating - I usually don't one star for an error like this. It did seem a bit of an odd plugin to be honest.
15 de Março, 2019
Bravo and thank you for this excellent plugin. As a non-tech-type person, I truly appreciate that it is so easy to use. Keep on keepin' on!
Ler todas as 26 avaliações

Contribuidores e programadores

“WP Broken Link Status Checker” é software de código aberto. As seguintes pessoas contribuíram para este plugin:


Traduza o “WP Broken Link Status Checker” para o seu idioma.

Interessado no desenvolvimento?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Registo de alterações


March 16th, 2019

  • Show a message in activation if any other WP Link Status version is active
  • Changed the way a constant is checked to avoid old PHP versions issues
  • Fixed bug filtering elements attributes on extracting content data
  • More info about debug behavior in the constants.php file


March 7th, 2019

  • Tested with PHP 7.0 and PHP 7.2
  • Tested with WP 5.x and Gutenberg
  • Coding style corrections
  • Fixed several soft bugs
  • Allow activation/deactivation/uninstall without admin area restriction
  • Prevent network-wide plugin activation for multisite installs
  • Remove threads with off status to avoid TEXT field overflow
  • More time to HTTP CURL spawn method to run
  • Improvements in debug and trace mode


September 11th, 2016

  • Fixed cURL options to avoid problems with GoDaddy hosted sites


August 7th, 2016

  • Changed permissions for generated files to avoid hosting conflicts like Hostgator.
  • Fixed crawling process issues when running on HTTPS sites with or without valid certificate.


May 30th, 2016

  • Solved bug for missing Custom Post Types when saving scan data.
  • Solved bug enabling Custom Post Types under scan crawling.


February 25th, 2016

  • Solved config bug when saving a running scan.


Release Date: February 11th, 2016

  • First and tested released until WordPress 4.4.2
  • Tested code from WordPress 3.4 version.