• Resolved Gal Baras

    (@galbaras)


    I’m getting most of the “failures” from sites that reject connections with the 403 HTTP status. This can be resolved either by changing the way the plugin connects, or circumvented by excluding 403 from being reported.

    Is there a way to do either with the local checker?

    If not, can the authors please introduce a way to exclude 403 from being reported?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Jair – WPMU DEV Support

    (@wpmudevsupport15)

    Hello @galbaras

    At this moment, the Local version of Broken Link Checker doesn’t have a function to exclude notifications or alerts when the plugin can’t access a link with a 403 error message. Usually this error message appears when the crawler can’t load a page because the access is forbidden. For the Cloud-based Link Checker, this can be solved by adding the Broken Link Checker IP addresses found in our documentation:
    https://wpmudev.com/docs/getting-started/wpmu-dev-ip-addresses/

    The Local Link Checker works inside your site, as a plugin, it shouldn’t be blocked by the site or a firewall of the site when it checks links of your site. But it can be occasions where you have a link pointing to another site, and the crawler can’t check it because that other site blocks it. In the case you get a notification like that, confirm that the link effectively loads for you, and then add that link in the exclusion list by going to Link Checker -> Settings -> Which Links to Check -> Exclusion list.

    If that doesn’t work for you, please share us more information about what kind of errors or alerts are you getting, if the broken link is from your site or an external site, and if adding that link to the exclusion list doesn’t work.

    Kind regards,
    Jair.

    Thread Starter Gal Baras

    (@galbaras)

    Well, it seems like many popular sites, like freepik.com, pixabay.com and news sites, block the local checker, even when it checks a single page. This could mean that the user agent is deemed to be a bot and disallowed, but this type of error has never been real in years of running the plugin.

    If the plugin cannot filter out 403 errors right now, please add this option, because I will happily use it.

    This can be added as a PHP filter for advanced users, if you’re concerned about novices making mistakes.

    Thank you.

    Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hi @galbaras

    I will share your feedback with our development team. I hope we can implement it in future updates.

    However I can’t give you any promises or ETAs.

    Best Regards
    Amin

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @galbaras

    Since we have acknowledged this will be improved in a future update, I’ll mark it as resolved for now.

    For new feature updates, you can get notifications on our progress by subscribing to our roadmap at https://wpmudev.com/roadmap/

    Once new versions are released, any pertinent changes will be described in the changelog, which you can find at:

    https://ww.wp.xz.cn/plugins/broken-link-checker/#developers

    Kind Regards,

    Nithin

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.