If I search for blue widgets, the ad shows, if I search for some words blue widgets (nothing in quotes), the ad does not show. There are no other advertisers in this niche.
The additional words are not negatived out in this ad group.
Any suggestions?
Ash
Try after increase the bid according to the some value. HTH
Yes, the leading words are slightly more expensive but I have a separate ad group for them.
The ones I am using are rock bottom priced and are in the hundreds.
They are valid search terms and there is good traffic. Very few people would use the prefix because they are redundant. To use a food example, the cheap term is "KFC Restaurants" and the redundant suffix is "Fried chicken in".
So I might have to live without the few people who use the extra words in this combination.
What puzzles me is why doesn't such a search trigger the more expensive ad for the prefix?
As we strive to provide more relevant ads, we have altered the nature of the broad match keyword. To provide a more relevant experience for the users, we will stop showing ads on broad variations of the keyword for which the ad has historically not performed well. This system was designed to decrease the number of irrelevant ads showing based on broad match keywords, as well as limit the number of potentially irrelevant clickthroughs you might receive.
Looks like I'll have to do some Powerposting to cover the longer phrase too.
I have narrowed down the problem to the word "in", e.g.
(ad is for North Utopia)
blue widgets in North Utopia = no ad
blue widgets North Utopia = ad shows
North Utopia = ad shows
Since you're not being shown in broadmatch for the search with "in", have you tested to see if a phrase match for either "blue widgers" or "north utopia" show "blue widgets in North Utopia"?
have you tested to see if a phrase match for either "blue widgers" or "north utopia" show "blue widgets in North Utopia"?
Yes, I have widget in magic number 1234 (broad).
Ad shows for:
widget in magic number 1234
widget in magig number 1234 (typo)
Does not show for:
widget in magic numbea 1234 (typo)
widget in magic number 12345 (no numeric "stemming")
widgets in magic number 1234 (no plural)
widget in magic number 1234s (no plural)
widget of magic number 1234
widget near magic number 1234
widget magic number 1234 *
widgets magic number 1234 *
magic number 1234
magig number 1234 (typo)
magig number (typo)
number 1234
1234
blue widget in magic number 1234 **
blue widgets in magic number 1234
* Contrast with earlier example blue widgets north utopia, which works. Therefore there is truth in the explanation that only certain broad match terms that did not perform well in the past have been modified.
** This surprises me.
Test for magig number (broad):
Ad shows for:
magig number
Does not show for:
widgets in magig number 1234
Goes to show that we can't generalise how broad match will work. Test, test, test.
I think the system is becoming more complicated that it needs to be. If I broadmatch a term, I want it to run like a broadmatched term - and not autofiltered results.
I did a little testing, and I noticed that when I used any word in my kw list that brings up: "in" is a very common word and was not included in your search - on the search results page of G, then my add seemed a bit random when it was shown.
So if I run a broadmatched add for, magic widget city, it was shown for the search (at least for the KWs I was trying), magic widget in city.
If I made an add for, magic widget in city, then I ran into the same problems with the ad not displaying in some searches. Magic was a niche word searched under 25k times month/G.
I had hope for broadmatch, and then I tested it with 'magic state'. (where magic is a much more searched term well over 100k/month)
I got different results for:
magic state
state magic
state in magic
magic in state
state of magic
magic of state
In some cases no ads were displayed, and in others, some ads did display and others didn't.
This seems to suggest what AWA was talking abot in the other post linked above. In the first example, G had not learned the KW yet b/c it wasn't searched enough. In the 2nd, it had started to filter how the results appeared.
Maybe common words that G dismisses in a search are causing the problem. Think AWA needs to look into this one.
Based on what I see here, I think the explanation is to be found in the quote provided by anallawalla in post #4:
As we strive to provide more relevant ads, we have altered the nature of the broad match keyword. To provide a more relevant experience for the users, we will stop showing ads on broad variations of the keyword for which the ad has historically not performed well. This system was designed to decrease the number of irrelevant ads showing based on broad match keywords, as well as limit the number of potentially irrelevant clickthroughs you might receive.
And yes, this is the same subject addressed in the earlier thread you posted, eWhisper.
As mentioned in that previous thread, it boils down to one thing: a system that is always working to show relevant ads to the more than 200 million people a day that search on Google. Towards this end, the system essentially shows the broad match variations that have worked well, while not showing the ones that haven't.
If there are variations that you 'must' show for, I'd suggest adding them as exact matches. This'll give them 1000 impressions to prove themselves.
AWA
