When moving a site to a new domain, it’s important to redirect visitors to the new domain. This provides a courtesy to your users, helps retain search engine ranking, and prevents broken links to your site.
Apache provides several methods for redirecting requests and this article documents several approaches.
The rules should be tested properly before applying them. In our case, we set up a virtual machine with cloned versions of both new and old sites (with an appropriately modified hosts file) to allow full testing of all redirects.
This article refers to a site that is being moved to a new domain as part of a re-branding exercise.
The site structure will remain broadly the same, but for two quite important differences. The old site permalink structure for the ‘projects’ and ‘people’ index pages is:
On the new site, these index pages will be located at the following URLs:
In addition, project categories (a custom taxonomy) are to be rationalised as part of the move/rebuild. The old URL structure involved having ‘projects’ as a category, with projects further grouped into sub-categories. For the new site, these sub-categories have been mapped into a more logical ‘project-category’ structure.
The resource found on the old domain at
http://olddomain/category/projects/term/ should be available at
http://newdomain/project-category/term/ on the new domain.
The redirects can be achieved with a combination of Redirect and Rewrite rules, or Rewrite rules only. Rules can be added on a Directory basis (either
.htaccess or in a
<Directory> block in the vHost config).
A better approach would probably be to include all necessary rewrite rules outside a
<Directory> block within the vHost configuration. This allows the redirect to happen without even the presence of a directory corresponding to the old domain - so when the move is complete, the old site can be collapsed completely.
These rules are added to a
.htaccess file in the root directory of the old site.
Alternatively, the rewrite engine only could be used:
Note that the first string to be matched should not have a leading slash. This is because in the directory context (within either a
<Directory> block or a per-directory
.htaccess file) the removed prefix always ends with a slash - so a Pattern with
^/ never matches in the per-directory context.
Bracketed sections of the source string are available as indexed variables in the destination string:
NOTE for testing purposes, you should designate these rules as “302” - a temporary redirect. These should be amended to “301” to denote a permanent redirect when you deploy the rules to the production server.
These rules could be placed in either a
.htaccess file in the olddomain.com document root or a
<Directory> block in the site virtual host configuration file for the old site (e.g.
/etc/apache2/sites-available/olddomain.com.conf). If adding the rules to an Apache config file, you’ll need to restart Apache for the rules to take effect.
Simple vHost Redirect
This block added to the virtual host configuration of the old site provides a one-to-one mapping of the old domain to the new. If the site retains the exact same permalinks (apart from the domain of course), this might be an adequate solution. Note that a
<Directory> block is not necessary:
This kind of simple redirect isn’t going to work in our case, because the structure of some of our URLs will be altered.
Complete vHost Redirect
Here’s the final virtual host config file solution:
Don’t forget to restart Apache for the rewrite rules to take effect.
comments powered by Disqus