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
-
Moz got problem crawling SquareSpace websites?
Moz sent us an email about our website https://www.openhill.com that they failed to crawl. I checked the forums with the same issues with mine and it looks like that Moz has problems with websites from Squarespace. I wonder if you do have a workaround on this. Let me know if you have instructions for me to fix this kind of issue. Thanks!
API | | leahdickey0 -
To get top searched from the website
I need to get top searched keywords by user from the given website URL through API call. Please help me to achieve this. I get anchor text and link metrics but no documentation to get Keywords. Thank in advance.
API | | Darwill0 -
Is Moz's rank checker driving referals (and bounces) in my analytics?
I see 200+ referral visits per month from "rank-checker.online" and they all bounce with one second session durations. Are these bounces hurting my SEO? They are definitely distorting my referral metrics. Can I block them somehow?
API | | 10516VT1163000 -
Wrong answers for API request
Hi, I just recently started getting errors when using the API. The request back contains zeros for all the keys except PDA which is a new to me. Haven't changed anything in the code and the authorization seems to work fine. Is this something on my end? However, I don't get for all the requests, perhaps half of the time. Example of the return: {"fmrp":0,"fmrr":0,"pda":27.7812456171725224,"ueid":0,"uid":0,"uipl":0,"umrp":0,"umrr":0,"upa":1} Thanks in advance! /Mathias
API | | Lobtec0 -
Moz Crawl Log File
Hi All - We have a large client who's website when down for a few hours the same day we crawled the site with Moz. They are asking if we can get a log file with the details of what and when Moz crawled on their site. Have any of you ever experienced this issue before? Is that data out there? Really appreciate the help.
API | | NobleStudios0 -
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