Receiving 4XX status codes

[MikeRoberts]

Normally the reports will let you know what page the error was encountered on and/or originated from. If there's an error listed there then odds are either the crawl found a broken link within your site that returned a 404 Not Found or you have something that was blocked returning a 403 Forbidden. Have you run any other crawls of the site (such as with Screaming Frog) or checked Google Search Console to see if there are any crawl errors listed on the site?

[janee]

I cannot replicate the issues on any other crawls. That is why I'm asking...

[MikeRoberts]

Where did the original report say the error was coming from? Does the originating URL return a 4xx error if you go to it manually?

[janee]

The report came from SEO moz and cannot be replicated and no more information is provided. It seems like a dead end to me...

[MikeRoberts]

Yes, I understand that much. But in the actual report from MOZ, if you had any 4xx error it will tell you in the report the exact URL that returned the error. If there was no URL listed then you had no URLs found returning that error.

[janee]

it is saying (it's own url) could it be?

[OlegKorneitchouk]

screenshot?

[janee]

Thanks!

4xx.tiff

[janee]

then view issue:

High Priority Issues

Found on 2016-06-16

4XX (Client Error)

4XX status codes (i.e., a 404 Not Found error) are shown when the client requests a page that cannot be accessed. This is usually the result of a bad or broken link. These issues should be kept to a minimum if possible. Make sure no internal links on your site are broken. For external links to your site, try contacting the linking site's owner and asking them to fix or update the link. For detailed descriptions of these errors and information regarding fixes for these errors, please visithttp://moz.com/learn/seo/http-status-codes.

[OlegKorneitchouk]

Ran another crawler and didn't see any issues so I think you should be good technically.

I also ran a stress test and there were times when the VU couldn't access the page (although generally this would throw up another error code, could be the reason for the 406).

https://app.loadimpact.com/load-test/e7aad2c2-5abc-4d0f-9206-bc155dffc706?charts=type%3D1%3Bsid%3D__li_clients_active%3A1%3BdataKey%3Dvalue%3B%3Btype%3D1%3Bsid%3D__li_user_load_time%3A1%3BdataKey%3Dvalue&large-charts=type%3D1%3Bsid%3D__li_clients_active%3A1%3BdataKey%3Dvalue%3B%3Btype%3D1%3Bsid%3D__li_user_load_time%3A1%3BdataKey%3Dvalue

[tawnycase]

Hi there! Tawny from the Help Team here. It looks like, from this screenshot, the referring URL does not contain the www - it could be that there's something not quite right about the redirect from http://premier-hd.com/ to http://www.premier-hd.com/ that's tripping up our tools.

I found this article about 406 HTTP status codes that might be helpful to you: http://www.hostingflow.com/http-error-406-not-acceptable/

It might be worth going over what you're seeing in your Site Crawl section with your web developer or whoever manages your web page for you. They'll be in a good position to help you address the issues that Site Crawl brings up.

I hope this helps! If you have more questions, feel free to write in to help@moz.com and we'll do everything we can to assist you!