Site Crawl Status code 430

[ianatkins]

Hello,

In the site crawl report we have a few pages that are status 430 - but that's not a valid HTTP status code. What does this mean / refer to?
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors

If I visit the URL from the report I get a 404 response code, is this a bug in the site crawl report?

Thanks,

Ian.

[kentcclark]

Which, of course, you can't do in Shopify.

Maybe we should just collectively get on Shopify to implement this by default.

[effectdigital]

It's all in this help document:

https://moz.com/help/moz-procedures/crawlers/rogerbot

"Crawl Delay To Slow Down Rogerbot

We want to crawl your site as fast as we can, so we can complete a crawl in good time, without causing issues for your human visitors.

If you want to slow rogerbot down, you can use the Crawl Delay directive. The following directive would only allow rogerbot to access your site once every 10 seconds:

User-agent: rogerbot

Crawl-delay: 10"

So you'd put the specified rule in your robots.txt file

[pc-limited]

This is happening to a client of mine too. Is there a way to set my regular MOZ Pro account to crawl the site slower?

[effectdigital]

This is a common issue with Shopify hosted stores, see this post:

• https://community.shopify.com/c/Shopify-Discussion/Crawling-Shopify-stores-returns-HTTP-error-430/m-p/300551

It seems to be related to crawling speed. If a bot crawls your site too fast, you'll get 430s.

It may also be related to the proposed, 'additional' status code 430 documented here:

"430 Request Header Fields Too Large

This status code indicates that the server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields."

I'd probably look at that Shopify thread and see if anything sounds familiar

[ianatkins]

@Angler - yeah thought the same - but why not log it as a 403 in the report. The site is hosted on Shopify - so don't get access to logs unfortunately.

Was wandering if it was related to rate limiting as in a few cases it's a false positive and page loads fine.

Have emailed Eli - thanks,

Best.

Ian.

[ANGLERTechnologiesUSAInc]

Hey Ian,

It's probably HTTP 403 which is Forbidden error for a web-page or website for some specific reasons like category block, country block, IP block etc. Just check once with your hosting / cpanel for global visibility without any blockages.

[A Former User]

Hey Ian,

Thanks for reaching out to us!

Would you be able to contact us at help@moz.com so that we can take a closer look at your Campaign.

Looking forward to hearing from you,

Eli