Tag Info

Hot answers tagged

2

You want to do a blanket redirect from one domain to another. Assuming Apache, put in your .htaccess file in the root directory of example0.com: RewriteEngine on RewriteRule ^(.*)$ http://www.example1.com/$1 [L,R=301] This will redirect all requests from 0 to 1 and keep the original request URI.


2

First off the easiest one for www is this. RewriteEngine On RewriteBase / RewriteCond %{HTTP_HOST} ^yourwebsite\.com$ [NC] RewriteRule ^(.*)$ http://www.yourwebsite.com/$1 [R=301,L] Now for some actual rewriting you should be able to use something like this. RewriteCond $1 !^(users) RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d ...


2

First of all, beware: canonical and hreflang at the same time sounds dangerous. You would have to use canonical only for duplication within the same language. Back to the main topic: Automatic redirection is not a good idea... You can read this from Google's documentation for international targeting: Avoid automatic redirection based on the user’s ...


1

Heroku gives directions on configuring DNS for root and they provide a list of DNS providers who can provide ALIAS/ANAME and other capabilities needed. They say, if your DNS provider will not provide this, then you have to do a redirect (just as I have done): If your DNS provider does not support ALIAS or ANAMEs, you will need to use subdomain ...


1

You seem to be doing everything right webmastering wise, but I took a look at your headers using CURL. When I tried just http://morphmarket.com, I got the following: HTTP/1.1 301 Moved Permanently Cache-Control: max-age=900 Content-Length: 0 Content-Type: text/html Location: http://www.morphmarket.com Server: Microsoft-IIS/7.5 X-AspNet-Version: 4.0.30319 ...


1

What a great question... Considering your setup I'm not what you can do here. It looks like the delay is on Godaddy's 301 redirect side so I'd be tempted to ask them why there's such a delay. Your A record points to 50.63.202.10, is that a hosting account? If so then I'd be tempted to remove the godaddy redirect and allow the non-www to go to the godaddy ...


1

What you're doing is not a good idea as it creates cloaking which violates google's webmaster guidelines. On top of that, many modern web browsers will ignore the textual HTML if they come across a Location: header with the proper redirect status code. The textual HTML in the normal redirect-based pages are there for compatibility reasons. This means if you ...


1

Using .htaccess You do this with a simple .htaccess rule by detecting the browsers Accept-Language (read here). RewriteEngine on RewriteCond %{HTTP:Accept-language} ^en-GB [NC] RewriteRule ^$ https://example.co.uk [L,R=301] Using PHP You can do this with a programming language to perform a lookup (I generally use a 3rd party open API) then send the 301 ...


1

I assume the old pages will remain indexed for a while unless there was a long time lapse between old site going down and new site going up. Do the 301's and see if you start picking up the traffic from the old indexed pages. I has a similar situation and gains most of the traffic back but this all happened in a very short amount of time. I would keep the ...



Only top voted, non community-wiki answers of a minimum length are eligible