Domain Authority Decreased on May 5 Update
-
Why the Domain Authority of my website decreased? Last month my website www.i-phony.com domain authority was 32/100. but today I see the result is only 23/100 . What was the reason behind this big decrease !!
Your answer is highly appreciated and very valuable for me.
Best regards
-
Hi Everyone
The weekly delays and the smaller Index are completely separate, but importing the index data into Moz campaigns are affected. A smaller index was necessary for us to release it without further delay. This release has 187 billion links instead of what we originally had planned which possibly between 250-300 billion links. We hope our next index will be intact and released on schedule.
Here are the index details: https://moz.com/products/api/updates
-
Hello,
I looked this up with open site explorer and it appears a lot of your linking domains look pretty spammy. One step would be to disavow those links and focus on getting better one's. (Your top few are really good links.)
Thanks,
- Mike Bean
-
I don't know if it is the reason but I noticed the sites that showed up as backlinks to my site after yesterday's update were much different than those from before the update. After the update my site showed fewer backlinks but my domain authority actually went up. It's possible the Mozscape index crawler visited different sites than it did previously and fewer/lower Domain Authority links were discovered for your site. Either that or your site lost some quality links since the last update.
Have you been monitoring your links with other tools? That could help determine if it's a loss of links or just different links being used to calculate your DA. Either way that seems like a big drop in DA.
-
Hi there
It more than likely happened because of the issues Moz is having.
But to answer your question beyond that (and if your site continues to see a lower DA), there's no one direct way to answer and fix this. You're going to have to do some research.
Learn about the following:
Domain Authority
Page AuthorityAs stated by the DA page...
"Unlike other SEO metrics, Domain Authority is difficult to influence directly. It is made up of an aggregate of metrics (MozRank, MozTrust, link profile, and more) that each have an impact on this score. This was done intentionally; this metric is meant to approximate how competitive a given site is in Google.com. Since Google takes a lot of factors into account, a metric that tries to calculate it must incorporate a lot of factors, as well.
The best way to influence this metric is to improve your overall SEO. In particular, you should focus on your link profile—which influences MozRank and MozTrust—by getting more links from other well-linked-to pages."
Take a look at the following resources:
On-Page SEO
Content Audit
How to Conduct a Backlink Audit Link Audit Guide for Effective Link Removals & Risk MitigationThere are a lot of factors that could go into this, so you need to put your SEO research hat on and dig in!
Hope this helps! Good luck!
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 Regarding Moz API token password update
Hi, In March we have updated password for MOZ API and used in our application it worked, but currently the updated password is not working and in the MOZ site the old password is shown and its active. We are using Legacy username and password.
API | | NickAndrews
We see that 5 tokens can be added for API, if we add 2 tokens both will be active.
We are currently using free services. Please help us resolve this issue.0 -
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 -
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,
API | | NielsVos
Niels3 -
Oct 14 2015 MOZScape update: none of DA are changed?
Hello, everybody. Today I noticed that finally the latest release of mozscape update has been posted. Now, I noticed that NONE of 25 campaigns websites NOR any of their competitors DA has changed. I do understand that DA can stay the same, but 25+25*3=100 websites domain authorities hasn't changed at all since August 4th (the date of previous mozscape release)? Or is this happening only to me? Please advise.
API | | DmitriiK2 -
September's Mozscape Update Broke; We're Building a New Index
Hey gang, I hate to write to you all again with more bad news, but such is life. Our big data team produced an index this week but, upon analysis, found that our crawlers had encountered a massive number of non-200 URLs, which meant this index was not only smaller, but also weirdly biased. PA and DA scores were way off, coverage of the right URLs went haywire, and our metrics that we use to gauge quality told us this index simply was not good enough to launch. Thus, we're in the process of rebuilding an index as fast as possible, but this takes, at minimum 19-20 days, and may take as long as 30 days. This sucks. There's no excuse. We need to do better and we owe all of you and all of the folks who use Mozscape better, more reliable updates. I'm embarassed and so is the team. We all want to deliver the best product, but continue to find problems we didn't account for, and have to go back and build systems in our software to look for them. In the spirit of transparency (not as an excuse), the problem appears to be a large number of new subdomains that found their way into our crawlers and exposed us to issues fetching robots.txt files that timed out and stalled our crawlers. In addition, some new portions of the link graph we crawled exposed us to websites/pages that we need to find ways to exclude, as these abuse our metrics for prioritizing crawls (aka PageRank, much like Google, but they're obviously much more sophisticated and experienced with this) and bias us to junky stuff which keeps us from getting to the good stuff we need. We have dozens of ideas to fix this, and we've managed to fix problems like this in the past (prior issues like .cn domains overwhelming our index, link wheels and webspam holes, etc plagued us and have been addressed, but every couple indices it seems we face a new challenge like this). Our biggest issue is one of monitoring and processing times. We don't see what's in a web index until it's finished processing, which means we don't know if we're building a good index until it's done. It's a lot of work to re-build the processing system so there can be visibility at checkpoints, but that appears to be necessary right now. Unfortunately, it takes time away from building the new, realtime version of our index (which is what we really want to finish and launch!). Such is the frustration of trying to tweak an old system while simultaneously working on a new, better one. Tradeoffs have to be made. For now, we're prioritizing fixing the old Mozscape system, getting a new index out as soon as possible, and then working to improve visibility and our crawl rules. I'm happy to answer any and all questions, and you have my deep, regretful apologies for once again letting you down. We will continue to do everything in our power to improve and fix these ongoing problems.
API | | randfish11