Tag Archives: negative threshold

How To Prevent Google Blocks And Avoid “Forbidden” Results

Some GTrends SE users have emailed me asking why they sometimes get “Forbidden” results and how to get rid of them. In a nutshell – you will get a “Forbidden” result when Google decides to ban your IP address (temporarily) because they detect that you are using an automated tool to search Google.com. GTrends SE needs to do Google searches to determine the “Competition” numbers.

In this tutorial I’ll explain how to prevent this block. Google’s proprietary detection algorithms are hard to fool, but the tricks I’ll mention below should be effective for most users.

Use longer Google grace period

The “grace period” is how long the application will wait between consecutive requests. Longer grace period = less likely to be blocked. 12 to 16 seconds work well in most cases. The setting is found under Settings -&gt Speed. Note that you can safely set the Google Trends grace period to a lower value (e.g. 2 seconds) to compensate for any loss in speed.

Enable “Always check searches first, competition second”.

This option works very well together with the next trick, below.

Use “Negative thresholds“.

The idea is to decrease the number of searches that GTrends SE needs to do by quickly eliminating worthless keywords. This helps decrease the time needed to process a list of keywords and decreases the chances of getting a Google ban.

You can find this feature under Settings -&gt Criteria. Make sure the “Enable this feature” box is checked, set “Action” to “Don’t check the keywords any further” and set the “Less than X searches per day” value as high as you can afford to. For example, if you set it to “70 searches per day”, keywords that have less than 70 searches/day will not be fully checked – GTrends SE will stop analyzing those keywords as soon as the number of searches is determined.

There are no explicit rules on what numbers you should set in the “Negative threshold” section – choose what makes sense for the niche you’re researching.

Get a good proxy

Using an anonymous proxy is a very effective way to avoid being blocked by Google (though you need to switch the proxies now and then so that the proxies themselves don’t get banned). The real challenge is finding a good proxy – most of the freely available ones are of dubious quality and may have been already banned, even before you try to use them. I’ve already written a few posts on this topic :

How to configure GTrends SE to use a proxy
Another tutorial on GTrends SE and proxies (includes links to some proxy sites)

While a few users have had success with commercial, subscription-based proxy providers, I’m reluctant to recommend a specific site. A few Google searches will likely turn up a number of proxy services – e.g. Socksify – use at your own risk.

Using The Negative Threshold

This tutorial explains the new Negative Threshold feature of the GTrends SE keyword research tool, and how to use it.

What It Is

This feature allows you to set a threshold (both for searches and competition) and apply special treatment to keywords that are below that threshold. You can make GTrends SE remove those keyword phrases from the list automatically, or not analyze them any further, or don’t do anything special except stating “Below Threshold” in the Verdict column. This frees up resources and can significantly decrease the time required to process a keyword list.

Negative Threshold Settings

You can configure the threshold options in the Settings window, under the Criteria tab. Here’s how they look :
Negative Threshold settings

And here’s what they mean :

  • Enable this feature – check this to enable this feature. If it’s not enabled none of the other options mentioned below will have any effect.
  • Less than X searches per day – the search threshold. Keywords that have less than this many searches will be considered below threshold. The default is 10, and you can enter 0 (zero) to ignore the number of searches a keyword has.
  • More than X phrase-matching results in Google – the competition threshold. Keywords that have more than this amount of competition will be considered below threshold. The default is 100 000 (which is quite a lot), and you can enter 0 (zero) to ignore this part of the threshold calculation.
  • Action – what to do with keywords that are below threshold. There are three possibilities here, all are pretty self-explanatory :
    • Just mark the keywords as below threshold.
    • Don’t check the keywords any further.
    • Delete the keywords.

    Choose whichever suits you best. The default is “Don’t check the keywords any further” – a middle-ground option that is faster than just marking the below-threshold keywords and safer than deleting them outright.

Choosing the exact settings is a matter of personal preference and what is needed in the current situation. Setting the search threshold higher and/or lowering the competition threshold number will cut off more useless keywords and make the research process faster.

On the other hand, if you use a very “aggressive” threshold configuration you might miss some potentially good keywords that just didn’t make it. Therefore I advise that you use a threshold that is more lenient than your good keyword criteria.


All Verdict values are recalculated when a keyword list is loaded from a file, and any configured threshold action will take effect immediately. This has one important implication – if you have set the Action to “Delete the keywords” and you load a keyword list that has some below threshold keywords, those keywords will not be loaded.

Another thing to note is that if you change the threshold settings while GTrends SE is running, it will only affect any newly checked keywords. Known verdicts will not be updated. If you want to recalculate them, you can either save the keyword list to a file and reload it, or select they keywords, right-click them and choose “Recheck keywords” from the popup menu (re-checking them can take a while).

Well, that explain how to use this feature to speed up your keyword research process 🙂