Go documentation is very good, the standard library is extensive, and it has a very active community, but it does lack certain libraries that web developers might find attractive, e.g. a comprehensive ORM.
Insinuating PHP is better because it's deployed in more places is silly.
You sounded a lot like Go hasn't proved it's viable for "web scale." It has. Is it as widely deployed? Of course not, it's new.
I'm not sure what strength of PHP you're referring to--I'm assuming the ubiquity with shared hosting providers--but it's not even that great of a language to interface with databases, which was your example before.
Not arguing for Go particularly, just arguing against PHP. Its ubiquity is basically all it has going for it, but yes, that's a big deal.
("Poor library support" is a terrible argument for PHP vs. Python, Ruby, or even functional languages with respect to web development too.)
Now you're twisting your own words.
This depends on what is your definition of "widely deployed":
A type of web app for which Go shines is ones that have data already prepared when the user arrives. Database retrieval and update can be handled by processes that aren't dependent on the user. This can make the app super fast; e.g. langalot.com.
On the other hand, PHP has a huge list of existing resources, libraries and excellent documentation and community.
Look over at the language used by the largest sites on the Internet, and compare the number that use PHP to the number that use Go. Not saying Go can't handle those applications, but obviously PHP was used in scale effectively on many occasions, while Go hasn't proved anything yet.