Google AdWords Team Points Out Flaw in Google Keyword Tool

November 23, 2009 by: admin

A Google AdWords API Help thread estimated position or average CPC being returned by the AdWords API differs from that of the Google Keyword Tool.

Eric Koleda from the Google AdWords API Team replied basically pointing fault at the tool.

I think the problem here lies in the Keyword Tool’s web interface.

You’ll notice that changing the match type drop down from Broad to Phrase or Exact does not change the estimated position or average CPC. It is unlikely that the match type has no effect on these parameters, and in the API changing the match type does change the returned position and CPC values. My guess is that the web tool is always using the Broad match type for getting estimates, and that the numbers returned by the API are accurate.

I validated that the Google keyword tool does not change the estimated position or average CPC when you change the match type from broad, exact, or phrase types. Logically, it would make sense that this means the keyword tool is off when reporting on those factors and narrowing the results by match type.

It seems if you want to get more accurate numbers for estimated position or average CPC you would have to use the AdWords API.

Forum discussion at Google AdWords API Help.



Related posts:

  1. Google AdWords Tax Calculator
  2. AdWords Keyword Phrase Not Triggering Ads? You May Be Banned
  3. Some Keywords in AdWords Ads Diagnostic Tool Require Content Network?
  4. Some Users Having Issues With Google’s Keyword Tool
  5. Google AdWords New Beta Keyword Tool
  6. Google Adds Keyword Predictions to Search Insights Keyword Tool
  7. Free Keyword Research Tool for Bloggers
  8. Do You Trust Google’s Keyword Tool?
  9. Google AdWords Advertiser Statistics, via SEM Rush
  10. Google Improves Search-Based Keyword Tool
  11. Wikirank is the most accurate keyword research tool ever
  12. Google Confirms Keyword Tool Issue is a Bug

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.

Trackbacks

Leave a Reply