Quote:
Originally Posted by Socks
Working on a site where every image of every gallery is on its own MD5'd URL.
|
Why? I tried this; I found I got much better SE traffic by naming the files say, {RANDOM}_model_name_scene.jpg; this also doubles as an Anti-Fusker system.
Quote:
We have a main set page for each gallery, and then each image also has its own URL.
All the images have the same sort of information on the page, we obviously don't write anything per image. However people can write comments per image, so there could be some content there. They all have the same title though, for example.
So it seems you're supposed to robots those individual image pages out, and only have the main set page indexed?
Or is it better to follow,noindex?
|
The Robots will ferret out these individual pages; but it's not often you see anybody searching for, or often clicking on an MD5 generated URL.
Quote:
If you just robots it out, does that mean google images etc won't pick those images up, hence the follow,noindex?
Other important things to think about in this kind of structure?
|
If you robots it out; Google won't see it. They won't put it anywhere. However, if your images are referenced on another site, last I had this happen, they indexed it by proxy via the link - at least, that's the only way I saw that (single) set in google images.
If you want Google Images to see it, but do a redirect, you can do that pretty easily with mod_rewrite.
You want to make the URLs as descriptive as possible, not as obfusicated as possible.