Welcome to the Q&A Forum

Sounds great, Mike! Just send them over and I'll take a look!

Thanks,
Carin

Hey Mike,

I'm sorry you're so frustrated with the issues in the index lately - I know it's an inconvenience, but, I assure, you the team has been working all hours to work out these kinks!

In fact, after many nights and weekends sacrificed, we're looking at probably being early on our next release.  The bugs will be much less evident in this next index as the stale crawl data is dropped from the index.

I know that doesn't help you out right now. Can you send me some details on the corruption you're seeing? A full OSE link with all the parameters would be perfect as well as a CSV, if you have one. If you don't feel comfortable posting in Q&A, please email me at carin@seomoz.org.

This sounds like the same bug we saw emerge in this index, and have since fixed, but I want to make sure that is the case.

Again, I'm really sorry for the inconvenience and frustration this is causing - we are working hard at ironing out these final issues!

Thanks,
Carin

This just came to our attention yesterday and our engineers have been investigating over the weekend. It appears to be fallout from the parsing bug that caused the initial delay of this index launch.

We're still investigating, but we do have another index in the works, with the parsing bug no longer present. We hope to have this ready in the next two weeks. In the meantime, we're looking into how we can remedy this current anchor text portion.

If you would like to read more about the parsing bug, Phil provided a great explanation in the forum article here.

Sorry for the inconvenience this will cause - we're looking into ways to remedy this as soon as we can!

Thanks,
Carin

Yep, David is correct - that call is only available with a paid API plan. If you are interested in a paid plan, check out the different tiers on our Mozscape API page.

Thanks!
Carin

No problem! I'm so sorry for the inconvenience!

I just pushed the remaining pending reports through, so I think you should be set, but if you continue to run into any problems, just let me know!

Hey there!

Haha - we ran into a problem on Monday night with one of the machines falling over causing a huge backlog to pile up. We were able to get things back on track yesterday and churn through the backed up reports, but with the index launch yesterday, we're seeing a bit of a backlog again this morning.

We are getting a monster machine up right now to speed through this! Once things calm down you should see these come through. It looks like you have about 8 pending - I'll keep an eye on them to make sure they go through!

Thanks,
Carin

Hey there!

The Top 500 list is compiled from our Mozscape (formerly Linkscape) link data compiled from our crawlers, but, unfortunately, we don't crawl Facebook since the pages are https.

Adding the ability to crawl https is on our road map, however!

Thanks,
Carin

Hey Ravi,

Sorry for the delayed response - I wanted to follow up with the engineers to see if they had any suggestions for you.

They agreed the Limit parameter set to 1,000 might be too large to process. Have you tried adjusting that to 300 or even 500? Do you see better success at a lower limit?

Our system will timeout at about 60 seconds so I'm not sure if the hanging is on our end. If dropping the limit size doesn't help, you might want to think about ending the request after about a minute. Sometimes requests that are too long wil timeout, but work fine on a retry as some data will be cached from the previous request.

I hope this information is helpful, but let me know if you're still experiencing issues!

Thanks,
Carin

Hey there!

Just want to make sure I'm understanding what you're trying to do - basically you're hoping to use jQuery to send requests to the API and then fetch the JSON results?

What type of queries are you sending the API? What would the API query look like?

Also, we do have the API Help Forums to post in or search as well - not sure if you've explored these pages, but there could be some helpful information for you there as well!

Thanks!
Carin

Hey! This is an issue I haven't heard of before - would you be able to provide anymore information like an example query to the API and some of the pages you are seeing hang?

Thanks!

Carin

Hey Max,

*imr is the "raw" internal MozRank value. The "pretty" value that most people use for their applications is *imp, which has been fit to a nice 0-10 scale.

*imr isn't an official data point in the API, just meaning we reserve the right to change as necessary, which is why we don't have it documented. However, we still return the value if you know the endpoint

Hope that helps! Let me know if you have more questions!

Thanks,
Carin

Hey Shinya,

I'm guessing from your question that you are trying the above API query and receiving an error (401 Unauthorized - unauthorized api 'links/page_to_page.domain_authority').

The reason is because the Scope and Sort parameters you are using are incompatible. The request you are sending is asking for pages on the same domain to be sorted by Domain Authority, but they will all have the same Domain Authority.

However, if you try something like this, it should work to sort the results by Page Authority. Let me know if you are still seeing the results you are hoping for!

http://lsapi.seomoz.com/linkscape/links/www.seomoz.org/blog?Scope=page_to_page&Sort=page_authority

Thanks,
Carin

Hey!

That sounds like odd behavior and I don't think I've heard of that happening before. I'd love to dig a bit deeper to see what's going on.

Would you be able to send me the pages you are searching? I assume you are experiencing this in Open Site Explorer?

If you would prefer not post the URLs in this forum, feel free to email me directly at carin@seomoz.org!

Thanks,
Carin