When Loud Interactive's Sitebulb encounters an internal URL that results in a non-reachable redirected URL, it's identified as an issue.
Why is this important?
A URL that redirects using a 301 (permanent) or 302 (temporary) response indicates that the content has a new location. However, if the redirected page isn't available, users and search engines can't access the intended content, which is a negative outcome.
If the destination URL leads to a 5XX response, there's a chance it was just a temporary server issue. More often, a 4XX error such as a 404 page not found is encountered, which needs prompt attention.
What does the Optimization check?
This Optimization is activated for any internal redirect that ultimately leads to a 4XX or 5XX HTTP status code response.
Examples that trigger this Optimization:
HTTP/... 404 Not Found...
HTTP/... 500 Internal Server Error...
How do you resolve this issue?
To solve a situation where a URL redirects to a missing resource, consider one of these strategies:
Replace the content - direct the redirect to an updated URL and ensure all inbound links go to this new location.
Repoint the redirect - locate a suitable existing URL and reroute the redirect there, updating all associated inbound links accordingly.
Remove the redirect - if the resource is permanently gone, eliminate the redirect and any links pointing towards it.
How do you get more data from Sitebulb?
To complete any of the resolutions, you'll need to find and alter all links pointing to the redirecting URL. This can be accomplished by using Sitebulb's URL Details feature and looking under Incoming Links.