I run an information repository website, catering specifically to CPUs, and before the website gets too large, I would like to know if the current setup is going to give me trouble in the future.
Say I have a directory for Skylake-based Intel Core i7 and legacy Pentium processors. At the moment, this is how the directory structure looks:
/core-i7/ /i7-6000/ /i7-6700/ index.php /i7-6700k/ index.php /i7-6700t/ index.php index.php index.php /pentium-legacy/ /75-mhz/ index.php /100-mhz-15-w/ index.php /100-mhz-17-w/ index.php /133-mhz/ index.php index.php
As you can see, the actual directories for each model are one-file directories. And this applies to all processors in the database. As the database expands, this will of course grow considerably (I estimate around 5,000 models), so before any of that takes place, I'd like to know if the following method would be better for any reasons at all, be it server-related, SEO-related, whatever you think will impact the website in any way.
Okay, here is the structure I'm thinking about using:
/core-i7/ /i7-6000/ i7-6700.php i7-6700k.php i7-6700t.php index.php index.php /pentium-legacy/ 75.php 100-15w.php 100-17w.php 133.php index.php
Of course, I can already see at least one benefit from this method, and that is with so many
index.php files open in Notepad++, it's difficult to know which one belongs to what model until you get to it and check the path, but is there any benefit for the website?
The website's content is mostly a year old, so that's why I bring SEO into this. It would likely take a while for Google to fix the search result URLs. I'm willing to accept this if there are any other greater benefits.
I'm assuming that the file system is ext3, although I'm not 100% sure.
Here is the website in question, should you wish to see the real example.