{"id":594,"date":"2014-01-22T12:17:00","date_gmt":"2014-01-22T12:17:00","guid":{"rendered":"http:\/\/www.urlrate.com\/blog\/?guid=b426ff4b33e38e66a8fdf979228a23b3"},"modified":"2014-01-23T21:22:36","modified_gmt":"2014-01-23T21:22:36","slug":"changes-in-crawl-error-reporting-for-redirects","status":"publish","type":"post","link":"https:\/\/www.urlrate.com\/blog\/changes-in-crawl-error-reporting-for-redirects\/","title":{"rendered":"Changes in crawl error reporting for redirects"},"content":{"rendered":"<div dir=\"ltr\" style=\"text-align: left\">\n<p>Webmaster stage: intermediate-advanced<\/p>\n<p>Prior to now, we&#8217;ve got considered occasional confusion by means of webmasters relating to how <a href=\"https:\/\/support.google.com\/webmasters\/answer\/35120\">crawl blunders<\/a> on redirecting pages have been proven in <a href=\"https:\/\/www.google.com\/webmasters\/tools\">Webmaster Instruments<\/a>. It&#8217;s time to make this somewhat clearer and more uncomplicated to diagnose! While it was that we&#8217;d report the error on the original &#8211; redirecting &#8211; URL, we will now exhibit the error on the ultimate URL &#8211; the one who in truth returns the error code. <\/p>\n<p><\/p>\n<p>Let us take a look at an instance:<\/p>\n<p> <img decoding=\"async\" border=\"0\" src=\"http:\/\/1.bp.blogspot.com\/-Nu8oByVfZ_w\/Ut-10G6bZ0I\/AAAAAAAAAZ8\/WzTWyUQKGPc\/s1600\/crawl-error-403-410-404-500-503-http-errors-failures-keyword-keywords-words-keys.png\" \/> <\/p>\n<p>URL A redirects to URL B, which in flip returns an error. The kind of redirect, and type of error is unimportant here. <\/p>\n<p>Up to now, we would have suggested the error noticed on the end below URL A. Now, we will instead record it as URL B. This makes it so much more uncomplicated to diagnose the crawl errors as they&#8217;re shown in Webmaster Tools. The usage of instruments like <a href=\"https:\/\/www.google.com\/search?q=curl\">cURL<\/a> or your favourite <a href=\"https:\/\/www.google.com\/search?q=http+header+viewer\">online server header checker<\/a>, which you could now simply verify that this error is in reality happening on URL B. <\/p>\n<p>This modification can also be visible in the complete error counts for some internet sites. As an instance, in case your site is moving to a brand new domain, you can simplest see these mistakes for the new area (assuming the old domain redirects correctly), which might lead to considerable changes within the total error counts for these web sites.<\/p>\n<p>Note that this modification only impacts how these crawl blunders are shown in Webmaster Instruments. Also, take into account that having crawl error for URLs that will have to be returning errors (e.g. they do not exist) <a href=\"http:\/\/googlewebmastercentral.blogspot.com\/2011\/05\/do-404s-hurt-my-site.html\">does no longer negatively affect the remainder of the website&#8217;s indexing or rating<\/a> (additionally as <a href=\"https:\/\/plus.google.com\/+JohnMueller\/posts\/RMjFPCSs5fm\">discussed on Google+<\/a>).<\/p>\n<p>We hope this transformation makes it slightly more straightforward to track down crawl error, and to scrub up the unintentional ones that you simply weren&#8217;t aware about! When you have any questions, be at liberty to submit right here, or drop by within the <a href=\"https:\/\/productforums.google.com\/forum\/#!categories\/webmasters\/webmaster-tools\">Google Webmaster Lend a hand Discussion board<\/a>.<\/p>\n<p> <span class=\"byline-author\">Posted with the aid of <a href=\"https:\/\/google.me\/+johnmueller?rel=author\">John Mueller<\/a>, WebSite Error Analyst<\/span><\/div>\n<div class=\"feedflare\">\n<a href=\"http:\/\/feeds.feedburner.com\/~ff\/blogspot\/amDG?a=gWbN-62JpnI:XYeN2MjTWz4:yIl2AUoC8zA\"><img decoding=\"async\" src=\"http:\/\/feeds.feedburner.com\/~ff\/blogspot\/amDG?d=yIl2AUoC8zA\" border=\"0\"><\/img><\/a>\n<\/div>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/feeds.feedburner.com\/~r\/blogspot\/amDG\/~4\/gWbN-62JpnI\" height=\"1\" width=\"1\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Webmaster level: intermediate-advancedIn the past, we have seen occasional confusion by webmasters regarding how crawl errors on redirecting pages were shown in Webmaster Tools. It&#8217;s time to make this a bit clearer and easier to diagnose! While it used&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[50,62,49,55],"tags":[],"class_list":["post-594","post","type-post","status-publish","format-standard","hentry","category-advanced","category-crawling-and-indexing","category-intermediate","category-webmaster-tools"],"_links":{"self":[{"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/posts\/594","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/comments?post=594"}],"version-history":[{"count":1,"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/posts\/594\/revisions"}],"predecessor-version":[{"id":601,"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/posts\/594\/revisions\/601"}],"wp:attachment":[{"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/media?parent=594"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/categories?post=594"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.urlrate.com\/blog\/wp-json\/wp\/v2\/tags?post=594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}