Tag Info

Hot answers tagged

8

When your website is too busy due to a large traffic, the best way of redirection is using custom error documents. So, when a user gets 503 error code, the server will redirect visitors to the custom error document page you have defined. There are different ways for different servers to customize error document pages. 1. For Apache server, add the ...


5

It seems like you're aiming for the second-worst outcome. If you're expecting a spike, you have time to do something: Implement in-code caching (can be easy, can take a while to get right) Optimise static files (jpegoptim, optipng, more-css, etc) to reduce bandwidth, speed things up for all users. Move your static stuff to a CDN to remove those requests ...


4

What webserver are you running on? Nginx To remove www in nginx do the following. if ($host = 'www.example.com' ) { rewrite ^/(.*)$ http://example.com/$1 permanent; } That will strip the www. To force https: rewrite ^ https://$server_name$request_uri? permanent; Along those lines. Apache Force https: RewriteEngine On RewriteCond %{HTTPS} ...


3

There are things you can do at a number of levels: Network Level Network Hardware: Install a load-balancer, with addition servers behind it. This will allow you to run your existing set-up fairly easily, but will probably cost quite a lot of money to setup in the time frame you have (depending on your hosting providers support levels) Virtual Hardware: ...


3

From the mod_rewrite documentation you need to use the NE (no escape) flag when your rewrite rule has a hash: RewriteRule #(.+)$ /? [L,R=301,NE] You commented that the NE flag may only apply to the target URL and not the rewrite pattern. If that is the case, another approach would be to escape the # sign. mod_rewrite supports \x style escape sequences. ...


2

I think this is a synchronisation problem of updating the Google databases. When you 301 redirect the home page to an article, you say to Googlebot the new home page is the article but Google takes more time to take into consideration a redirect than a title change. That's why I think Google updated your title without taking into consideration the redirect ...


2

Google WMT feature to 'Add a site' asks users to enter a URL, and gives example 'www.example.com' - which is not helpful when trying to add an https site To add the https version of the site, just look at the URL in WMT for http version and change it from https://www.google.com/webmasters/tools/dashboard?authuser=0&siteUrl=http://www.domain.com to ...


1

I feel like I am misunderstanding something, but if I am actually understanding the issue, it seems like two tools would completely solve the problem. (Leave the 301s in place.) Create a robots.txt and disallow all indexing and crawling on the old site. In Webmaster Tools, click Google Index/Remove URLs. Enter the domain name of the old site. It will ask ...


1

You are right about GEOIP and GEO Location. It is hard to do and requires maintenance. Even then, according to some I am in Florida, Ohio, New Hampshire, Pennsylvania, etc. One out of four ain't bad! Not something to count on. Concerning your idea about the new domain name and doing a 301 redirect. If you are thinking that the domain name is of any benefit ...


1

Using DNS is not a redirect. You simply pointed another domain name to the same server. Nothing more. There is serious danger in this in that you will/can end up with duplicate content that will harm SERP performance severely. TO avoid this, traditionally, you would want to have both domains configured on a web server (it does not have to be the same ...


1

I wouldn't recommend using HTML meta tags to manage redirects. Go into your root directory, find the .htaccess file and add this to the top. # This allows you to redirect your entire website to any other domain Redirect 301 / http://siteB.com/ You may have to edit your settings to view that file because most programs hide the .htaccess file by default. ...


1

There are two techniques that you can use: Frame redirects This is a technique where the first domain serves an HTML frameset that hides the other URL. It has some disadvantages: Users may not be able to navigate out of the frameset. Clicking links may not change the URL, even if they navigate to external websites. Users may have a hard time ...


1

Thanks to the hint of Max and this post, I found the answer to my problem: RewriteEngine On RewriteCond %{HTTP_HOST} !^$ RewriteCond %{HTTP_HOST} ^mydomain.com [NC] RewriteCond %{HTTPS}s ^on(s)| RewriteRule ^ http%1://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L]


1

You will have one problem that you will need to address so I will cover it first. You will have trouble with duplicate content using the method you suggest. On each page, you can have either HTTP point to HTTPS content or the other way around. Adding this to the header of each page, obviously modifying the example URL on a case by case basis, then you ...


1

Google has a site migration howto. A protocol change counts as url modification; this is the relevant section. The switch goes much like a regular HTTPS switch. Once your urls are made protocol-relative, and before you start redirecting, you should validate the https site in Google's webmaster tools. It's a separate site with its own sitemap. There is no ...



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