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 MOZ API for domain authority
I am using the MOZ API to check domain authority (DA). Recently, I noticed a discrepancy: the DA value retrieved via the API differs from the result on the MOZ homepage. Specifically, the API returns a DA of 10, while the homepage shows "NO DATA." Additionally, other services like Ahrefs report a DA of 0. I relied on the MOZ API's result when purchasing this domain and now feel misled. I would like to understand the exact reason for this inconsistency.
API | | Skys0 -
I can not get the results from API now.
Dear master,
API | | Feipo
I can not get the results from API now. And also yesterday. My id is 1393657@qq.com.2 -
Location Data Batch Updates via the MOZ API
According to the MOZ API documentation, I am able to update multiple Locations in a batch in order to create or update their location data, currently 130 locations. I have successfully created a batch and the API returned the $id, as I expected. Yet, it doesn't make clear how the multiple locations I want to update are supposed to be sent back to the API. I was expecting an upload of a CSV file or JSON data, and not Query Parameter as noted in the docs. When including a JSON file, properly formatted, as a binary upload, the response is still expecting a locations parameter. See error here: { "status":"MISSING_PARAMETER", "message":"locations missing. ", "response": { "locations":"MISSING_PARAMETER" } } https://moz.com/developers/docs/local/api#_api_batch__id-PATCH
API | | yuca.pro1 -
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 -
API ACCESS to COMPETITOR DATA
Is there access with any of the available API's that I may be able to show my client's keyword competitive data for them vs their competitors (The ones they specify?). Perhaps in JSON format?
API | | Digitlead0 -
Connect to API
Hello Very often, when we connect to the API we get http error 401. We make some reconnections. How solve this problem? Request: https://lsapi.seomoz.com/linkscape/url-metrics/?AccessID={MY AccessID}&Expires=1478887421&Signature={MY Sig} Body: ["slemma.com"] Response: {
API | | SlemmaDev
"status" : "401",
"error_message" : "Permission denied: bjeacbehaehnbmhibjgnamekcheocbfcddeaci"
} Thanks!0 -
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