Broken Link Checker for WordPress

Sometimes, links get broken. A page is deleted, a subdirectory forgotten, a site moved to a different domain. Most likely many of your blog posts contain links. It is almost inevitable that over time some of them will lead to a “404 Not Found” error page. Obviously you don’t want your readers to be annoyed by clicking a link that leads nowhere. You can check the links yourself but that might be quite a task if you have a lot of posts. You could use your webserver’s stats but that only works for local links.

So I’ve made a plugin for WordPress that will check your posts (and pages), looking for broken links, and let you know if any are found.

Download it now! (40 KB)

Note : This page, and the feature list below are slightly out of date as a major update has been released recently (see details). I’ll get around to updating this page eventually.

Features

  • Checks your posts (and pages) in the background (whenever the WP admin panel is open ).
  • Detects links that don’t work and missing images. Checks both internal and outbound links.
  • Notifies you on the Dashboard if any problems are found.
  • Link checking intervals can be configured.
  • New/modified posts are checked ASAP.

The broken links show up in the Manage -> Broken Links tab. If any invalid URLs are found a notification will also show up in the sidebar on the Dashboard.

The Broken Links tab displays a list of invalid URLs found along with the relevant posts and the anchor text of the links. “View” and “Edit Post” do exactly what they say and “Discard” will remove the message about a broken link, but not the link itself (so it will show up again later unless you fix it; this plugin doesn’t modify your links).

By default all old posts/links are re-checked every 72 hours, or you can set a different time period.

Notes (Semi-Technical)
I realize there’s a lot of features that could be added to improve this plugin considerably. However, this release is intended to “test the waters” and see if there’s demand for a plugin like this, so I only implemented the most basic functions. The plugin has been upgraded to be slightly beyond “basic” ;)

I thought about using WP’s pseudo-cron to run the link checker by schedule and decided against it. AFAIK the cronjobs execute when a page is requested; since this plugin does some lengthy processing it may increase page load times unacceptably when used in this manner. That’s why I set it to run the checks asynchronously (AJAX) and invisibly in the admin panel.

Installation
Just like any other WordPress plugin -

  1. Download (see below).
  2. Unzip.
  3. Upload the broken-link-checker folder to you wp-content/plugins directory.
  4. Activate the plugin in the Plugins tab.

Upgrading

  1. Deactivate the plugin (important!).
  2. Do steps 1.-3. from “Installation”.
  3. Upload the broken-link-checker folder to you wp-content/plugins directory.
  4. Re-activate the plugin in the Plugins tab.

DownloadCC-GNU GPL
Version 0.5.3 : broken-link-checker.zip (40 Kb)

Requirements

  • WordPress 2.7 or later
  • MySQL 4.1 or later

Starting with version 0.5 this plugin is only compatible with WordPress 2.7 and up. Older versions (e.g. ver. 0.4.14) should work with WP 2.1 – 2.6.x.

Share :
  • Reddit
  • del.icio.us
  • Digg
  • StumbleUpon
  • DZone
  • Ping.fm
  • Sphinn
  • Twitter
Related posts :

1,084 Responses to “Broken Link Checker for WordPress”

