Does anyone know how long the page strengh tool caches the data for non members or free members before allowing a refresh?
well i thought it was a week. But i'm not sure. Dont worry about it. it means you have longer to improve it.
No, I am not that bothered about it and don't care what it scores for my sites, but I am doing research for something and have found out a little fact which I think people will be interested in, but need to find out exactly how long they are caching their results. I submitted Directory Share at 9:25am Brazil local time so I will keep checking it and see when they let me refresh the data.
Ok, in case any of you were interested.... an0n was correct, I was only able to refresh the report after 3 days (72 hours). The reason this was interesting for me was because I was doing some research for a new project which will be using the Alexa Web Information Service. This service is not free, they charge $0.00015 per request or $0.15 per 1,000 requests. Matt publicly acknowledged that this was the API which they use in a recent Whiteboard Friday comment: The terms and conditions for the API are quite long winded, but in the section specifically relating to the Alexa data, it states: Oops, guess they missed that when they switched the tool to only allow premium users to refresh reports.
wow. so does this mean seomoz could be taken to court of breach of alexas TOS. thats a good find there silky
I think it's 3 days as well. I'll double check with our developer tomorrow. I know it's not 100% accurate still, but we're up around 80-90% of factors being returned. One big problem has been that Technorati has actually been down, so querying them has been a huge pain as the tool hangs but it never returns results...
Rand, thanks for dropping by, although I think you missed the overall point of the thread. Have a read of my third post as I think the question you may want to ask Matt your developer, is how do we fix this. This thread was never about the accuracy of the tool as we are all well aware of the issues on that point.
Thanks - I'll let Matt know that we'll need to request the Alexa data more often... sadly, that means the tool will probably be less accurate - doh!