No data in Moz

[MarcelMoz]

Hello,

Since last tuesday there has been no data in Moz anymore. The error code for the homepage says:

'608 : Page not decodable as specified Content-Encoding:'

I checked this list http://moz.com/help/pro/why-can-t-rogerbot-crawl-my-site but it doesn't tell me more.
Hopefully anyone can help me.

Thanks,

Marcel

[MarcelMoz]

Yesterday another crawl failed. Moz's Help team told me on the 15th of November:

'Our engineers are looking at this now and I should have news for you today. Sorry for the delay, I'm sure we can figure this one out.' Since that day I haven't received one message from the Help team, very disappointing.

I'm missing the data of one month now and this is not acceptable.

Marcel

[MarcelMoz]

A new campaign for a new website we have just launched caused no crawling problems. This seems to tell there is no Gzip error at server admin side. Moz is working on this case so I hope to get a positive word soon.

[MarcelMoz]

Hi Joel,

Today I subscribed for a trial period with Raven Tools. This tool can actually crawl our website. This tells me that the issue is possibly not a Gzip error but an issue on Moz's side.

Gzip is a piece of technique which is not required for browsers to show pages. I suppose that Gzip is neither required for the Moz bot to crawl a site. A lot of websites do not use Gzip what should mean that they can't get their website crawled by Moz?

What possible solutions are there to solve this problem? Is opening a whole new account a solution? I suppose that some technical masterminds are working for Moz. Could you pass this case to them to get the problems solved?

I contacted our server admin again but they already told us nothing happened lately related to this problem.

Thanks again.

Marcel

[JoelDay]

Hey Marcel,

I looked at your latest crawl and it appears you're still getting that gzip error.

Unfortunately I don't have any way to see more about your server since the crawl is dying at the www subdomain.

Sorry I couldn't shed any more light on this.
You may be able to have your server admin check your logs using the timestamp in the CSV as a reference and see what happened.
Thanks,
Joel.

[MarcelMoz]

I found out that hiding the navigational items caused the Google ranking problems. This has been solved now. Still there is no data in my crawl diagnostics report and it got updated again on the 6th of November. Two empty updates now.

Why can Roger bot only see two indexed pages? Can anybody help me with this problem? I need to see all the data again.

Thanks.

Marcel

[MarcelMoz]

Hi Joel,

Thanks for your reaction. I checked several Gzip tools and they are all telling me there are no problems with the Gzip on our website. I also contacted our server admin and I am waiting for more information now.

Another issue we are dealing with is that we have lost some (over 15 positions/ categories) of our organic positions since last Sunday. And new pages won't appear in the SERP (but will get indexed) where they used to gain a top 10 ranking one or two days after putting them online. Ofcourse with high quality content. It seems like Google are devaluating our pages for some reason. Since last Friday we have lost some organic traffic every day (10-20%).

Could there be a correlation between the Gzip error and the oganic position drops? I was thinking about: a Gzip problem will cause page load time problems (which we have last few days on the homepage) > page load time is a Google ranking factor > higher page load times means a drop in organic positions what means a organic traffic drop.

Another thing I was thinking about is a website change we have made last week. We hid some navigational items by just adding them as 'hidden items' in the source code. Since hidden content has been not done by Google guidelines, could this be a reason for the position drops? We undid this change this morning to hopefully regain our positions.

Could you help me further by thinking with me or giving me some new insights?

Thank you very much.

Marcel

[JoelDay]

Hey Marcel,

Thanks for the question. It looks like what happened is that when we hit your www home page we got a gzip error. Unfortunately I don't have any specific advice on how to resolve this but you should be able to work with your server admin to determine the cause and solution of this.

Thanks!
Joel.