Domain Authority drop due to Moz update?
-
Hi guys,
I have noticed an unusual Domain Authority (DA) drop in mid November for many different websites here in Sweden. There was a Moz update the 12th of November which I assume has to do with this drop.
I have attached the DA history chart to visualize the drop.
Does someone have any information about:
- Did the drop in DA have to do with the update the 12<sup>th</sup>?
- Did the new update have a new type of metric calculation?
- Is anyone else experiencing this drop?
Any extra details would be helpful.
Thanks a lot guys.
-
Ultimately people complain about DA because they lack the understanding of what it measures.
DA paints a picture of the hierarchy of the web and your "ranking" within the web. This is how DA was designed. As professionals we have chosen to utilise this ranking but sadly people are using it without first learning fully what it means and as such fall into pitfalls
The scale is designed to represent the whole web. The web is to large to simply divide into smaller sections that allow you to have a scale in which you can climb. If you define a static ceiling or remove the ceiling you either end up with all websites above the ceiling forcing it to be redefined anyway or allow DA to climb so high that it is unobtainable anyway.
DA can tell you everything you need it to, as long as you stop looking at it as a figure only you can influence.
-
Good answer. I do think, though, that Moz might have to field less concerned individuals complaining about drops in DA if 100 represented a number of links no website will ever reach.
If the scale has to be normalised every time the index is crawled because the ceiling sites are snowballing links at a rate at which the rest can't keep up, perhaps it's time to look at the scale?
No earthquake can be Richter 10.0, and that's in the design. I understand that DA is also a logarithmic scale but clearly not one robust enough to prevent this constant renormalisation.
-
Hi Oscar,
I answered a similar question to this a week or 2 ago but cant find it. Ill keep trying but here goes again
Moz Authority shouldn't be compared a month to month basis. It is not a direct reflection of how well or badly your website is doing. What it is, is an indication of how much authority you have COMPARED to other websites.
Lets say facebook is the top website and has 5000 links pointing to it. This means that DA 100 = 5000 links
During the same month your own website has 500 links. And is DA 30.The following month facebook gains 1000 links. The benchmark for DA 100 now = 6000 links. Your own website gained 10 link but your DA dropped to 25.
Your website hasn't changed and you own backlink profile got stronger. However you lost DA. This is because the "standard" got higher. Likewise if the best website lost 1000 links and you did nothing your DA would climb.
As such you can't compare it month to month, but should compared it verses your competitors. As you saw from your attachment, all the website you are tracking dropped. So in relation to your direct competition you are still fine, there is nothing to worry about.
I would suggest that you consider the time of year. As Christmas approaches the internet goes link crazy as they begin to advertise and all sorts of reviews and recommendation are made. As such expect the best website particularly to gain massive amounts of links, this in turn increases the "standard". The result is, all website that havn't built as many links that month experience a drop in DA.
As long as you havn't experienced massive drops compared to competitors i wouldn't worry.
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
-
Get discovered and lost linking domains separately
Hello, We want to get "discovered and lost links" using api.
API | | OlegKireyenka
You do not have discovered and lost metrics available via the Links API and we call api for backlinks and then cross reference this with the links found the last time, we are able to get only NET links, but we want to get "just discovered and lost links" separately.
for example: inbound links for 27 July is 600, inbound links for 30 July is 750, okay, NET links from 27 July to 30 July = 750-600=150. And in this case "discovered and lost links" maybe: 400 and -250, 300 and -150, 150 and 0, and etc. Maybe I can not understand something, give example please. Thank!0 -
Moz Update
Hi, in the past we could see the next Moz update in https://mza.seotoolninja.com/products/api/updates, but i can´t see it anymore there, has been changed to another place?
API | | Agenciaseomadrid0 -
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
API | | thomas.deruiter0 -
Moz rank tracker API
Hi we trying to make a PHP script to get values of keyword rank for a certain country and URL like we do in Rank Traker under Moz Pro tools. Is there any reference i can use to build one myself.
API | | Moreleads0 -
Moz & Google Tag Manager
Does Moz take into account Google Tag Manager or will it keep flagging up duplicate content, etc?
API | | moon-boots0 -
August 3rd Mozscape Index Update (our largest index, but nearly a monthly late)
Update 5:27pm 8/4 - the data in Open Site Explorer is up-to-date, as is the API and Mozbar. Moz Analytics campaigns are currently loading in the new data, and all campaigns should be fully up-to-date by 4-10pm tomorrow (8/5). However, your campaign may have the new data much earlier as it depends on where that campaign falls in the update ordering. Hey gang, I wanted to provide some transparency into the latest index update, as well as give some information about our plans going forward with future indices. The Good News: This index, now that it's delivered, is pretty impressive. Mozscape's August index is 407 Billion URLs in size, nearly 100 Billion (~25%) bigger than our last record index size. We indexed 2.18 trillion links for the first time ever (prior record was 1.54 trillion). Correlations for Page Authority have gone up from 0.319 to 0.333 in the latest index, suggesting that we're getting a slightly more accurate representation of Google's use of links in rankings from this data (DA correlations remain constant at 0.185) Our hit ratio for URLs in Google's SERPs has gone up considerably, from 69.97% in our previous index to 78.66% in the August update. This indicates we are crawling and indexing more of what Google shows in the search results (a good benchmark for us). Note that a large portion of what's missing will be things published in the last 30-60 days while we were processing the index (after crawling had stopped). The Bad News: August's index was late by ~25 days. We know that reliable, consistent, on-time Mozscape updates are critically important to everyone who uses Moz's products. We've been working hard for years to get these to a better place, but have struggled mightily. Our latest string of failures was completely new to the team - a bunch of problems and issues we've never seen before (some due to the index size, but many due to odd things like a massive group of what appear to be spam domains using the Palau TLD extension clogging up crawl/processing, large chunks of pages we crawled with 10s of thousands of links which slow down the MozRank calculations, etc). While there's no excuse for delays, and we don't want to pass these off as such, we do want to be transparent about why we were so late. Our future plans include scaling back the index sizes a bit, dealing with the issues around spam domains, large link-list pages, some of the odd patterns we see in .pl and .cn domains, and taking one extra person from the Big Data team off of work on the new index system (which will be much larger and real-time rather than updated every 30 days) to help with Mozscape indices. We believe these efforts, and the new monitoring systems we've got will help us get better at producing high quality, consistent indices. Question everyone always asks: Why did my PA/DA change?! There are tons of reasons why these can change, and they don't necessarily mean anything bad about your site, your SEO efforts, or whether your links are helping you rank. PA and DA are predictive, correlated metrics that say nothing about how you're actually performing. They merely map better than most metrics to Google's global rankings across large SERP sets (but not necessarily your SERPs, which is what you should care about). That said, here's some of the reasons PA/DA do shift: The domains/pages with the highest PA/DA scores gain even faster than most of the domains below them, making it harder each index to get higher scores (since PA/DA are on a logarithmic scale, this is smoothed out somewhat - it would be much worse on a conventional scale, e.g. Facebook.com 100, everyone else 0.0003). Google's ranking algorithm introduces new elements, changes, modifies what they care about, etc. Moz crawls a set of the web that does or doesn't include the pages that are more likely to point to a given domain than another. Although our crawl tends to be representative, if you've got lots of links from deep pages on less popular domains in a part of the web far from the mainstream, we may not consistently crawl those well (or, we could overcrawl your sector because it recently received powerful links from the center of the web). My advice, as always, is to use PA/DA as relative scores. If your scores are falling, but your competitors' are falling more, that's not a bad thing. If your scores are rising, but your competitors' are rising faster, they're probably gaining ground on you. And, if you're talking about score changes in the 1-4 points range, that's not necessarily anything but noise. PA/DA scores often shift 1-4 points up or down in a new index so don't sweat it! Let me know if you've got more questions and I'll do my best to answer. You can also refer to the API update page here: https://mza.seotoolninja.com/products/api/updates
API | | randfish8 -
About Expiry of MOZ API authentication and MOZ API call in .NET application
MOZ API signed authentication is getting expire after particular time, and coming up with the error "Authentication has expired , Re-send your authentication". **right now we are getting new authentication details using ** https://mza.seotoolninja.com/products/api/keys after doing login. but, how do we get new credentials (authentication details) , by doing MOZ API call using c# or any other programming language, we are using this API in .NET. Also, How we can increase the session expiry time. i think it is concerned with the Sample Expires of Signed authentication , but we are unable to change it , as it is coming with the authentication failed.
API | | BenuAggarwal0 -
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://analyti/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a> freya.RoutesUtils.applyDefaultParams<a class="console-message-url webkit-html-resource-link" title="http://analyti/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a> freya.RoutesUtils.make<a class="console-message-url webkit-html-resource-link" title="http://analyti/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:223">application-c42010fe6b0d425aca7cad19e29223b3.js:223</a> freya.Routes.settingsCampaignPath<a class="console-message-url webkit-html-resource-link" title="http://analyti/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://analyti/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://analyti/assets/application-c42010fe6b0d425aca7cad19e29223b3.js:231">application-c42010fe6b0d425aca7cad19e29223b3.js:231</a> (anonymous function)<a class="console-message-url webkit-html-resource-link" title="http://analyti/pro/home:213">home:213</a> fire<a class="console-message-url webkit-html-resource-link" title="http://analyti/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:60">jquery-b68cd156547e7de90502ecf7becf0beb.js:60</a> self.fireWith<a class="console-message-url webkit-html-resource-link" title="http://analyti/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:66">jquery-b68cd156547e7de90502ecf7becf0beb.js:66</a> jQuery.extend.ready<a class="console-message-url webkit-html-resource-link" title="http://analyti/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:22">jquery-b68cd156547e7de90502ecf7becf0beb.js:22</a> DOMContentLoaded<a class="console-message-url webkit-html-resource-link" title="http://analyti/assets/jquery-b68cd156547e7de90502ecf7becf0beb.js:53">jquery-b68cd156547e7de90502ecf7becf0beb.js:53</a>1