Please advice me on subdirectories for a huge website

Hey everyone!

My company bussiness is to sell software (reseller), and we have alot of product pages (very detailed ones, basicly localised versions of the official pages of the softwares inside our own site.)
By the time I am writing this we already got 90 pages and like 15 more are coming by the end of the August . Sometimes when I open our site on a new PC it takes more that 3 sec to load up which I consider slow.

I must say I am building the website by myself and I am not a web designer or anything. Got basic skills or maybe little above the basic level.

So back to the questions:

  1. Is it a good idea to separete the website with subdirectiories so that each software have a dedicated wordpress install.

  2. At the moment we got like 350mb database. If I separate the the website to may small one I am going to reduce the db size right? Is this way going to speed up the loading time.

  3. Will there any be any problems regarding SEO.

  4. How can I access the admin panels of those site. For example if my domain is “mydomain.com” and I acces admin by typing mydomain.com/admin. Will I acces them by typing: mydomain.com/software1/admin; mydomain.com/software2/admin and etc.

Please advice me :slight_smile:

Hi!

I’ll respond to your questions with my personal opinion:

  1. I personally wouldn’t separate the website into multiple WordPress installs. It just adds too much time in terms of maintenance/updates.It they were different companies or domain names, then maybe, but in this case I think this would be overkill.
  2. Each individual DB will be smaller than the current one, yes, but speed may not increase. If the DBs are all on the same server, I wouldn’t expect much speed increase.
  3. Separating the current website into multiple should not really affect SEO if done correctly. BUT I think it’ll be better/easier to get SEO right if it is all in one install, since you can more easily link content to each other.
  4. If you separate them, you’d have one Admin Panel for each site, which would site as you say under “/software1/wp-admin”, “/software2/wp-admin”, “/software3/wp-admin” and so on. I don’t think this is a very efficient way.

I personally would recommend the following:

A) One single website, with a good structure for the products. I.E. have one top page for each software, and subpages to each of those for specifics:

software
│           │   │   │       │   ├───Software1
│           │   │   │       │   │   └───Sepcifics1
│           │   │   │       │   │   └───Specifics2
│           │   │   │       │   ├───Software2
│           │   │   │       │   │   └───Sepcifics1
│           │   │   │       │   │   └───Specifics2
│           │   │   │       │   ├───Software3
│           │   │   │       │   │   └───Sepcifics1
│           │   │   │       │   │   └───Specifics2

This would give you URLs such as:

www.domain.com/software/software1/
www.domain.com/software/software1/specifics1
www.domain.com/software/software1/specifics2
www.domain.com/software/software2/
www.domain.com/software/software2/specifics1
www.domain.com/software/software2/specifics2

The top page “software” is optional. I would only use it if the company offered more than just software.

B) One single installation of Wordpress Multisite. This would allow you to have ONE single Admin panel and create sub-sites for each software. This has some benefits such as:

  • Each subsite caneither have it’s own domain (www.software1.com), subdomain (software1.domain.com) or folder (www.domain.com/software1).
  • Each sub-site can have it’s own design/layout (colours, fonts, images, etc) and plugins.
  • Access can be give to specific members based on software.

On the other side, some disadvantages:

  • Al sub-sites do reside on the same DB as them main wordpress installation, using it’s own prefix for some tables, but sharing others. This makes separating them if ever needed (exporting one of the sub-sites) a bit tricky.
  • Although you can enable settings/plugins/themes globally, there’s always some customization to be done on each sub-site individually.

So there you have my opinion. There are more ways to solve your issue, but I think these two are the best options. Both have good things, and bad things.

:slight_smile:

I hope to have helped you.

I agree…and keep it flat

Thanks for the replays guys!

I got another question that is bothering me. I have a blog that is on a subdomain. Both the website and the site are new. Should I migrate the blog into e subdirectory so that I can build SEO on the domain of the site, wich is my brand name and etc?

Thanks

If the blog is part of the main website, and about the same content, I’d suggest to keep it all on one domain, not a subdomain. Therefore I’d recommend something like www.domain.com/blog/article for example.

Hey! Thanks for the answer.

We moved it to a subdirectory. As you suggested.

Got another interesting question. In Google Webmaster Tools (Search Console) we have added:

I added the new Url as new property - https://mydomain.com/blog

And I was trying to use the tool “Change of Adress”, but it wont show me the /blog property only https://mydomain.com is there as option. And if I choose that It is saying that it’s a different from where the redirect is going (301 to https://mydomain.com/blog).

There is one yellow notice that says "Don’t use this tool unless you are moving your primary website presence to a new address."

So am I getting this right? You should use this only to change the adress if its different from the main domain of the site.
Example: https://mydomain.com --> https://mydomain2.com

So how do I tell google my blog is on different address? Will Google know that from the new sitemap, which will contain the /blog links and the 301 Redirect for all the content from https://blog.mydomain.com to https://mydomain.com/blog and basicaly I wont need this tool ?

Please advice :slight_smile:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.