PDA

View Full Version : Deep Folder Structure (slightly OT)


beno
01-26-2007, 01:49 PM
Hi;
I'm new to this. A long time ago I tried optimizing a site and noticed that Google seemed to dislike deep folders, or links like this:
mysite.com/folderA/folderB/folderC/folderD/folderE/folderF/apage.htm
Now, from an organizational point of view, that can be really, really useful. Do the SEs have a problem with links like the above?
Thanks,
beno

lizcamps
01-26-2007, 03:28 PM
Hi beno,

As far as I've heard, 2-4 directory folders deep is about the limit and then you're going to experience diminishing returns with each additional folder down to the target page.

My personal opinion is that such a deep subdirectory structure is contraindicated, limited not only by the search engines' capabilities, but more because the URL becomes so darn long that people cannot easily:

- Link to that drilldown page
- Copy and paste that URL into their browser (if it breaks onto 2 lines)
- Remember that URL -- maybe they can remember that domain but I know non-heavy users who will blanch at seeing a long URL and make no attempt to remember even the domain part of it

All in all, the simpler the better, for search engines, for consumers, etc.

beno
01-26-2007, 04:45 PM
Right, that was my experience from a few years back. So it hasnīt changed. Well, as far as short urls, Iīve seen some like this, quite commonly, from big sites:
mysite.com/gsu8o8925gu83t34u03tupti9tp.htm
Short, concise, memorable...okay, not memorable. But does the SE look for that? Reason I ask is because my next option is to write a python script and create a LDAP database and simply convert all my links over. That way...

1) I can retain my exact dir structure, which is essential to keep me from losing my mind (over a thousand pages, all logically organized ;)
2) I can simply associate the above kind of link (randomly generated) to the correct link in my dir structure serve the appropriate page.

No redirects, all transparent, a bit of a pain to build, better in LDAP than MySQL for speed and since the data will never need updating once entered. Did I miss something, or does this look good to you?
Thanks,
beno