Hi Etienne

I checked the campaign you have with the 902 response and the issue is with your host blocking AWS IPs. I could not find any SSL or SNI errors for the domain.

You will want to reach out to your hosting provider to make sure they are not blocking any AWS IP ranges. Our IPs are dynamic so we will not be able to provide a range for you.

There are also other issues with the SSL configuration which will need to be looked at which could result in different errors once the IPs are unblocked.

http://www.screencast.com/t/b8qEdNah

You can run a test here for any SSL domain: https://globalsign.ssllabs.com/analyze.html

Hope this helps!

Hello!

I can confirm your site does use SNI which can be checked at https://globalsign.ssllabs.com/analyze.html?d=www.honesthouse.co.uk&latest

If anyone else is unsure about your own site, you can use the above link, replace the URL and click on any server results which will confirm SNI status shown here: http://www.screencast.com/t/GLzjD7gjzjR

As for any workaround, other than disabling SNI completely, the quickest option to get crawled would be to sign up for the beta.

Jon will keep everyone posted with any new status and I can assure you this is our top priority feature we are working on.

Hey Philip

Currently we would need a physical address in order to validate against Facebook Places or Google+. You can setup an address in one of them to validate and publish then set your info to be hidden or private afterwards. By marking your business type as a home business in the csv file will allow our partners to hide your address.

Hope this helps!

UPDATE: Only one partner can hide the address, all others will display the full NAP and in order for us to stay connected to a validating source (google/facebook) the listing must not be setup as an SAB. Google now hides SAB listings from their Places API.

Service Area Businesses are not supported and it is recommended to manage your listings manually: http://www.localvisibilitysystem.com/2013/04/22/private-local-citations-where-can-you-list-your-business-but-hide-your-address/

Yes the sign up link is in the very first post by Jon

The link is http://goo.gl/forms/LCvL9Ix8JDHfbAvr1

Your robots.txt is blocking us with the wildcard directive at the very bottom.

You will want to add:

User-agent: dotbot
Disallow:

This should update when we release a new index next month.

Hope this helps!

Hi Radi

Just wanted to add that dotbot only crawls once a month while rogerbot crawls weekly. So you will not see any new metrics on OSE until we update our next Index.

Hello!

We do not have a hashtag tracker. Overall we don't have a strong focus on Social metrics outside of Followerwonk and we're more about tweets to and from particular users rather than a larger trend analysis. If we see more interest in this, it could be something our product team could add to their roadmap.

Currently I would recommend checking out https://tagboard.com/ for hashtag analysis.

Hi Ryan!

Our crawler will flag pages that have at least 90% similarity in the entire source code of the site so not just the body.

The way you want to interpret the report is the contact-us page has 35 duplicates, so "gabe" and "sale" are not dupes of each other in this section but are only each a duplicate of "contact-us". Those URLs might appear with their own duplicates of the same pages further down in the report.

While on the front end the pages do not appear to be similar. The issue is likely with the amount of javascript code on those pages.

Our crawler cannot read javascript so we are likely only able to see the template of the page. Other search tools are probably seeing the same thing as it returns 79% similarity  using this tool: http://www.freebulkseotools.com/similar-page-checker-tool.php

I can't provide much insight from a dev perspective but hope this helps!

Hi Etienne

There is a public 3rd party tool which also fails to connect which is hosted on AWS:

https://www.hurl.it/

If you run a GET request to this URL you will see a time out. Your admins can use this tool to quickly isolate any issues as this timeout is the same we are running into.

The SSL issues reported may not block normal browser connections but possible non-browser user-agents which would be another bot or server. We do not have any requirements or TLS, 1.0 and up is supported.

Hope this helps!