Why does OSE show old data (Previous update results)?
-
Moz api started to show July 13 update results for my website. I checked it 2 days ago and saw all new established links and updated DA PA for July 27 update. But last 2 days both Moz Api and OSE main page show July 13 update results. Is there a maintenance or mismatching error between old and new databases?
-
It seems fixed now. I have just checked again and fortunately new update results appears.
-
We can certainly check on it if you provide the domain! I would recommend sending in the information to help@moz.com where you particular case can be discussed outside the public forum.
-
As i said before after 27 July update i checked several times and saw all new established links and increasing DA 5-6 points-up for my websites. But yesterday evening suddenly Moz Api and Ose started to show old data. Problem still persists.
-
We do not have a penalty system, but it's certainly possible that your metrics did not meaningfully change from one index release to another. It's all calculated based off the backlink profile we have for your site.
-
No way! Still it shows July 13 data for my all websites except one. That's very interesting. Is there any Moz penalty for some domains? I mean does moz have a penalty system?
-
Sorry for any trouble! While there can be a small time period after an index update in which the API is updated but the tools and apps built from it have not yet switched over to the new data, at this point everything from the July 27 update should be available from all sources. If you're seeing incorrect or inconsistent data, feel free to reach out to us at help@moz.com with the domains and URLs that you're seeing issues with, and we can look into it. Thanks!
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
-
What does "ffspl" mean in a url-metrics result set?
So I've got this server-side JScript object I've declared which works nicely for us. var mozObj = new MozInteraction()
API | | StevePoul
.setMethod("GET")
.setHost("http://lsapi.seomoz.com")
.setPath("linkscape/url-metrics")
.setCols(parseInt("11111111111111111111111111111111111111111111111111111", 2))
.setLines(10)
.setAccessId(accessId)
.setSecret(secret)
.setExpires((new Date()).addDays(1).valueOf())
.generateSignature(); etc etc The setCols call sets the Cols value to the maximum possible: 9007199254740991. The weird thing is that in the JSON response I get a whole pile of column names that I can't find descriptions for in the documentation at https://moz.com/help/links-api/making-calls/response-fields e.g. ffspl1 ffspl2 ffspl3 ... fuspl0 fuspl1 fuspl2 fuspl3 ... pfspl0 pfspl1 pfspl2 pfspl3 ... puspl0 puspl1 puspl2 puspl3... etc1 -
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?
API | | Agenciaseomadrid0 -
The April Index Update is Here!
Don’t adjust your monitors, or think this is an elaborate April Fool’s joke, we are actually releasing our April Index Update EARLY! We had planned to release our April Index Update on the 6th, but processing went incredibly smoothly and left us the ability to get it up today. Let’s dig into the details of the April Index Release: 138,919,156,028 (139 billion) URLs. 746,834,537 (747 million) subdomains. 190,170,132 (190 million) root domains. 1,116,945,451,603 (1.1 Trillion) links. Followed vs nofollowed links 3.02% of all links found were nofollowed 61.79% of nofollowed links are internal 38.21% are external Rel canonical: 28.14% of all pages employ the rel=canonical tag The average page has 90 links on it 73 internal links on average. 17 external links on average. Don’t let me hold you up, go dive into the data! PS - For any questions about DA/PA fluctuations (or non-fluctuations) check out this Q&A thread from Rand:https://moz.com/community/q/da-pa-fluctuations-how-to-interpret-apply-understand-these-ml-based-scores
API | | IanWatson9 -
Two days since the supposed update
And still no update. Less a question, more a comment. Feeling a bit of deja vu here.
API | | pfrance3 -
Is there a way to connect to MOZ Pro data via Tableau?
Looking to automate reporting data from MOZ Pro. Specifically, site audit and keyword ranking data. Would like to connect to MOZ Pro backend via Tableau. Not seeing an obvious way to do this. Any guidance?
API | | jevons0 -
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 -
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