MOZ API - Search Visibility
-
Hello there,
We are looking to see if we can recreate the Search Visibility report through the API. We are wondering which API parameters and metrics we should use to recreate the report? Also, we want to distinguish between traffic coming from desktops and mobile traffic. Is this possible with the API? Which type of account do we need to use for these functionalities: the free account or paid account? We are currently using a free account.
Also: we are wondering if can access historical data with the API? For instance: we want to determine the domain authority from October 2016 off on. Is this possible?
Thanks in advance!
Kind regards,
Bart Minten
-
Hello Lisa,
Thank you for your fast response! Good to hear that Moz has plans for a keyword API! We are greatly looking forward to that! In the meantime we'll make due with the current functionalities.
Kind regards,
Bart
-
Hi there Bart,
Lisa from the Moz help team here!
No, I'm afraid that it would not be possible to use the API this way. The Search Visibility metric depends entirely on keyword rankings and we don't currently offer an API for this or traffic data. We calculate Search Visibility by:
- Taking all of your keywords and the associated URL’s position and applying a click through rate (CTR) for each position.
- The CTRs are then summed
- This number is then divided by the total number of keywords.
We do have a keyword API in our future plans and there is survey you can take to register your interest in a keyword API and tell us what kinds of things you're looking for: https://www.surveymonkey.com/r/YZ58JVH
We use the traffic data provided by GA. You would need to investigate this directly to distinguish between mobile and desktop visits.
Our API contains the link data that you see in Open Site Explorer and only contains the data from the most recent update. The only place to see historical link data is within the campaign. We'd love to be able to store and show previous data as part of our API but we'd need a much bigger boat (by which I mean data center).
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
-
Can you tell me about the impact of Do-follow and No-follow backlinks for increasing Moz DA?
Have Do-follow backlinks and No-Follow backlinks same value to increase Domain Authority in Moz? Recently, I have created 290 profile backlinks which was do-follow. But from yesterday I have seen all backlinks are no-follow now according to the decision of sites' owners. My site's DA has already increased up to 35. Will this DA fall gradually from now? Apart from it, if I have created same backlinks for my another site; will my DA be 35? Please try to clarify it. My site is: https://kodnest.com Thanks. Waiting for your valuable answer from Moz official.
API | | FrankJOwens0 -
Do you fetch website titles from paid api https://moz.com/help/guides/moz-api/mozscape/api-reference/url-metrics?
We are using one of your API: https://moz.com/help/guides/moz-api/mozscape/api-reference/url-metrics on our website and it does not show up the title for each website.
API | | SOSCreatives
But when I see the title of the same website through your extension Moz Bar, then it does show the title from the extension of that website. Can you tell me what is missing here?0 -
Mozscape API Updates (Non-updates!) - becoming a joke!
This is the 3rd month in succession where the Mozscape index has been delayed. Myself and clients are losing patience with this, as I am sure many others must be. Just what do you suppose we tell clients waiting for that data? We have incomplete and sometimes skewed metrics to report on, delays which then get delayed further, with nothing but the usual 'we are working on it' and 'bear with us'. It's becoming obvious you fudged the index update back in January (see discussion here with some kind of explanation finally from Rand: https://moz.com/community/q/is-everybody-seeing-da-pa-drops-after-last-moz-api-update), and seems you have been fumbling around ever since trying to fix it, with data all over the place, shifting DA scores and missing links from campaign data. Your developers should be working around the clock to fix this, because this is a big part of what you're selling in your service, and as SEO's and marketers we are relying on that data for client retention and satisfaction. Will you refund us all if we should lose clients over this?! .. I don't think so! With reports already sent out the beginning of the month with incomplete data, I told clients the index would refresh April 10th as informed from the API updates page, only to see it fudged again on day of release with the index being rolled back to previous. So again, I have to tell clients there will be more delays, ...with the uncertainty of IF it WILL EVEN get refreshed when you say it will. It's becoming a joke.. really!
API | | GregDixson2 -
New Moz reports
The new MozPRo reports do not give me the same level of data as my previous reports on the old platform, including detailed keyword reporting. I recently discovered that even if I schedule a monthly report, I still only get weekly data. Is it just me or is anyone else struggling with these new reports?
API | | Discovery_SA0 -
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 -
What is Moz's Error.aspx?aspxerrorpath HTTP Status 302 error message?
Hi, I am not sure what this error message is: "Error.aspx?aspxerrorpath". It immediately follows pages that are given at 302 status in Moz's crawl report. The same pages have never had this error before: | http://www.homedestination.com/news/2013/Minneapolis-home-price-appreciation.html | | http://www.homedestination.com/mortgage-worksheet.html | | http://www.homedestination.com/foreclosure-eligibility.html | Each page has a 100% score with WC3. Could you give me more insight as to what Moz may suggest I do to give the page a 200 HTTP status as before? Thanks.
API | | jessential0 -
Does any one know if there is a tool out there built with the Moz API where you can feed in a large list of URLs and get back Domain Authority?
Does any one know if there is a tool out there built with the Moz API where you can feed in a large list of URLs and get back Domain Authority? Has anyone used the API for something like this before? Thanks! Max
API | | Porch0
