Page Redirects
Permanent redirects are very important to maintaining the integrity of your website with search engines. This involves the server returning a 301 status to the request, followed by passing the request to the new page. Temporary redirects aren't best practice. This is handled quickly and easily at the page level with the SEO Content Management System. Placing a permanent redirect for a page is a single step, however in the demonstration, each event is accounted for, so there are three states that are shown.
|
Adding a permanent redirect at the page level is easy. You login to your search engine friendly CMS and navigate to the page you want to place a redirect to. On the admin toolbar you will see an "aliases" tab. This will take you to the page redirect form where you can place the location of the old page in the field and submit it. That's it. |
 Click for Larger Image |
 Click for Larger Image |
Shown here, the redirection form, you can see that all you do is put the old location in the form field. This example was taken from this website's construction, just like all of the others. Initially the demonstration folder was named "functions". Here the old location is provided as an example, it being "/cms/functions". Now, when you request that page, you will find a permanent redirect to the demonstration index page. |
|
When you are done adding a redirect for your page, you will see a list of all aliases with a checkbox adjacent the redirect location. You can remove any alias simply by checking one to many boxes and submitting the bottom form. Managing page redirects is quite simple using the SEO Content Management System. |
 Click for Larger Image |
Redirects Using Rules
In some cases, typically large website migrations requires a lot more redirecting, something that trying to manage at the page level would be rediculous, so we write rules at the Apache, or web server, level. This allows redirections to be based off of directory, URL parameter or wildcard. For example an archive of news items that were in a /news/ directory. We could simply write an Apache level redirect from /news/ to the new website feature, which could be a search box to query archived news articles... or a company knowledge base, etc. Redirecting has to be done and it must use 301 server redirects. Something that is handled quickly and easily with our CMS.