Welcome to the Q&A Forum

Thanks - I always forget to check Mozcast - looks like it's been a rough August so far!

Hi there! Tawny from Moz's Help Team here. That page is taking you to your Mozscape API credentials - when you follow that link, you'll get one set of credentials, and when I follow it I see my own credentials, etc. It's related to our API. If you're not using the API, feel free to remove that link - it really only serves to take you to your credentials information. If you've still got questions, feel free to write in to help@moz.com with all the details of what's going on - we'll be better able to investigate any potential issues through a support ticket.  Thanks!

There's currently no issues on our end with our API. Since MozCheck.com is not actually run by us and runs by using our API, you'd have to contact them in order to understand what's up with their site. Sorry for not being able to give you better news.

Anytime!! Have a great weekend!

Hi there! Kristina from the Help Team here. I apologize for the delay! Unfortunately at this time, our API is only going to be showing you link data. So, the information you're looking for it to provide on Keyword Tracking isn't going to be available through our API. I sincerely apologize for the inconvenience as I'm sure you were hoping for a different answer. In the future, feel free to contact our team anytime by emailing help@moz.com and we'll be happy to assist from there! Thank you, -Kristina

Thanks  Kristina, Working fine. Keep up the good work.

Hi there - Kristina from Moz's Help Team here. A batch of 10 URLs will count as 10 rows and you would need to wait 10 seconds before making the next query. If you make your next query too quickly you will be hit with a throttle which lasts 30 seconds. If you make another query during that period, you potentially could push that 30 second throttle even further out. I hope this helps! In the future, feel free to email our team anytime at help@moz.com and someone from our team will be happy to help out! Have a great day. -Kristina

Thank you for this update. I have Tumblr, Blogspot etc. that I use as part of my strategy and it is quite disconcerting this morning to see an individual post on a Tumblr blog with a PA of 94.  It's like looking in your bank and seeing a balance of 100K.

It's no trouble at all, yamayamax! Happy to help any time

Hey there! Your traffic data in your campaign is imported directly from your Google Analytics account. We don't change or alter it, so if you're seeing dropped traffic there can be a few different causes. If your traffic in your Moz campaign is lower than what you're seeing in GA, this is likely due to a connectivity issue the prevented us from collecting your traffic data on a daily basis. Oftentimes this is caused by expired or invalid tokens. We recommend reconnecting that token to restore traffic data. You can double check this by heading into your Traffic from Search section and switching the timeframe to daily. You may see missing data points from the days it wasn't connected. If your Moz traffic matches what you're seeing in GA (as it sounds like is the case for you), this might be an issue on GA's end. We would recommend troubleshooting with Google to find potential causes. Traffic drops can also be due to SEO-related issues. Unfortunately, we can't diagnose SEO root causes for you, but you can definitely use Moz Pro to research why it might have happened. Did you have an increase in crawl errors that might be preventing people from reaching your site? Did a competitor make big strides recently? The Q&A forum is a great place to reach out to SEO experts who might be able to help. You might also consider reaching out to an SEO consultant to look into the issue!

Hi, This is a recurring question on the Moz Q&A - you might want to check Rand's post about fluctuation of the DA in relation to index updates: https://moz.com/community/q/da-pa-fluctuations-how-to-interpret-apply-understand-these-ml-based-scores Dirk

Glad to hear it on all accounts.

Thank you Danny.  Exactly what I was looking for and fast too!

Hey There, Happy to help answer your questions regarding our API. Our Free API Access will not lead to any charges unless you reach out to us and ask for additional rows to be added to your account. So there should be zero surprise charges from the API product. What happens when I get near my usage limit? - Usage can be monitored here - https://moz.com/products/mozscape/usage What happens when I just hit the limit? Once you pull 25k rows for the month, your account will be suspended until the following month.  **What happens when I past the limit? **Unless you reach out and ask for additional rows, your account will be suspended until the following month, where you will get another 25k rows to use. Let me know if you have any other questions about the API. Ian W.

Hi there, Andrea from the Moz Help Team here, thank you for bringing this to our attention! I'm sending it up to our engineering team to take a look into this.

Hi Simon, that is very strange! Would you kindly send an email to help@moz.com so we can see what is going on? Thanks. Christy

Hi Trevor, Andrea from the Moz Help Team here Our Index rolled out yesterday and the blog post went live this morning, I'd recommend checking that out as well as the Q&A thread from Rand that it mentions which covers fluctuations (or non-fluctuations) with PA/DA scores. Hope that helps but we're available to assist if there are any other questions!

I wish I had an answer to that If I had to guess, I'd say sometime in the next 2 years, but not anytime in the next 9 months. We've stopped asking the team for a final delivery date because it's just too hard to estimate all the work required, and past estimations have been so far off target. Instead, we just try to estimate the next quarter worth of sprints and then measure how we perform against those. It turns out, replicating a processing system like Google runs without billions in revenue is really hard

OSE seems to be locating your links - up to over 3500 from the other day when I saw was like 300. So I would say when the index refreshes next, you'll see this return. If not, hopefully tech support can help more because it's definitely a weird issue. Headers look fine, robots is ok, no meta robots blocking it & I can crawl with Screaming Frog ... so yeah. No reason other than the glitch that I can see.