Hacker News new | past | comments | ask | show | jobs | submit login

True, what I want to say is.

If you have a ton of user uploaded media (and such), you probably want to not want SE to index everything. (For example to save bandwidth).

I should probably re-word that line, but I dont want to get too technical.




> If you have a ton of user uploaded media (and such), you probably want to not want SE to index everything. (For example to save bandwidth).

Bandwidth is cheap. Ranking poorly in search engines is not.

If you've got a ton of user uploaded media, you've potentially got a ton of content for Google to pick up on and rank you for.


If you aren't able to control user spam effectively, Google will think you are the spammer. (maybe another item should be: use nofollow on user links)


For something like an image hosting or pastebin site, isn't that possible a privacy concern?

I'm curious, what is the standard practice for the storage of static media - where are the static files (text/images) stored on the server, and how are the appropriate config files that concern that media set up?


If you don't want the world to see your files, actually stop them from being accessed instead of politely asking robots to not index them.


If the images are relevant then you're tossing earned SE traffic and extra value in the other ranking signals Google uses. If you have 1000 posts on gardening and an image for each with gardening in the filename, you're going to have an easier time ranking for gardening.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: