Red Hat Bugzilla – Bug 809194
404 Response Codes from Internally Linked URLs
Last modified: 2015-05-14 21:07:42 EDT
Created attachment 574576 [details]
List of URLs responding with a 404 code
Description of problem:
Several (currently 33) internal links on the OS community site are returning 404 (file not found) response codes when accessed.
Version-Release number of selected component (if applicable):
Visit any of the 33 URLs in the attached .csv file.
Steps to Reproduce:
1. Visit any page on the list of URLs (e.g. https://www.redhat.com/openshift/community/documents)
404 response code
Active page on https://www.redhat.com/openshift/community/
This data was accessed via a Google Webmaster Tools crawl report.
Issues affect both SEO and user experience (broken links).
Any links to (e.g.), "OpenShift_Express-*" need to be replaced with the latest versions, already published on the Community site, that no longer use "Express" as part of the name.
Lowering the severity since this is not related to source code so this don't block stg build. Drupal content changes right in production.
This is only a bug if the related URLs are linked *from* any of our pages. Please note that GWT reports every 404 *including* the URLs linked only from external sites that links to us.
For some of the most important ones we can create redirects in order to keep important external articles or blog posts working. But for most of them, it would be nice to know which of our own pages links to those that are returning 404. Is that kind of information available?
Internal link information is available within the GWT UI for each of these URLs, but is not easily exported. I can give you direct access to the data via a Google account if that works.
(In reply to comment #4)
> Internal link information is available within the GWT UI for each of these
> URLs, but is not easily exported. I can give you direct access to the data via
> a Google account if that works.
It does, my google account is: firstname.lastname@example.org.
(In reply to comment #5)
> (In reply to comment #4)
> > Internal link information is available within the GWT UI for each of these
> > URLs, but is not easily exported. I can give you direct access to the data via
> > a Google account if that works.
> It does, my google account is: email@example.com.
Great - you now have access via http://www.google.com/webmastertools.
Information is under Diagnostics >> Crawl Errors. Click on a specific URL to access internal link information on the 'Linked From' tab.
The most important 404s has been fixed with URL redirects right in production. Examples:
* /documents to /documentation
* /forums/express to /forums/openshift
* all guides and documents
* broken FAQs
* broken feature requests
* many others
We can expect them to be removed from GWT Crawl Errors in some time. The ones related to forums threads has not been fixed when we understand the threads has been closed (not Express to OpenShift renaming problems), in that case a 404 is actually expected.
(In reply to comment #7)
According to your comments, tested this bug on product, it has been fixed now, thanks.