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:
- 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.
Even installing plug-in created 504 Gateway Timeout error. Installing, running and deleting each required repairing and optimizing my database tables through phpMyAdmin because each prevented me from accessing site admin afterward. Had to delete plug-in through FTP due to 504 error.
tested on wp 4.7.2 and woocommerce last version and it works perfectly, thanks!
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.