Welcome to the Q&A Forum

I know that Rogerbot has an issue with SSL / SNI technology used with our Amazon Cloudfront setup even though most browsers support it.

Is there a timeframe for this to be fixed?  If not is there a specific set of instructions or any way for us to get this from showing up on our High Priority list?

Thanks!

Sean

Ok I understand.  Thank you for the response Chiaryn.  I will use our robots.txt to clear the pages in question from the crawl error report.

Sean

Hello!

I have a page with name="robots" content="noindex, follow"> on it because it's just a form page with no SEO value, but Moz is still reporting it as a crawl error for not having a meta description.

Is there something I'm missing?  Or should I wait until the next Moz Crawl to see if it drops off?

If so - how did you end up resolving them?

For instance we have 85 "temporary redirect" errors from our Zendesk support site in our crawl error report and we don't have access to the robots.txt file through Zendesk.

Thanks Yossi, this is kind of what I expected I think.  I guess the question should have been "has anyone had Moz crawl issues with their Zendesk support site"?

The main issue with our support site is that Zendesk does not allow access to the robots.txt file so there is no way to add regular expressions like the wildcard search/* to it.

I will re-post the question as above.

Hello!

We have a Zendesk support site at support.zspace.com - our Moz crawl report is saying that there is 85 temporary redirect issues, mostly coming from our support site.

My question is, does the Moz crawler use robots.txt?

We have currently Disallow: /search in our robots.txt, but not /search/*

Most of the temporary redirect URL's in the crawl error report look like this...

https://support.zspace.com/hc/en-us/search/click?data=BAh7CjoHaWRp

So would we need to add "Disallow: /hc/en-us/search/*" to get Moz crawler to ignore these?