The difference between api value and screen value
-
When I check the two parameters (PA and DA values) actually, these values often differ from those which I receive from your API. Why does it happen?
-
Thanks for the response! And thanks for the advice!
-
Redirects:
yyxysh.com -> DA=8; UPA = 17 in OSE, API {"pda":7.946532082305239,"upa":16.535296818533226}
www.yyxysh.com -> DA=8; UPA=21; {"pda":7.946532082305239,"upa":21.185637908436604}zaegi.com -> 17/27; {"pda":17.31598169835115,"upa":27.430491280580874}
www.zaegi.com -> 17/13; {"pda":17.31598169835115,"upa":13.339025908887258}As you can see API and OSE works. But checking different domain screw test. Please check your software did add "www" in beginning of checks? Because mine tests shows that it ADD it.
If you have Mac then you can use mine SEOAuditor very small app that return few important metrics:
http://www.mobiliodevelopment.com/seoauditor/
Actual API examples are from it. I just enable "debug log" to get raw results. -
I don't think the difference I observed came from rounding because it varied quite more than the difference of rounding range! For instance, in the domain of "yyxysh.com", I observed UPA as 17 directly via OSE. On the other hand, API output UPA as 21.1856379084366. In another case, in the domain of "zaegi.com", I confirmed 27 via OSE in contrast to 13.3390259088872 via API. I assume such a difference doesn't come from a time lag because API refreshes the current values such as UPA within 1 hour before or after OSE refreshes. I found about 50% of samples encountered such a value difference after my investigation for a few days. Therefore, I hope you would give me additional advice or cause about the phenomenon. Thank you very much for your help in advance.
-
Dev that use API here.
Yes - they're different sometimes because rounding. In OSE you get numbers as PDA 25.294393094636707 and UPA 36.15102264746345. And Moz OSE round them to 25 and 36. This is ok. But on mine other site bgdn.net as response get{"pda":22.949587785824708,"upa":27.22655880092715}. OSE shows 23 and 27.
If you post some URL with difference here we can debug and see difference.
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
-
Unsolved Empty Response from API v1
Hi, I always receive a empty reponse from your API v1. Here ist my API call for further investigation:
API | | George4445
"http://lsapi.seomoz.com/linkscape/url-metrics/https://www.moz.com/?AccessID=mozscape-1234567890&Expires=1719916530&Signature=generatedsignaturecode" Reponse: {} Do you experience some problems with the api? Thank you very much
Regards George Shaylen0 -
Unsolved "The account does not have access to that quota" - API v1 URL Metrics
Hi! On one of our servers we get the message "The account does not have access to that quota" when pulling data for v1 URL Metrics endpoint in the API.
API | | aheitzman
This only happens on one specific server, others have worked flawlessly. Any idea of what might be going on? Thanks0 -
Unknown data items in Links API response
So I'm on the documentation page at https://moz.com/help/links-api/making-calls/url-metrics . I've copied the bit fields table into a spreadsheet. I've removed all the "deprecated" items and have totalled up the remaining items making a Cols= value of 182537205900657000. For want of better knowledge, I've used that same value for LinkCols=, SourceCols= and TargetCols=. The request url ends up being (anonymized): http://lsapi.seomoz.com/linkscape/links/fordanddoonan.com.au?Cols=182537205900657000&AccessID=xxx&Expires=1557458487346&Signature=xxx&SourceCols=182537205900657000&TargetCols=182537205900657000&LinkCols=182537205900657000&Limit=1000&Scope=page_to_domain&Filter=external My question is, what do I make of all the extra fields that I get in the json packet what should I do to remove them? These extra fields are: lrid, lsrc, ltgt, luufq, luueid, lufeid, luujid, luumrp, luumrr, luflan, lufspf, lufsplc, lufspp, lufsps, lufspsc, luus, lufuid, lupuid, lufipl, luupa, lupda, luued, lufed, luped, lupib, luulc, flan, fspf, fsplc, fspp, fsps Is it simply a case of limiting the values of TargetCols, LinkCols and SourceCols? If so, to what?
API | | StevePoul1 -
API Access Change
I'm not sure, but I seem to remember that there was a certain number of API calls that USED to be included with my MOZ Pro level subscription and as I check it now, the API access is a separate subscription. Was there a recent change or has my memory finally started going?
API | | SWGroves0 -
3 result limit to Top Pages API call
I am using the MOZ API to make calls for the top pages for a particular URL. However, when I pass in any limit value greater than 3 the API only returns 3 results. I have even tried to put in URLs like 'www.moz.com' and still only 3 results. Sample call to the API below: http://lsapi.seomoz.com/linkscape/top-pages/www.moz.com?AccessID=member-xxxxxxxxx&Expires=1419020831&Signature=xxxxxxxxx&Cols=2052&Offset=0&Limit=50
API | | solodev0 -
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 -
Is there a reports Api?
hello fellow Mozers. got a question. is anyone aware of an api coming out to feed individual reports? We have a crm to manage all of our clients, and I'd love to feed the new moz analytics directly into our system. Please let me know if it already exists, is in the works, etc. Thanks, Stephan
API | | Stephan_Boehringer0