I've noticed sometimes half of my keywords will show as being -9999. if I check it with the api elsewhere they're ranking fine. if the api doesn't return results, or returns an error, does the KWT enter -9999? if it does, could we get that changed? really disconcerting and makes the graphs look weird
It always happens to me. But I know Shawn have told that the problem here is on Google not his script. Wait for a few minutes or days and it will return to its normal state.
I understand there are problems with the api that aren't his fault, but I was wondering if this was a case of error handling that may be able to be fixed on the KWT's side
It's not possible because the only way you could get results from Google is through Google API. Otherwise if you used any way to connect to Google then you will be banned by Google. Hope that makes sense.
Can you post a picture of one of the graphs that looks weird by chance? The graphs should ignore any of those entries for that exact reason...
oops, looks like I was wrong about the graphs-- just checked, those were a few that legitimately dropped out. is there any way to make the results not update and show "error" instead of -9999 though? it'd be nice to be able to differentiate between actually dropping out completely versus just having an error.
While it sound like a good idea in theory, storing an error flag (even if 1 byte) on a per record basis would grow the database massively... there are close to 1 billion records of individual daily results (many, many, many gigs for that database). Adding a field to store the status of the API request is a lot of data to store for not very much gain...
So this is the story why this was not implemented. Thanks for the info. Now I know what to tell my friend whenever they ask question why DP keyword tracker is showing -999999. Thanks Shawn.
That's not necessarily the reason... in *most* cases it just means whatever it was looking for wasn't found in the top (however deep you look).
wouldn't it be possible to store it in the DB using some unique int (that isn't possible to get naturally) and have it parse that output to show the error when reporting?