I don't believe these results are an accurate representation of the Google Maps geocoder or map data. And it's absolutely not the case that an incorrect result

I don't believe these results are an accurate representation of the Google Maps geocoder or map data. And it's absolutely not the case that an incorrect result is considered better than no result. I spot-checked on the Google API a few entries that the spreadsheet showed in the wrong country (Waldemar, Coldstream, Osceola, Snow Road Station, Belgrave, Winger, Heidelberg, Priceville, Vernon, Blackwater). I only got one result that was wrong (Vernon) with the default settings. With a country bias to Canada, which I hope would have been there for an API user from that country, that one is resolved to a sensible looking locality as well. There clearly are some queries in that set for which Google returns the wrong answer, but I'd be the frequency of those problems is an order of magnitude lower than this post suggests. It'd be interesting to know what the reason for this discrepancy is, but without seeing the exact queries on the wire one can only speculate.