Pages: « 1 2 3 4 5 [6] 7 8 9 10 1137 » Show All

  1. 125
    Leo says:

    You can probably use get_permalink, giving it the post’s ID as the parameter. This function is provided by WordPress core.

    Anyway I’ve not tried that yet. Good luck with that! We can find a way out together if you are faced with any coding problem. :)

  2. 126
    White Shadow says:

    Interesting, that seems to work. I’ll have a new version up soon, thanks :)

  3. 127
    Blaenk Denum says:

    Yeah I was about to tell you to do what Leo said, it’s definitely better and more logical.

  4. 128
    jez says:

    hey white shadow, as mentioned in my pioneer (around 10 to 20) comment earlier in the development of your genius plugin – I do still get the unlink error.
    only occurs with images (wikipedia and my own), do you have any idea how to fix that?

    cheers,
    jez

  5. 129
    White Shadow says:

    I didn’t figure it out at first, but now I know it doesn’t work because I haven’t added any specific “image-unlinking” code. So the “Unlink” button only works for links.
    Maybe one day :P

  6. [...] noarchive) along with Nofollow Case by Case. Add in Google XML Sitemaps, Ozh’ Better Feed, Broken Link Checker and PagerFix if/as applicable, for bonus [...]

  7. 131
    [sr] says:

    This is a very cool plug-in but I’m having some trouble with it. It’s constantly reporting many valid URLs as if they were invalid, aside from catching the occasional invalid one. I’ve experimented with the settings to no avail. I’m running 2.5… Any suggestions? Thanks

  8. 132
    White Shadow says:

    It’s possible that those links that are incorrectly reported as broken point to websites that employ some kind of anti-bot protection, which might block the link checker. This has already happened before.

    Another possibility is that the “broken” links load very slowly, so the connection times out and the plugin assumes the links don’t work.

  9. 133
    [sr] says:

    Yeah… I’m seeing it happening now on multiple blogs, each of which aren’t having load time issues and are also running plug-ins like Bad Behavior, AntiLeech and/or others (many of the URLs reported as invalid are internal)… I’ll play with different configurations to try to pin down where the incompatibility lies. thx

  10. [...] Broken Link Checker: And lastly I like this plugin because it shows me what posts have broken links on them so I can correct the problems and eliminate future seo problems because of missing pages! Last 10 posts in Readers QuestionsQuestions Need Answers #1 – May 24th, 2008Advertisments For Technology – April 14th, 2008What Are Authority Sites? – April 3rd, 2008Readers Questions – February 4th, 2008 Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]

  11. 135
    Fabian says:

    Nice plugin! Thanks a lot! I hope that in future version could check broken links in comments too. ;-)

  12. 136
    White Shadow says:

    I’m testing comments to see if the DNS issue is on my end, or somewhere else.

  13. 137
    Piklog says:

    Hi,
    How can i use link checker for rapidshare or mu links?
    Is it work for those?

  14. 138
    White Shadow says:

    @Piklog – I suppose it should work for those as well, but I haven’t tested it.

  15. 139
    Piklog says:

    I’m new wp user, can you test it for me?
    I think RS, MU links are different from direct link checking.
    It’s different.
    thanks :)

  16. 140
    White Shadow says:

    @Piklog – Ah okay, you’re just being lazy here, how hard would it be to add a RS link to a post and see if the link checker catches it? :P

    Anyway, I tested it, and it doesn’t work for them. Apparently RS won’t report the standard 404 HTTP code when a file is missing. Shame on them.

  17. 142
    Anna says:

    Hello! I made the Broken Link Checker translatable.
    It’s here – http://mistress.hweia.ru/2008/06/broken-link-checker/ (the post is in russian, but it’s the only .zip there, hard to miss :)

  18. 143
    White Shadow says:

    @Anna – Thanks. I fixed a few things (that shouldn’t have been translater) and will upload a new version soon.

    By the way, I understand Russian just fine, though I’m not russian myself. ;)

  19. [...] should thank W-Shadow for providing us with this automatic broken link checker plugin for WordPress. And you may also want to check outgoing links using bad neighborhood checker [...]

  20. 145
    tino says:

    After activating I get this:
    Aborting: WordPress API Malfunction
    For some reason the function get_currentuserinfo() did not behave as expected. Your user_level seems to be null. This can be resolved by navigationg to the Users section of the WordPress administrative interface. In this section check the user that you use for administrative purposes. Then under the drop down labled “change role to…” select administrator. Now click the change button. Should you still recieve this error please report this bug to the plug-in author. In your report please specify your WordPress version, PHP version, Apache (or whatever HTTP server you are using) verion, and the version of the plug-in you are using.
    WordPress version: 2.5.1
    PHP version: 4.4.7
    Plug-in version: 2.1.2

  21. 146
    White Shadow says:

    @tino – I don’t have the slightest idea why that happens. Also, I think you’ve got something wrong here, as none of my plugins are currently on ver. 2.1.2

  22. 147
    Cody says:

    I had similar problems as Tino, but mine actually have to do with your plug-in. Despite the fact that I can’t find a post on your site referencing the new version 0.4, I received an update notice on my WP Plugins page. I applied the automatic upgrade and it instantly started kicking out SQL errors about my All-in-one-SEO plugin, which I’ve been using for a long time in conjunction with Broken Link Checker. These errors started the moment I upgraded your plugin, so it appears it conflicts with All-in-one-SEO. I wish it weren’t the case, but as soon as I deleted your plugin off of my server (because I couldn’t access my admin to deactivate first), the SQL errors disappeared. Bummer, ’cause I like your plugin a lot…

  23. 148
    White Shadow says:

    @Cody – It’s all probably caused by the internatialization code which was contributed by someone else (see a few comments below). I don’t know anything about debugging this aspect of WP plugins, so I’m tempted to simply “downgrade” the public version to the code that was in 0.3.9…

  24. 149
    Anna says:

    @White Shadow – Err, I put an internationalisation in, but i18n-ing is just a special markup of text strings and one extra function to tell wordpress where the translation file is. I use All-In-One SEO too and I had no problems with SQL… WTF?

  25. 150
    White Shadow says:

    @Anna – Yes, but it still caused problems for Cody and I, too, have no idea why. I’m quite sure there were no other changes in the plugin aside from i18n-related stuff.

  26. 151
    Anna says:

    @White Shadow – Maybe Cody’s update went wrong – connection errors, access rights or smth like that…

  27. 152
    White Shadow says:

    Maybe, but it doesn’t seem very likely. If the download was corrupted he wouldn’t have been able to extract the ZIP archive (at least not with WP’s automatic upgrade). The plugin worked before, so access rights were okay; there’s most likely no reason why the should have changed with the update.

  28. 153
    koullis says:

    does it checks rapidshare links if they are alive or files have been deleted?

  29. 154
    White Shadow says:

    @koullis – nope, as I mentioned before, it doesn’t work with RS. It would always treat those links as working.

Pages: « 1 2 3 4 5 [6] 7 8 9 10 1137 » Show All

Leave a Reply