Just to expand on a couple bits of info alluded to above, there are basically two risks to consider, neither of them relating to the algorithms (those are safe).
First, is incidental data leakage. Do you run slaterockandgravel.com as Mr. Slate but have your key signed firstname.lastname@example.org? Did Betty sign your key and you don't want the world to know about that? These are unlikely cases, but consider them.
Second, perhaps more, is guard against somebody man-in-the-middle'ing your website, and presenting your friend with a fake key for you, which they plan to use to intercept his communications to you. Again unlikely, but two things you can do to avoid the problem: a) put it up under TLS -or- b) (better) upload your key to a public keyserver (sks or similar) and only put the key ID on your website (you can even provide a web link to the sks webservers with a lookup for your key id). People have already figured out key distribution, so leverage their work.
For most of these things, it probably won't be you who gets attacked this way, but it will be somebody, so each of us should act as if it will be us, and then we have a safer community.