=== WP Broken Link Status Checker ===
Contributors: seedplugins, pauiglesias
Tags: broken links, broken, links, crawler, headers, http, nofollow, redirections, scan, status, checker, url
Requires at least: 3.4
Tested up to: 4.4.2
Stable tag: 1.0
License: GPLv2 or later

Check HTTP status response codes of all your content links and images, looking for broken links, redirections, nofollow links, etc.

== Description ==

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 once a scan is configured you can start the crawler from the same 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 detected according to the scan configuration, allowing basic filtering options.

You can read a detailed user guide and the documentation from the plugin page:

http://seedplugins.com/wp-link-status/

== Installation ==

Install from WordPress

1. Visit the Plugins page from your WordPress main menu and select Add New link
1. Click on Upload plugin, next Browse, choose wp-link-status.zip and press Install Now.
1. Once uploaded and install click Activate Plugin
1. 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
1. Activate the plugin through the 'Plugins' menu in WordPress
1. Get started from the WP Link Status menu

== Frequently Asked Questions ==

= 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.

== Screenshots ==

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

== Changelog ==

= 1.0 =
Release Date: February 11th, 2016

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

== Upgrade Notice ==

= 1.0 =
Initial Release.