Sorry, got it wrong.
Apart from the examples working at Google.com, the actually don't ... |
No, actually you are right!
At FindForward, I never get wildcard omissions, even for e.g. "god * america". |
By the way, we are seeing even stranger things, many a times google refuses to respect many other operators, especially operators with (-) minus prefixed.
Have you guys seen this type of behaviour?
|
I don't know if it has anything to do with what you're seeing, but I'm getting some strange results, too: Searching for a certain phrase returns about 750 results, searching for the phrase and an additional " -lyrics" (without quotes) returns about 5600 results.
But then, that might just be the usual skewed Google page count math.
Wildcard search still doesn't work most of the time. |
Stranger from India, do you have some sample queries for the behavior you are seeing?
Andreas, yes, that sounds like the usual flaws of PageCount math... |
If you 'refresh' your 'Preferences' – evrything seems to work as per normal e.g.
"the * are green" --> "the trees are green" |
The wild card still seems broken. I think people may have initally seen it work or not work somewhat randomly, depending on what software version the server they were routed to was running.
It seems to consistently fail for me now. I have a suspicion Google might view this as a "feature" rather than a bug.
I have been able to work around it at times by using an additional exclude phrase, e.g.:
"fat * cat" -"fat cat" |
i tried it just a few days ago and it was working with <god * america> (no quotes) twas pretty funny becuase i was demonstarting to a friend that it didnt work and it worked. But if you search for <"god * america"> it doesnt work. |
use brackets... [word1 * word2] |
