Is it true that google moved to ssl encrypted protocol and doesn't release keyword data anymore?
-
Hi,
I have a couple trivial questions regarding google search and the way Moz keyword reports are working.1/ is it true that google moved to ssl encrypted protocol and doesn't release keyword data anymore?
2/ if so than how Moz still manages to collect this data? Is it because of api or some other “deal” with them? Or you're paying for it.
3/ Why is “traffic from organic search” only for one week? Or I am missing something .
http://screencast.com/t/rslio5ZSKAx
It would be great to:
a/ go month by month (my client is requiring monthly reports)
b/ compare one week/month with another to see if it's getting better or worse.Thanks in advance,
JJ -
Thank you Keri, I really appreciate you took time to answer my question so quickly.
JJ
-
The vast majority of keyword data from Google is now "not provided". There is still some that gets through, though less with every month. Data you're seeing is from the keywords that still get through, plus the keywords from other search engines.
We are working on monthly reporting (and you can get some monthly reporting via custom reports), but it's not available in general just yet. It's a high-priority project, as we realize it is an important feature.
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
-
Unknown data items in Links API response
So I'm on the documentation page at https://moz.com/help/links-api/making-calls/url-metrics . I've copied the bit fields table into a spreadsheet. I've removed all the "deprecated" items and have totalled up the remaining items making a Cols= value of 182537205900657000. For want of better knowledge, I've used that same value for LinkCols=, SourceCols= and TargetCols=. The request url ends up being (anonymized): http://lsapi.seomoz.com/linkscape/links/fordanddoonan.com.au?Cols=182537205900657000&AccessID=xxx&Expires=1557458487346&Signature=xxx&SourceCols=182537205900657000&TargetCols=182537205900657000&LinkCols=182537205900657000&Limit=1000&Scope=page_to_domain&Filter=external My question is, what do I make of all the extra fields that I get in the json packet what should I do to remove them? These extra fields are: lrid, lsrc, ltgt, luufq, luueid, lufeid, luujid, luumrp, luumrr, luflan, lufspf, lufsplc, lufspp, lufsps, lufspsc, luus, lufuid, lupuid, lufipl, luupa, lupda, luued, lufed, luped, lupib, luulc, flan, fspf, fsplc, fspp, fsps Is it simply a case of limiting the values of TargetCols, LinkCols and SourceCols? If so, to what?
API | | StevePoul1 -
How frequently is the Search Volume update for each keyword? API for Search Volume?
Subject pretty much says it all... How frequently is the Search Volume update for a given keyword? Is there an API call that would include keyword-specific Search Volume for one or more keywords? Thank you.
API | | ToddLevy0 -
January’s Mozscape Index Release Date has Been Pushed Back to Jan. 29th
With a new year brings new challenges. Unfortunately for all of us, one of those challenges manifested itself as a hardware issue within one of the Mozscape disc drives. Our team’s attempts to recover the data from the faulty drive only lead to finding corrupted files within the Index. Due to this issue we had to push the January Mozscape Index release date back to the 29<sup>th</sup>. This is not at all how we anticipated starting 2016, however hardware failures like this are an occasional reality and are also not something we see being a repeated hurdle moving forward. Our Big Data team has the new index processing and everything is looking great for the January 29<sup>th</sup> update. We never enjoy delivering bad news to our faithful community and are doing everything in our power to lessen these occurrences. Reach out with any questions or concerns.
API | | IanWatson2 -
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 -
Next button keywords doesn't work in new Campaign
Hi, Problem: I try to create a new campaign but when i put keywords in it, the « next » button stay “gray” and is inactive… I can’t press it. I’m using chrome. I deleted my history in my browser. I did some campaigns yesterday and it was ok. Please tell me what wrong. Martin Lapierre
API | | mlapierre0 -
What is Moz's Error.aspx?aspxerrorpath HTTP Status 302 error message?
Hi, I am not sure what this error message is: "Error.aspx?aspxerrorpath". It immediately follows pages that are given at 302 status in Moz's crawl report. The same pages have never had this error before: | http://www.homedestination.com/news/2013/Minneapolis-home-price-appreciation.html | | http://www.homedestination.com/mortgage-worksheet.html | | http://www.homedestination.com/foreclosure-eligibility.html | Each page has a 100% score with WC3. Could you give me more insight as to what Moz may suggest I do to give the page a 200 HTTP status as before? Thanks.
API | | jessential0 -
Using excel to pull MOZ data about links
I have a list of links 500 in excel that I would like to get the number of backlinks, PA and DA for the relevant link, is there a pre-built excel sheet that utilises the Moz Api that can pull this data easily? Thanks!
API | | ChrisClayts0