Is everybody seeing DA/PA-drops after last MOZ-api update?
-
Hi all,
I was wondering what happend at the last MOZ-update. The MOZ-health page has no current errors and i've checked a lot of websites probably about 50 a 60 from our customers and from our competitiors and everybody seems to have a decrease in DA's / PA's. Not just a couple went up and down like normally would happen, but all seems to have dropped.... Is anyone seeing the same in their campaigns?
Greetings,
Niels -
I have a client who has dropped from DA16 to DA1 and lost the few links he had he's NOT happy!!
Haven't just spent a few weeks impressing upon him the importance of building up his DA, it's been pretty hard trying to pacify him over this.
Great explanation from Rand, but c'mon MOZ when are you going to fix this?
And when are you going to enable tracking of DA? AuthorityLabs and others can do it for keyword ranking. I'm sure you can do it for DA and PA.
It appears their primary competitor has maintained their DA of 19. So can someone please explain this added twist?
-
Thnx! That explains a lot
-
Thanks for the logical answer, makes a lot of sense.
-
If we found fewer links to your sites with this index update, that can certainly be a factor in why you may have seen your Domain Authority drop a bit. These fluctuations aren't out of the ordinary, for all the reasons Rand mentions above - the number of backlinks in our index, and the quality of those links, will impact your DA scores.
You may see your DA bounce back after our next index update. This isn't scheduled for next week - our indexes take approximately 4 weeks to process. It looks like the next update is scheduled for February 28th. You can check this page for details on the Mozscape Index update any time: https://moz.com/products/api/updates
Hope that helps!
-
Yeah all my own and client sites are down 2-4 points. I'm seeing a decline in backlinks tracked so I thought that may be a factor. It's either a one time change moving forward or perhaps a bug that will correct itself next week? No idea.
-
Hi Niels - yep, I saw a bit of this too. I believe there's two causes:
-
We crawled a larger swath of the web in this index, so we captured more sites and more links, and that may mean the scaling of PA/DA (which are logarithmic) stretches to accommodate the larger number of links found, especially to sites at the top of the scale. For example, if Facebook has a DA of 100 with 5 Billion links, then we find 5 billion more links to it, Facebook still has a DA of 100, but it's a much higher threshold. Thus, sites with fewer links (and less quality links) will fall in DA as the scale is now stretched.
-
We crawled some weird stuff in this index, by mistake (or rather, because spammers built some nasty, deep crawl holes that Google probably didn't fall for but we did). A ton of odd domains on strange ccTLDs were seen, and crawled, because they gamed PageRank with lots of sketchy links. We've now excluded these for indices going forward, and hopefully will see the impact abate.
All that said, over time, as our index grows, you can expect that raw DA/PA numbers could get harder to achieve, meaning a lot of sites will drop in PA/DA (and some will grow too, as we discover more links to them in the broader web). My best advice is always to not use PA/DA as absolutes, but rather relative scores. That's how they're designed and how they work best.
It's like back when Google had PageRank, and Moz.com grew from PR4 to PR7, then as Google got bigger and bigger, and the web got bigger, Moz.com fell to PR5, even though we had way more links and ranked for way more stuff. The raw PR scale had just become stretched, so our PageRank fell, even though we'd been improving.
-
-
I second that.
-
Are you guys seriously using templates to answer questions about a lower DA. -.- ? I've got the exact same answer in the chat...-.- Atleast you could admit something went wrong with the last API-update.... As i'm counting the people here... more then 13 seo-consultants who pay a lot of money per month for accurate tracking all dropped down with a lot of websites.
Normally i wouldn't bother with a dropdown and it will probably be fixed in the next update but some customers even use it as a KPI and we gotta explain them we worked hard but they dropped with 10 points. -.- So answering something like:
"The reasoning behind this can be hard to pinpoint without the help of an SEO consultant or the specific web designer for your website".
Ain't gonna cut it for me..-.- What do you think we are? Atleast give us something we can communicate to our customers. -.- What i see in the API is a loss of:
- Januari 2017 » 1,100,261,648,691 (1.1 trillion) links.
- December 2016 » 1,114,899,547,461 (1.1 trillion) links.
So i could see it as a loss of 14 billion links since the last update? And because those links where lost for all high DA-websites everything dropped down. That would be the answer i aspected.
No hard feelings, but just be transparant with us, so we can communicate it to our customers. -
You're not wrong! Seeing a drop in links is likely to mean that our crawlers just didn't pick up those URLs this time around and include them in our index, but in all likelihood those links that we previously reported are still out there on the web. Our tools just haven't re-visited them to add them back into the index.
-
I also noticed that the number of External Links plummeted. Ours dropped from ~80 to ~45. Our biggest competitor lost about 150 of their 400.
Correct me if I'm wrong, but isn't this more likely to represent the Moz crawler not crawling certain URLs, rather than an actual loss of those backlinks?
-
Hi there! Tawny from Moz's Help Team here.
Aw, man! Sorry to hear about your DA dropping. You're right that it appears to have happened for everyone, across the board. I think I can help explain. The reasoning behind this can be hard to pinpoint without the help of an SEO consultant or the specific web designer for your website. Domain and Page Authority scores are both calculated using Moz's Ranking Models. In essence, we take a lot of rankings data from the search engines (by running queries) and then try to build a predictive scoring system using our own on-page analyses and Mozscape link data to construct an algorithm that will effectively reproduce the search engines' results. Our current accuracy hovers in the 70% range, but over time, we expect to improve.
Once we have a ranking model (which we internally call "uber"), we can create scores that best approximate the combinations of all our page-specific link metrics or domain-specific link metrics (removing the keyword-specific features like anchor text, on-page keyword usage, etc). These scores represent the model's query-independent or non-keyword-based ranking inputs.
In simple terms, Domain Authority is our best prediction about how content would perform in search engine rankings on one site vs. another. Page Authority answers the same question for an individual page. Both are amalgamations of all the link metrics (number of links, linking root domains, mozRank, mozTrust, etc.) we have into a single, predictive score.
It's important to note that both Domain Authority and Page Authority are on a 100-point, logarithmic scale. Thus, it's much more difficult to grow your score from 70 to 80 than it would be to grow from 20 to 30.
It is also important to note that if the higher authority sites that your site is seeded from drop in score, it will ripple down to all of the other links branched off from the very top. A good place to start is to compare the DA from the linking root domains from the previous index. Also take a look at your competitors scores to see how much they have dropped as well. As our indexes grow in size, there are more links that are included in our calculations. I think this is a big part of why we saw drops in Domain and Page Authority this time around - more links included in our calculations will skew the scores a bit lower.
We recommend keeping track of how many linking root domains you have from index to index, as this will be a quick way to confirm possible reasons for an increase/decrease in the score. For an in-depth discussion from Rand, check out this article: https://moz.com/community/q/da-pa-fluctuations-how-to-interpret-apply-understand-these-ml-based-scores I've found this article to be most helpful when I'm trying to determine why Domain or Page Authority scores may have fluctuated so much, especially when it's across the board like this.
Here's some places to really delve into what is going on:
http://moz.com/blog/whiteboard-friday-domain-trust-authority
http://moz.com/blog/googles-algorithm-pretty-charts-math-stuff
http://moz.com/blog/whiteboard-friday-domain-authority-page-authority-metricsHere are some good resources to help you take a look at the factors.
http://moz.com/blog/whiteboard-friday-domain-authority-page-authority-metrics
http://apiwiki.seomoz.org/w/page/20902104/Domain%20Authority
http://moz.com/blog/whiteboard-friday-domain-trust-authorityI hope this helps!
-
I'm also curious about any news/updates regarding this topic. So is there any news?
We suddenly dropped in DA from 40 > 34 (!) and our competitors lost a little less, from 3 to 5 DA points. We also lost like 185 external backlinks and so did our competitors.
Rankings are the same.
-
Any news around this topic yet?
We also dropped in Da from 29>27 and another of our sites even from 21>17 (both https). All of our competitors also dropped in DA (one 30>22).
No drops in rankings fortunately.
-
Dropped 3 points, so did all of our competitors. The number of links seemed to have taken a dive for all sites I follow.
Is anyone from Moz looking into this?
-
Yep. All HTTP. Drops of around 3 - 4 points across the board. It's almost reassuring that we're not alone.
-
Haha
-
bounces theory of chest on to his knee, then volleys into the back of the non-existent net, and celebrates with Gillon the fact they have ruled something out
-
Yeah, I can't see a pattern either. Most domains I track are still http including ours but the https ones I track have seen drops as well (4 out of 5, 1 has stayed the same).
-
Throws theory out of window
-
Our 10 point drop is on a https site
-
Are the websites you're all seeing drops on http or https?
The reason I ask is that I've seen a small drop on some http sites and a small rise on https sites. Wondering if there is a correlation?
-
Yep, the biggest drop we have seen is from 10 to 1 on a small website we haven't worked on in months. Mostly smaller drops but bigger than other months. I monitor some competitors as well and out of 24, 2 have stayed the same, 1 has improved, all others have dropped. Our websites have all dropped except for one (which has stayed the same).
Glad to know we're not the only ones!
-
Well, on the good side, there is only one way to go...
-
Yes, a new website we haven't worked on yet has dropped from 14 to 1. -.-
-
Thankfully not, only between 1 and 3.
-
Anyone got more than 10!???
-
Yep yep. I'm seeing drops across the board, for everyone!
-
Hi,
Yes i have just asked something similar. One client has seen a 10 point drop.Not an easy one to explain...
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
-
My DA dropped suddenly
Hi Everyone! DA of my site dropped from 7 to 1. I don't know what is the reason behind it? Can you tell me what is the main reason of dropping down?
API | | lucas77861 -
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 -
Sample API call error
from mozscape import Mozscape client = Mozscape('xxxxx', 'xxxxx') # Now for some anchor text results anchorResults = client.anchorText('http://www.moz.com') # Or for just specific columns anchorTermResults = client.anchorText('http://www.moz.com', cols=Mozscape.ATCols.term) this is the error I am getting **mozscape.MozscapeError: HTTP Error 403: Permission denied: fpalgkadgnamhiblgpakemcfeedbebdcfk** My python is installed in appdata/local/programs and it is an enterprise environment. Thank you in advance!
API | | Sreenivas.Bathula0 -
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 -
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 -
Extracting MOZ Domain Authority
Hi
API | | SteveWarren
I have looked but cannot find any reference to this, so I hope someone can help me.
Is it possible to upload a list of domain URLs and retrieve their MOZ Domain Authority?
Many thanks
Steve0 -
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