A relatively painless way (if .htaccess is too hard for your contact to implement) is to use rel canonical to point to the url you want since Google and Bing will (eventually) notice your canonical tag.

So, for http://www.cascadevillagehotel.com/index.htm you could add a tag like the one below into your index.htm file in the head section:

You should also make sure that any links to the home page refer to http://www.cascadevillagehotel.com rather than http://www.cascadevillagehotel.com/index.htm

See http://support.google.com/webmasters/bin/answer.py?hl=en&answer=139394 for more info on rel canonical

Having said that, a 301 redirect is probably the best way to solve the problem.

BTW, I'm assuming it is an Apache server and so uses .htaccess - IIS can be a bit more tricky (see http://www.seomoz.org/blog/what-every-seo-should-know-about-iis#chaining for IIS redirects)

You could use something like this in the .htaccess file (always make a backup copy of the .htaccess file before saving it in case something goes wrong - typos etc.):

BACKUP EXISTING .htaccess FIRST!!!

RewriteEngine On

RewriteBase /

may need to uncomment the next line depending on host

#Options +FollowSymlinks

add www for non www pages - you may not need these two lines

RewriteCond %{HTTP_HOST} ^cascadevillagehotel.com$ [NC]

RewriteRule ^(.*)$ http://www.cascadevillagehotel.com/$1 [L,R=301]

The following redirect is the one for index.htm assumes the default page is /

redirect 301 /index.htm http://www.cascadevillagehotel.com/

If you're sure that the files on mamp and what's on the server are the same, then perhaps your hosting company is doing something or there's something in the config of the web server.

Sorry Vanessa, that's as much as I can help with - guess you need to find someone who knows whmcs

Good luck, would be good to know how it works out and what the solution is.

Sorry, on the edge of my knowledge, perhaps try removing those lines and seeing the effect? (I'd try removing them one at a time starting with the second one).

I don't think that's it - that's a 301 redirect and the issue you reported is a 302.

If you see the same issue I do with cookies affecting the result, then I'd suggest that is a clue - as far as I know htaccess redirects don't make use of cookies.

I get this using httpfox.

302 Redirect to: / http://servicioshosting.com/

I also see the redirect on https://www.servicioshosting.com/index.php when I first switched to English language from the home page. Then when reloading https://www.servicioshosting.com/index.php there was no 302.

I also noticed that when I deleted servicioshosting.com cookies and reloaded https://www.servicioshosting.com/index.php the 302 was back.

So I suspect it is something to do with the way the CMS is using cookies, since crawlers don't set cookies they get the 302.

I guess you'll need to dig into the CMS/talk to a developer. Good luck!