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
-
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 -
Is There any API from FourSqaure that allow us directly feeding business listings into it , Moz is doing same , so there must be some API?
Hi, i have seen "Moz Local" , has a option , "FourSqaure". I just a curiosity to ask that , is there any tie-up between FourSqaure and Moz , coz Moz must be using its APIs to feeds its business listings into FS Database. When i have searched for FS APIs for direclty feeding business listings into it , i got nothing ? so i have got this question? if any one can help me out.
API | | Prodio0 -
"403 Forbidden" is they will be displayed in the "API"
Nice to meet you.
API | | yamayamax
Although the future API of the question of "URL Metrics", I want you to forgive me English is very immature thing. I'm very troubled now.
If you call the "API" in the manner described below, such PHP of the program, "403 Forbidden" is the result.
Because the information when you visit the URL directly is displayed, we suspect the PHP of the problem.
About the cause, it will be saved in a very and Nowak advice.
Whether Thank you. code $accessID = "<removed for="" privacy="">";
$secretKey = "<removed for="" privacy="">";
$expires = time() + 300;
$SignInStr = $accessID. "\n" .$expires;
$binarySignature = hash_hmac('sha1', $SignInStr, $secretKey, true);
$SafeSignature = urlencode(base64_encode($binarySignature));
$objURL = "http://www.google.com";
$flags = "103079217188";
$reqUrl = "http://lsapi.seomoz.com/linkscape/url-metrics/".urlencode($objURL)."?Cols=".$cols."&AccessID=".$accessID."&Expires=".$expires."&Signature=".$SafeSignature;
$opts = array(CURLOPT_RETURNTRANSFER => true);
$curlhandle = curl_init($reqUrl);
curl_setopt_array($curlhandle, $opts);
$content = curl_exec($curlhandle);
curl_close($curlhandle);
$resObj = json_decode($content); //decode the json object and fetch results
echo $reqUrl . "
";
echo "Domain Authority : " . $resObj->{'pda'};
echo "Page Authority : " . $resObj->{'upa'};
?>
------------------------------------------------------------------------------------</removed></removed>0 -
Can the API Filter Links with Certain Anchor Text?
I am trying to get all links that have a certain strings in their anchor text: I am using the python library: https://github.com/seomoz/SEOmozAPISamples/blob/master/python/lsapi.py Looking at the documentation, it says I can get the normalized anchor text by using the bit flag 8 for the LinkCols value: https://moz.com/help/guides/moz-api/mozscape/api-reference/link-metrics So I tried this: links = l.links('example.com', scope='page_to_domain', sort='domain_authority', filters=['external'], sourceCols = lsapi.UMCols.url, linkCols=8) But it doesn't return the expected 'lnt' response field or anything similar to the anchor text. How do I get the anchor text on the source URLs? I also tried 10 for the linkCols value, to get all the bit flags in the lf field as well as the anchor text. In both instances (and even with different variations of targetCols & sourceCols), this is all the fields that are returned: 'lrid', 'lsrc', 'luuu', 'uu', 'luupa', 'ltgt'
API | | nbyloff0 -
API Limit Question
Hi, I am unfamiliar with API's in general but never had an issue with being throttled until today. I used the api a lot heavier today which is why. According to the API dashboard I made 5100 "requests" today and 21,000 "rows returned". I am using a MOZ PRO account and have been throttled as a result. I am wondering when does it reset? Is it a daily, weekly, or monthly limit that I hit and what is the limit? Thanks
API | | greganderson4440 -
Moz api request problem fail (status 401)
Hello! I'm getting an error for seomoz call using API: {"status":"401","error_message":"Your authentication failed. Check your authentication details and try again. For more information on signed authentication, see: http://apiwiki.moz.com/signed-authentication"} Can you help me?
API | | leoh0 -
Seo moz api request problem [401 error_message Your authentication failed]
Hello Team, I have moz pro account. I'm getting following error for seomoz call using your API: {"status":"401","error_message":"Your authentication failed. Check your authentication details and try again. For more information on signed authentication, see: http://apiwiki.moz.com/signed-authentication"} The link that we are using is:
API | | eBrandz
http://lsapi.seomoz.com/linkscape/url-metrics/ And following bits are requested during the call: 68719476736 34359738368 32 2048 16384 The error is intermittent. It comes and goes. There were no issues with results 3 days ago. I suddenly started getting this error. Could you please investigate into it and let me know the cause of issues and its correctiveness. It will great if you can provide us a support email Id for immediate response. Thanks,0 -
How to best use MOZ api?
i love the idea of the api - but need a tool to access it. having seen the seogadget excel addin, but unable to use it with my MAC. Do you have a recommendation for using api without writing my own code? Thanks, in advance!
API | | robertdonnell0