Conversation
supportThe Cloud version of your broken link checker does not properly handle sites which might share a base domain. I have two *separate* sites, both implemented with WordPress: https://www.deepsoft.com/ (my company site) and https://www.deepsoft.com/~heller/ (my personal site). The BLC is getting confused and reporting broken links when scanning my personal site. I think it is confused by relative links. The page I need help with: [ log in to see the link]
Hello @robertpheller I can see what you mean, despite of being two different sites, both share the same domain (www.deepsoft.com) and when you are running BLC in your personal site, and sees a link to your company site, since both are the same domain it will consider it’s also part of the same site. I’m checking this with our development team, in order to investigate more about this issue. Kind regards, Jair.
Hello @robertpheller Broken Link Checker, in The Hub, has an option to exclude URLs by using REGEX rules. You may be familiar with excluding specific pages but with a proper REGEX rule it may be possible to ignore all the URLs from one site when you use BLC in the other site. The option is located in The Hub, by going to the “Link Checker” section, then click on the menu of that page and then click on “Ignore URL Rules”. REGEX rules can be complicated to create and test. I’m providing examples of these rules, which I tested using the Regex101 site, but make sure to test these on your own and make the necessary changes according to your site(s) needs. For your personal site, to ignore all the pages from your company site, the rule can be: ^https:\/\/(www.)?deepsoft.com\/(?!~heller).* For your company site, to ignore all the pages from your personal site, the rule can be: ^https:\/\/(www\.)?deepsoft\.com\/~heller.* These are just examples, but are a good starting point to properly ignore all the unwanted pages. Kind regards, Jair.
This rule hackery should not be needed! It seems to be needed because the cloud-based link checker is missing “knowledge” that the local version gets implicity.
The rules don’t seem to work. I have reverted both sites to the local checker, which seems to work. A big part of the problem is that I am using relative links (ommiting the https://www.deepsoft.com and https://www.deepsoft.com/~heller — the wp-admin/options-general.php page’s “Site Address (URL)” setting). This reply was modified 17 hours, 34 minutes ago by Robert Heller .
Hello @robertpheller I will report this issue to our development team to see how we can improve the Cloud Scanner in the next updates. For now, the best solution is to ignore those links. We will get back to you if we find a better solution. Best Regards, Amin
Hello @robertpheller I can see what you mean, despite of being two different sites, both share the same domain (www.deepsoft.com) and when you are running BLC in your personal site, and sees a link to your company site, since both are the same domain it will consider it’s also part of the same site. I’m checking this with our development team, in order to investigate more about this issue. Kind regards, Jair.
Hello @robertpheller Broken Link Checker, in The Hub, has an option to exclude URLs by using REGEX rules. You may be familiar with excluding specific pages but with a proper REGEX rule it may be possible to ignore all the URLs from one site when you use BLC in the other site. The option is located in The Hub, by going to the “Link Checker” section, then click on the menu of that page and then click on “Ignore URL Rules”. REGEX rules can be complicated to create and test. I’m providing examples of these rules, which I tested using the Regex101 site, but make sure to test these on your own and make the necessary changes according to your site(s) needs. For your personal site, to ignore all the pages from your company site, the rule can be: ^https:\/\/(www.)?deepsoft.com\/(?!~heller).* For your company site, to ignore all the pages from your personal site, the rule can be: ^https:\/\/(www\.)?deepsoft\.com\/~heller.* These are just examples, but are a good starting point to properly ignore all the unwanted pages. Kind regards, Jair.
This rule hackery should not be needed! It seems to be needed because the cloud-based link checker is missing “knowledge” that the local version gets implicity.
The rules don’t seem to work. I have reverted both sites to the local checker, which seems to work. A big part of the problem is that I am using relative links (ommiting the https://www.deepsoft.com and https://www.deepsoft.com/~heller — the wp-admin/options-general.php page’s “Site Address (URL)” setting). This reply was modified 17 hours, 34 minutes ago by Robert Heller .
Hello @robertpheller I will report this issue to our development team to see how we can improve the Cloud Scanner in the next updates. For now, the best solution is to ignore those links. We will get back to you if we find a better solution. Best Regards, Amin