Pitfalls of Allowing Directory Sublistings on Website Files

[maxsun]

Are there any pitfalls to allowing directory sublisting of files?

For instance, Apache defaults to allowing browsers to view all files under http://www.website.com/images.

I turned off that feature yesterday (i.e., don't show a subdirectory listings). This morning I noticed my log file was DRASTICALLY reduced in size.

I'm just worried I killed something important--like the google bots/spiders can't access the subdirectories now. I use FF and haven't noticed any problems browsing the website. My second thought is that someone has been accessing my files somehow in ways that weren't intended...

Anyone else have any ideas/comments?

Thanks,

[brian.mark]

I'd go with your second thought there. It's possible that some image bots (i.e. Google Images) were crawling those, but they will only rank for alt text or anchor text. Filenames aren't usually what you want them to rank for, and the folder probably didn't have much PR anyway to make them attract any traffic.

Brian.

[maxsun]

I'm not worried about the images so much--the filenames are just stock #'s, but I do have a /jewelry subdirectory, which I do want indexed and the filenames are meaningful there (i.e., rhodochrosite_bracelet_2401.htm).

I did check out a competitor and they have the subdirectories Forbidden. Mine will show the headers but not list the files, so something's different.

So I' guess I'll just keep an eye on it--but I am jittery--especially with Christmas only 10 weeks away. Would hate to be penalized right now!

Thanks for the input.