How do batched URL metrics work in terms of rows and rate limit?
-
I am using the free API plan to get URL metrics and batching my calls like this:
https://github.com/seomoz/SEOmozAPISamples/blob/master/php/batching_urls_sample.php
How does this work in terms of rows and limits? If I do a batch of 10 urls does it count as 1 row? or 10? Do I have to wait 10 seconds before calling the next batch?
-
Hi there - Kristina from Moz's Help Team here.
A batch of 10 URLs will count as 10 rows and you would need to wait 10 seconds before making the next query. If you make your next query too quickly you will be hit with a throttle which lasts 30 seconds. If you make another query during that period, you potentially could push that 30 second throttle even further out.
I hope this helps! In the future, feel free to email our team anytime at help@moz.com and someone from our team will be happy to help out!
Have a great day.
-Kristina
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
When I click into the moz bar on our website www.essexparts.com it shows that the URL is Canadian and shows a Canada flag. The website and company are in the US. Can someone please explain this?
When I click into the moz bar on our website www.essexparts.com it shows that the URL is Canadian and shows a Canada flag. The website and company are in the US. Can someone please explain this? Also does the location have any bearing on how it shows up in google? XNQOQoJ
API | | Tindol0 -
API metrics for discovered and lost linking domains
Hello, Could you tell me, can I use the api to get such data as ‘Discovered in the last 60 days’ and ‘Lost Links’?
API | | OlegKireyenka
If yes, which values of ‘Cols’ in URL Metrics I can use? Thank!0 -
Is Anchor text metric is available for free MOZ API ?
I'm accessing anchor text metric using free MOZ API account which is for 30 days. is there is any way to get anchor text ?
API | | rogerdavid0 -
MozBar not working and Help is asking for to login
I can not use MozBar, receive a pop up about API credentials and when I go to Moz Help am asked to login but my credentials do not work. moz-login-issue-2016.09.28.png
API | | Stacious0 -
API - Internal Links to page and related metrics
Hi dear moz Team! Currently I´m building a Java application accessing your API. But there are some metrics I urgently need which I can´t get out of the API until now: The total number of internal links to a page The total number of internal links to a page with partial anchor text match MozRank passed by all internal links w. part. match anchor text (would be nice) For example, if I try this by your links endpoint, my idea was: http://lsapi.seomoz.com/linkscape/links/http%3A%2F%2Fwww.jetztspielen.de%2F?AccessID=..
API | | pollierer
&Expires=..
&Signature=..
&Scope=domain_to_page
&Filter=internal
&Sort=domain_authority
&SourceCols=4 (or any other value)
&SourceDomain=www.jetztspielen.de
&Offset=0
&Limit=50 If I try this, the API says: {"status": "400", "error_message": "Cannot set a source domain when filtering for internal links."} Is there any way to get the data I need by your API endpoints? I´m currently writing my master thesis and it is very important to me to solve this somehow. Thank you very much in advance! Best, Andreas Pollierer1 -
Moz Analytics doesn't work
Hello Mozers, Moz analytics doesn't work already more than a week. I've tried on Mozila Firefox 29.0.1 and Chrome Version 34.0.1847.137 and getting some nasty errors. Firefox Firebug console: TypeError: freya.getApp is not a function
API | | juris_l
...mpaign_owner_id:app.getParam('campaign_user_num'),campaign_id:app.getParam('camp... applic...23b3.js (line 223) Chrome Firebug console: Uncaught TypeError: undefined is not a function <a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a> freya.RoutesUtils.applyDefaultParams<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a> freya.RoutesUtils.make<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a> freya.Routes.settingsCampaignPath<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:227">application-c42010fe6b0d425aca7cad19e29223b3.js:227</a> freya.views.NavSite.freya.View.extend.renderData<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:713">application-c42010fe6b0d425aca7cad19e29223b3.js:713</a> freya.View.Backbone.View.extend.render<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:231">application-c42010fe6b0d425aca7cad19e29223b3.js:231</a> (anonymous function)<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/pro/home:213">home:213</a> fire<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:60">jquery-b68cd156547e7de90502ecf7becf0beb.js:60</a> self.fireWith<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:66">jquery-b68cd156547e7de90502ecf7becf0beb.js:66</a> jQuery.extend.ready<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:22">jquery-b68cd156547e7de90502ecf7becf0beb.js:22</a> DOMContentLoaded<a class="console-message-url webkit-html-resource-link" title="http://analytics.moz.com/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:53">jquery-b68cd156547e7de90502ecf7becf0beb.js:53</a>1 -
API: General information URL on path level
Is it possible to get general information (refdomains, mozrank etc.) out of the API on path level? If so, what is the best way to do this? Example www.test.com/folder/ -> Combined data (for example, total refdomains etc) for all URL’s indexed by Moz that include www.test.com/folder/ -> like www.test.com/folder/item/page.html and www.test.com/folder/page2.html
API | | MerkleNederland0 -
Suggestion - How to improve OSE metrics for DA & PA
I am sure everyone is aware at Moz, that although the Moz link metrics ( primarily I am talking about DA & PA) are good, there is a lot of room for improvement, and that there are a lot of areas where the metric values given to some types of site are well out of whack with what their "real" values should be. Some examples
API | | James77
www.somuch.com (Link Directory) - DA 72
www.articlesbase.com (Article Directory) - DA 89
www.ezinearticles.com (Article Directory) - DA 91 I'm sure everyone would agree that links from these domains are not as powerful (if of any value at all), as their DA would suggest, and therefore by definition of how moz metrics work, the sites these have links from such sites are also inflated - thus they throw the whole link graph out of whack. I have 2 suggestions which could be used to singularly or in conjunction (and obviously with other factors that Moz use to calculate DA and PA) which could help move these values to what they should more realistically be. 1/. Incorporate rank values.
This is effectively using rank values to reverse engine what google (or other engines) as a "value" on a website. This could be achieved (if moz were not to build the data gathering system itself), by intergrating with a company that already provides this data - eg searchmetrics, semrush etc. As an example you would take a domian and pull in some rank values eg http://www.semrush.com/info/somuch.com?db=us - where you could use traffic, traffic price, traffic history as a metric as part of the overall Moz scoring alogrithm. As you can see from my example according to SEMRush the amount of traffic and traffic price is extreamly low for what you would expect of a website that has a DA of 72. Likewise you will find this for the other two sites and similarly to pretty much any other site you will test. This is essentially because your tapping into Googles own ranking factors, and thereby more inline with what real values (according to Google) are with respect to the quality of a website. Therefore if you were to incorporate these values, I believe you could improve the Moz metrics. 2/. Social Sharing Value
Another strong indicator of quality the amount of social sharing of a document or website as a whole, and again you will find as with my examples, that pages on these sites have low social metrics in comparison to what you would normally associate with sites of these DA values. Obviously to do this you would need to pull social metrics of all the pages in your link DB. Or if this we to tech intense to achieve, again work with a partner such as searchmetrics, which provide "Total Social Interations" on a domain level basis. Divide this value by the number of Moz crawled pages and you would have a crude value of the overall average social scorability of a webpage on a given site. Obviously both the above, do have their flaws if you looked at them in complete isolation, however in combination they could provide a robust metric to use in any alogrithm, and in combination with current moz values used in the alogrithm I believe you could make big strides into improving overall Moz metrics.1