It annoys me to see the language called Golang, when it very clearly is just plainly Go. That said, the only way to find anything on Google is to search with "golang <issue>".
Which is exactly why everyone calls it "Golang". If you never refer to it as "Golang", any search for which your content might be a reasonable result is going to lose itself in all the other uses of the word "Go". It annoyed me to see it called "Go", as it does whenever I see a tool choose an extremely commonly used or ambiguous word for it's name.
There have been a huge number of projects with this issue - e.g. fedora's directory service, called 389.
But I think far and away the worst offender for me was chef. In the early days of using chef, googling for chef cookbook was a total disaster.
I know it sounds nice, and probably super cool when you're talking to your friends to name your project a memorable common word, but for anyone reading this that's in the middle of a new project - please try to at least think about people who might want to google the name...
I think the most significant example of this for me, historically, has been gnu screen. Googling for help with problems or configuration for screen has never been easy, no matter how popular it's become. And there's no obvious disambiguation, either. It's rare for it to be called "GNU Screen," so you're severely limiting results by using that. And actual screens of both the door and display variety, break, are broken into panes, etc.
Not going to lie, it's a smallish part of the reason I switched to tmux.
Square released some dashboard-graphing software they wrote called Cube. Which is a clever name, sure, but google 'square cube graphing' and you have no chance whatsoever of getting an answer related to what you want to learn about.