Add this code to the top of

loanspanel — Wed, 20 Jul 2011 16:22:09 +0000

Add this code to the top of the page, separately from the server {} section for the preferred canonical name.

Thanks. Hadn't thought about

aharown07 — Tue, 05 Apr 2011 15:48:15 +0000

Thanks. Hadn't thought about SEO impact. I've got all set up with redirects now though anyway. Sounds like it's the way to go for multiple reasons.

If the content is the same on

bernard11 — Tue, 05 Apr 2011 09:49:14 +0000

If the content is the same on all three sites, two of the sites (maybe even all three) will be punished by the search engines for duplicate content. Therefore, it is probably best to have different content on each site or to make 301 redirects from each domain to the main site.

_____________
Bernard
Improve English Grammar

This may help you WWW

mike222 — Mon, 07 Mar 2011 20:23:28 +0000

This may help you

WWW Redirect with nginx

WWW redirect requires rewrite module, but it is included as standard HTTP modules during compilation of nginx. All Linux distribution packages that I’ve tested with include this feature.

Add this code to the top of the page, separately from the server {} section for the preferred canonical name.

For instance, if you like to redirect to non-www, add the following code:

server {
listen 80;
server_name www.example.com;
rewrite ^/(.*) http://example.com/$1 permanent;
}

The word permanent is key. It turns the redirect into 301 redirection. After this block, you may configure the domain without www.

Here is the code for redirecting non-www to www:

server {
listen 80;
server_name example.com;
rewrite ^/(.*) http://www.example.com/$1 permanent;
}

Thanks. If redirect is the

aharown07 — Mon, 28 Feb 2011 12:14:29 +0000

Thanks.
If redirect is the standard way/best way, I know how to do that.
I'm using nginx as web server, so no .htaccess, but it's pretty straightforward.

The simplest thing to do

TrafficNova — Sun, 27 Feb 2011 15:26:18 +0000

The simplest thing to do would be to put a redirect in the .htaccess file in the root of your .com website to do a 301 redirect to your .org website, assuming you are using apache. Alternativley you should be able to configure the webserver to do the redirect for you.

Google .htaccess redirects and you should be able to find loads of examples.

Not using any. All command

aharown07 — Wed, 16 Feb 2011 14:16:41 +0000

Not using any. All command line.... which I'm pretty new to but the theory is to get more resource per dollar by not paying for management & not paying for resource hungry control panels.
So far, it's going pretty well. I've got two sites working on the server (very simple ones) and plan to move "the big one" this weekend.
Could not have done it without vpsBible dot com (I'd link but I can't remember if that's permitted here or not)

So I'm hosted at Linode and the server is Ubuntu Linux 10.04 LTS. Using nginx as the web server. Last night I found instructions for doing a redirect in nginx. It's about a three step process. Not too bad. That's probably what I'll do. Just wasn't sure if there was a better idea like maybe having the .com display a page that says "Hey, you've got the wrong url, how about going to ....org" Could do that I guess, but is there any advantage?

(I should probably mention that Linode has a control panel, but it is pretty much for managing the basics like DNS and rebooting the virtual server (though you can do that from the command line, too). But it has some powerful features like installing your OS from an image, managing copies of disk images, etc. So that's nice. But it doesn't manage your web server at all.)

What kind of server

pr0gr4mm3r — Wed, 16 Feb 2011 11:52:38 +0000

What kind of server management software (cPanel, Plesk, if any) are you using on your new VPS?