I am going to take a leap here, and perhaps those looking on will chime in.
I think BEFORE we install Wordpress, we should determine WHERE we are going to install it.
Is there any benefit to installing Wordpress directly into the root directory the (public_html/) or should we install it in its own directory (public_html/wordpress)
Now Rawtop mentioned something, that perhaps is worth noting here, and that is how deep Google likes to crawl. Now it isn’t a definite, but I believe that they prefer to crawl no deeper than 3 levels.
So if you install WP into its own directory, you are already 1 level down.
It depends on what else your doing with the site… You should think long-term about what you may want to do in the future. The issue is that WordPress controls whatever directory it’s in. You can’t just upload a file or new directory in the WordPress directory and have it work. Instead, every exception that you want handled outside of WordPress has to be added as a RewriteRule in your .htaccess or VirtualHost file. That’s not prohibitive, just a hassle…
On rawtop.com I’ve got 4 blogs currently (3 powered by Blogger which I need to change to WordPress, and 1 WordPress blog that I’m going to dump 'cause it would be better served by a forum). I could use one WordPress install to power all of the blogs, but that gets messy. It works well when you’ve got multiple similar blogs - like I’m going to have with wilywilly.com where there are different porn blogs that share posts. But if you have one WordPress powering dissimilar types of blogs (like I do on rawtop with a personal blog, a porn blog and a stories blog) then the concept of categories is basically dedicated to separating the blogs which isn’t a good thing at all… But what you lose by having multiple installs is the ability to search across all blogs on the site to find something - which I’d really like on rawtop.com. I think I’ll need to go with something like Google’s or Yahoo’s Site Search to tackle that problem…
If the domain is purchased to run a blog, then do it in the root, but if it’s there to be part of say a tour to show a recent update to the site, then by all means a subdirectory is fine.
Also, I would NOT in any way name a subdirectory with wp or wordpress, and you should also avoid using those in naming your database as well, for security reasons.
But wouldn’t it also make sense to have multiple users for one blog? I mean if you are making several ‘blog themes’ but run under one install, wouldn’t it be easier to use the WPMU version? Then a ‘search anything’ plugin would allow for site wide searching, or the google plugin for searching?
[quote=Bec;15299]If the domain is purchased to run a blog, then do it in the root, but if it’s there to be part of say a tour to show a recent update to the site, then by all means a subdirectory is fine.
Also, I would NOT in any way name a subdirectory with wp or wordpress, and you should also avoid using those in naming your database as well, for security reasons.[/quote]
Absolutely in regards to naming your db and directory, but with the CMS capabilities of WP, why not give it a whack for the whole site? Granted the CMS functions are a bit wonky, but possible, but it does depend on the type of site you want on the domain.
I am just thinking that blogs can be more than just a few lines of text with pictures, but some great permanent pages that make sales, that using the ‘page’ option can allow for some good ‘free site type’ galleries. And more.whistle
Which brings up the question as to how many ‘posts’ one should have on that first page… the default is 10 I think but I prefer to cut it down to around 5, as I am long winded.
Ok. Maybe I am do it wrong, but Google doesn’t seem to have an issue. In most cases, I intstall WP in a folder. I then change my permalinks so that all posts are in the FOLDER root.
So it goes like this, assuming I installed WP in the folder uncut-cocks.
In my case for Wily Willy I like the fact that different blogs can share posts, so a single install works for me. But yes, if you wanted completely separate blogs WPMU might be the way to go.
[QUOTE=rawTOP;15302]The stylesheets are at /wp-content/themes/some-theme-name/style.css - it’s obvious which blogs are powered by WordPress.
To me the directory shouldn’t be named wp or wordpress simply because there’s no SEO value in that (unless you’re doing a blog about WordPress)…[/QUOTE]
If you are doing a blog about WP, then you should use WP in the folder.
Even if, I’d say NO to using WP in the directory or DB, as many of the hackers attaching WP blogs, are looking for just that designation to try and break in… it gives them a beginning, and I just don’t wanna make their job easy. 666
[QUOTE=abostonboy;15305]Ok. Maybe I am do it wrong, but Google doesn’t seem to have an issue. In most cases, I intstall WP in a folder. I then change my permalinks so that all posts are in the FOLDER root.
So it goes like this, assuming I installed WP in the folder uncut-cocks.
IF I have two titles the same, WP adds a 2 at the end. However, I rarely fuck up that bad too many times. It has done well for me in the past.[/QUOTE]
Right, but you could have them in the domain root if you didn’t put WP in a folder.
I debated about putting all the posts in the root of Wily Willy, but opted for them being one level down in a /YYYY-MM/ type directory structure. It was a hard decision though 'cause dates are really pretty irrelevant to porn… And I could still change my mind if I see someone has a better idea.
Rawtop > In regards to the MU, what I was trying to say, was couldn’t you use it to share posts within, by adding several users (them being you) ? I am not familiar with it, but from what little I read, I thought different users could share posts within the MU framework?
Also, have you looked at the one install plugin that supposedly allows you to share plugins/themes for WP? Not sure but I THINK I saw where it allowed for sharing of content beyond just plugins/themes.
I don’t know that much about WPMU either… What I need done I can accomplish with the regular version so I’m happy with that. A guy who works for me looked at it at one point and found that it wouldn’t do what I needed it to do (mainstream stuff). All I know of it is the little he told me back then.
[QUOTE=rawTOP;15309]Right, but you could have them in the domain root if you didn’t put WP in a folder.
I debated about putting all the posts in the root of Wily Willy, but opted for them being one level down in a /YYYY-MM/ type directory structure. It was a hard decision though 'cause dates are really pretty irrelevant to porn… And I could still change my mind if I see someone has a better idea.[/QUOTE]
That is true. I do have some blogs with all in root level. I am just afraid that at some point Google will consider it spams. 1000’s of urls in root. It scares me a bit.
You’re making me like my date-driven directory structure!
I have mainstream corporate sites that have tens of thousands of documents in the same directory (though not in the root). It’s not always a bad thing…
You can also install WP in the root and have all your posts in a single directory that’s not the root…
The reason why I don’t like so many documents in the root is because it can become unmanageable if you want to change things around on the site. On the other hand if all the post files are in one directory, then things are much easier to handle.