Google Bot Error 500

for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of how to fix crawl errors in google webmaster tools this site About Us Learn more about Stack Overflow the company Business

Google Crawl Errors Pages Don T Exist

Learn more about hiring developers or posting ads with us Webmasters Questions Tags Users Badges Unanswered Ask Question _ Webmasters Stack Exchange is a question and answer site for pro webmasters. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Google Webmaster Tools - Crawl errors with 500 status code up vote 1 down vote favorite I will try to explain the situation: In December 2012 I deployed a website with a sitemap.xml, etc... there were circa 2000 URLs. After a while I changed something on my website, upgrading my pages to circa 30,000 and I deployed again updating the sitemap.xml. I also updated the routing of my urls: ie: from mysite/id=myName to mysite/id/my-name. Now for some reason I'm receiving from Google Webmaster Tools 8 crawl errors with a 500 status code on some pages with an old URL... how can it be possible? And how can I fix it? google google-webmaster-tools web-crawlers http-code-500 crawl-errors share|improve this question edited Mar 8 '13 at 12:50 Simon Hayter♦ 21.4k43279 asked Jan 9 '13 at 23:05 Andrea Turri 12113 Can you please clarify... "WebMasterTools of Google 8 errors 500"? "Google 8"? "8 errors"? "500 errors"? "500 pages"? "8 errors with an HTTP status code of 500"? –w3dk Jan 9 '13 at 23:37 ...8 errors. Server error 500... –Andrea Turri Jan 10 '13 at 13:01 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote The problem with 500 (Internal Server) Errors are that they are generic errors when the server is unable to return a valid response and no other error is app

Part 1, then check out Part 2 & Part 3). Gateway timeout... File not found. Authorization Required. Forbidden! INTERNAL SERVER ERROR! If search bots are spending time on your site just running into walls and spinning around in circles, that's time they won't be spending crawling your carefully-optimized content, and as we know from part 1 of this series , the more often Googlebot crawls a page, the better that page will rank. But persistent HTTP errors and other bot-confounding behaviors just squander your crawl budget, limiting the potential for improvement elsewhere. In this installment, we'll look at the http://webmasters.stackexchange.com/questions/41008/google-webmaster-tools-crawl-errors-with-500-status-code different types of crawl errors, what they mean, and how to discover and monitor them on your site. Broken links Broken links just happen. Writers mangle links while editing content. Developers mangle links when the logic to auto-generate those links fails to account for some potential condition (or if they're just ignorant of basic on-page technical SEO). With multi-user CMS environments, people fat-finger the delete button or change settings that can http://www.dirigodev.com/blog/seo-web-best-practices/crawl-errors-increasing-googlebot-crawl-budget-part-4 cause important pages to suddenly go missing and return "404 Not Found" errors. The bots will follow these links repeatedly. 404s are okay in and of themselves; they're not going to hurt your rankings unless more of your indexed pages are returning 404 than not (e.g., high-turnover content like individual URLs of for-sale listings, or large-catalog e-commerce with fluctuating availability). Outside of such extreme cases, Google knows that accidents happen and will re-crawl previously-good URLs that have gone 404 just in case they've come back. That's a great service, but your site's crawl budget is still eroded by every request that Googlebot spends handling an error response instead of discovering valuable content, so it's obviously important to monitor 400-level errors and resolve whatever you can so they stop happening, whether that's restoring content on that URL so it can return 200, or 301-redirecting it to a functioning URL with similar content in order to preserve the page authority that the now-404ing URL had accumulated. Google does a decent job of detecting and reporting "soft 404s", where the site responds to a request for a non-existent URL with a temporary redirect (302 instead of 301) to a page that reads like a 404 page but returns 200 instead. Many CMSes do this automatical

Start here for a quick overview of the site Help Center Detailed answers to any http://serverfault.com/questions/359662/iis-7-5-why-googlebot-receive-500-internal-server-error-from-website questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and crawl errors network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top IIS 7.5 - why Googlebot receive 500 internal server error from Website? [closed] up vote 0 down vote favorite google bot error I have a problem: when googlebot come to website pages where is login form - it reveice error from site ("ureachable" in webmaster tools). This error is N500 HTTP/1.1 500 Internal Server Error Cache-Control: private Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Date: Sat, 11 Feb 2012 07:56:20 GMT Content-Length: 4855 When googlebot visit pages without login form - it receive ok (status 200) When I visit website page through browers - everything is ok in all pages (with login forms and with it). My system: Windows Web Server 2008 R2 (x64) Application pools: ASP.NET 4 - Managed pipeline mode: "Integrated" ISAPI and CGI Restrictions: ASP.NET 4.0.30313 (32-bit): Allowed IIS 7.5 I have only one version ASP.NET Web.config (part): Failed Request tracing log (part) :