Moz Update
-
Hi, in the past we could see the next Moz update in https://moz.com/products/api/updates, but i can´t see it anymore there, has been changed to another place?
-
Ohhh yes, i see now thanks, but are imagination of myself or before you could see more?
-
You can still see it on the link you originally posted - the box with the text about the current index mentions it.
-
Hey there! Yep, you're right - that's still where we post updates about our index releases.
-
I just answer myself i feel kind of stupid i see the date in here https://moz.com/products/api
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
-
Can you tell me about the impact of Do-follow and No-follow backlinks for increasing Moz DA?
Have Do-follow backlinks and No-Follow backlinks same value to increase Domain Authority in Moz? Recently, I have created 290 profile backlinks which was do-follow. But from yesterday I have seen all backlinks are no-follow now according to the decision of sites' owners. My site's DA has already increased up to 35. Will this DA fall gradually from now? Apart from it, if I have created same backlinks for my another site; will my DA be 35? Please try to clarify it. My site is: https://kodnest.com Thanks. Waiting for your valuable answer from Moz official.
API | | FrankJOwens0 -
Are Moz-specific ids available in response sets from V2 calls?
I'm assuming that moz assign a unique internal id to each page, subdomain and root_domain. When making v2/links requests, are these moz-specific ids available? Currently, when gathering backlinks for a client we're generating our own ids. Maintaining uniqueness is costly time-wise. "results": [{
API | | StevePoul
"source": {
"page": "news.energysage.com/pros-cons-electric-water-heaters/",
"subdomain": "news.energysage.com",
"root_domain": "energysage.com", ... "target": {
"page": "mainlineplumbing.net.au/",
"subdomain": "mainlineplumbing.net.au",
"root_domain": "mainlineplumbing.net.au",0 -
Moz Api Integration with Google Data Studio
I want to automate my competition research process. Right now my competition research is completely manual which is ok if working in a small project. Usually, start looking at Google for the best sites for a specific niche. In an excel sheet insert the URL in a column and start to put information in next columns, information such as DA, PA, backlinks, page speed, schemas validation and stuff like that. As I mentioned for a small project I usually take 10 websites as a reference to analyze how difficult can be rank a website. The problem starts when I have to scale when I have to evaluate 100 or 200 or even more websites in different niches or target location or industry. Does not make sense keep doing manually. So my question is there any way to connect the Moz API to Google Data Studio or Google Sheet
API | | Roman-Delcarmen2 -
Old moz pixel?
We recently switched our website to secure https and noticed there is a pixel still firing that is related to moz but have no idea what it is for. https://moz.com/products/Mozscape/api/keymaster/Mozscape/credentials It is serving a 401 error status and going to remove off the site. Any idea what that was for? Thanks -
API | | APMSEOPRO
Nate0 -
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://moz.com/products/api/updates
API | | randfish8 -
Moz crawl error? DA & Linking domains significant drop.
Hi guys! Our site www.carwow.co.uk appears to have been punched in the face by the latest Moz update. It's claiming our #linking root domains has dropped from 225 to 135 and has subsequently hit our DA from 38 to 35. We haven't disavowed any links and our off-site strategy has been going well the past 2 months. Search performance has increased by around 15% (around 5k sessions) and rankings have improved week on week. Any idea if this is a Moz error? That's almost a 50% drop in linking root domains. Thanks, James
API | | Matt.Carwow0 -
Any idea why HubSpot (which uses the MOZ api) can find our backlinks but OSE can not?
Links are showing up in the HubSpot link tool within a couple of days. OSE has our site showing zero backlinks. ahrefs is finding them too but that makes more sense. Does the API update more frequently than OSE? Any thoughts? Thanks!
API | | KLEANTreatmentCenter0 -
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://moz.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