Hi
we found "broken links" which are not broken, see screenshot.
If they are reported here, they were broken when 4SEO tried to load them. From what I see on the screenshot, I would say they were entered as relative links but I can't be sure. If the link itself is valid, then it may be the server (your server) that blocks 4SEO from loading the page in the end.
What you need to do is select a link and look where the broken link has been found, and then I can look at that page source code, to see how the link was created.
For instance, if you look at the first link, http://www.[redacted].de/datenschutz, 4SEO is correct and it is a redirect. The [redacted].de ones are also redirects, although reported as errors, because that site redirects to the HTTPS version.
It may also be they have firewall that incorrectly detect 4SEO robots as a spammer and block it with a 404 for instance? Again, first step is to know where, on which pages these links are. Then another step would be look at the error log files, which usually will have more information. You can use our free 4LOGS plugin to do that very simply.
are only displayed minutes later. Is there a solution?
Broken links and redirections are found when a page is analyzed. It means, in the background, must load the entire page (by making a request to the website, not just searching the database), then searching for all links in the response from the server and then try to load each of these links to see if they work or not.
If you talk about minutes, then it's a testimony to having 4SEO working well on your website. Commercial services such as ahrefs, Moz, semrush usually takes days to crawl a site (and they do a crawl only every few days, unlike 4SEO which permanently looks for new pages and new links.
You can of course test all links on a page instantantly, for instance by using our free browser extension, SEOInfo. However, it's not a background process, a crawler: the extension only checks the page you're on, after you pressed a button.
Best regards
Yannick Gaultier
weeblr.com / @weeblr