Error Code 803
-
Hello all,
With every new Moz report that comes in, an error code 803 appears. I check each link that comes up as an 803 but they work perfectly. What could be causing this to happen?
Error Code 803: Incomplete HTTP Response Received
Your page did not send a complete response to the Moz Crawler's request. Our crawler is pretty standard, so it's likely that other browsers and crawlers may also encounter this error. If you have this error on your homepage, it prevents the Moz crawler (and some search engines) from crawling the rest of your site.
-
I'm also getting these errors so my crawler is pretty much useless to us at the moment lol
-
-- update: the new Moz Pro site crawler is now live, this means we can now crawl your SNI site. If you have any queries please check this post on fixing 803 errors, or reach out to help@moz.com --
Hi there! Kristina from Moz's Help Team here.
Unfortunately at this time our crawler isn't compatible with Server Name Indication (SNI), which appears to be in use on your site. In general, SNI is a totally acceptable security configuration, but our crawler simply isn't equipped to be able to handle these settings.
The good news is that our team has been working hard on a new crawler that will support this configuration and this crawler is currently in its Beta phase. We started this thread to keep our community updated on the progress of our new crawler. If you're interested in being a part of the beta testing, the link to the sign up page is here: http://goo.gl/forms/LCvL9Ix8JDHfbAvr1. Our team will be in contact after you've filled out that form when we are ready to add additional users into the Beta.
We will be rolling the new crawler out to all of our users once it's out of it's Beta phase, but I don't have an exact timeframe of when that will be at this time as it's still being worked on.
In the meantime, I apologize for the inconvenience and let me know if you have any questions or need any additional clarification.
Thank you,
-Kristina
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
API url_metrics Error deserializing POST body
Getting error in https://lsapi.seomoz.com/v2/url_metrics API I'm using Basic Auth for authentication. { "name": "Bad Request", "message": "Error deserializing POST body"} CVW2T4f
API | | verdet32321 -
MOZscape API Signup "An unknown error has occurred"
Hello, I am not able to signup for MOZscape API, I am getting error while signing up for MOZScape API under free trial. https://moz.com/checkout/api --> Getting error here, please help. Thanks.
API | | rahul2k11in0 -
Crawl error HELP!
Hi. I have two campaigns that are constantly giving crawl errors, but in Search Console I don't. How can I do to fix this? The URLs are: https://www.starmeup.com/blog/en/ and https://www.starmeup.com/blog/es/ Thanks
API | | lala20172 -
Moz crawl error? DA & Linking domains significant drop.
Hi guys! Our site www.carwow.co.uk appears to have been punched in the face by the latest Moz update. It's claiming our #linking root domains has dropped from 225 to 135 and has subsequently hit our DA from 38 to 35. We haven't disavowed any links and our off-site strategy has been going well the past 2 months. Search performance has increased by around 15% (around 5k sessions) and rankings have improved week on week. Any idea if this is a Moz error? That's almost a 50% drop in linking root domains. Thanks, James
API | | Matt.Carwow0 -
What is Moz's Error.aspx?aspxerrorpath HTTP Status 302 error message?
Hi, I am not sure what this error message is: "Error.aspx?aspxerrorpath". It immediately follows pages that are given at 302 status in Moz's crawl report. The same pages have never had this error before: | http://www.homedestination.com/news/2013/Minneapolis-home-price-appreciation.html | | http://www.homedestination.com/mortgage-worksheet.html | | http://www.homedestination.com/foreclosure-eligibility.html | Each page has a 100% score with WC3. Could you give me more insight as to what Moz may suggest I do to give the page a 200 HTTP status as before? Thanks.
API | | jessential0 -
Duplicate description error: one for meta one for og:type
I am getting the duplicate description error from Moz. I use both the og:description and . I am not sure if that is going to get me penalized by the search engines or my pages somehow discounted if I have meta description and og:description on the same page. What does Moz recommend? NOTE: for years I have followed this in the best practices format put out from other sources. Found at: http://webmasters.stackexchange.com/questions/52600/should-i-have-ogdescription-and-meta-description-together-on-every-page Short Answer: Use both! Long Answer: The OG stands for Open Graph which is apart of the Open Graph protocol of which works on platforms such as Facebook. The meta description element is for search engines such as Google, Yahoo and Bing. Since these are two separate tags that kinda do the same thing but they are designed for different types of platforms, one for Facebook and the other for Search Engines. The reasoning behind this is that the Open Graph protocal is more rich in what content can be feed to Facebook without scrapping the full page, think rich snippets. So images, description and more information is feed to Facebook via the Open Graph. Using both is a good idea.
API | | jessential0 -
Huge in crease in on page errors
Hi guys I’ve just checked my online campaign and I see errors in my crawl diagnostics have almost doubled from the 21<sup>st</sup> of October to the 25<sup>th</sup> of October going from 6708 errors to 11 599. Can anyone tell me what may have caused this? Also I notice we have a lot of issues with duplicate page titles which seems strange as no new pages have been added, can anyone explain why this might be? I look forward to hearing from you
API | | Hardley1110 -
Batch URL Error 413
Hello, i am using the free mozscape api to get the domain and page authority of urls. i am batching the url as shown in the sample code however i have over 500 URL i need to check and when running the request i get the following: stdClass Object ( [status] => 413 [error_message] => Too many urls in batch. Batches must be less than or equal to 200 urls. ) When i change it to 200 urls the request works fine, now is there a way to enable me to batch all 500 urls at once? i did read that the beta api is capable of batching urls in one request : http://moz.com/blog/400-higher-throughput-mozscape-api-now-in-beta-and-seeking-testers Has this been implemented yet into the current api? Thanks
API | | pauledwards0