Set Up CMS Redirects

Product: CMS

Version: CMS 10, 10.x, CMS 8, 8.x, CMS 9, 9.x

Published: September 8, 2012

Last updated: 1/30/2021

Comments:
0 Comments

Description

This article will detail how to configure, deploy, and test custom 301 redirects on your Ingeniux CMS in version 7.0 and above.

Purpose

Redirects allow you to create user-friendly URLs for pages served by the CMS, allowing users to view pages by entering these easier-to-remember URLs directly into the browser's address bar.  They also allow links that were used in prior iterations of your site(s) to continue to function while rendering prior materials that used old URLs useful and relevant.

Requirements

Ingeniux CMS 7.0 or above.

Step-by-Step

Ingeniux recommends configuring redirects through the Redirects app in the Apps pane.
  1. Log into the CMS client.
  2. Click the Apps ribbon in the bottom left of your browser.  
  3. Under the Apps pane, click Redirects.  
  4. click Add on the left-hand side of the screen, and the From and To text areas will "unlock," allowing input.
  5. In the From field, enter the URL from which you want users to be redirected.  
    • Example: If you would like users to be redirected from www.yourdomain.com/business, enter "business/".  
    • NOTE: end all From entries that are words with a trailing '/' as it will improve accuracy.
  6. In the To field, enter the xID or structured URL you wish users to be redirected to.  
    • Example: 'x123.xml' or 'business-systems.htm'.
  7. Initiate a publish of any type so that the redirects.xml propagates to all Content Management Servers.


Testing redirects:

  1. Verify that a publish has been completed since updating, adding, or removing redirects.
  2. Browse directly to a redirect that you wish to test in your browser of choice.  Using 1.5 and 1.6 as an example, browse to www.yoursite.com/business and it should redirect your browser to www.yoursite.com/x123.xml.

Additional Information

  1. The From field is relative to your domain.
  2. From entries do not need a leading '/'.
  3. xIDs in the From entry require the .xml extension.
  4. From entries that are words (e.g., "student") should have a trailing '/' to make them clearly defined. Otherwise, the redirect will match to any string beginning with the specified word. In other words, "student" in the From field would match requests for www.domain.edu/student as well as www.domain.edu/studentlife and www.domain.edu/studentresources. However "student/" in the From field would only match www.domain.edu/student.
  5. The To field can contain absolute or relative links.
  6. Absolute URLs in the To field can be any domain. For instance, you could redirect from "x12345.xml" to www.google.com.
  7. Relative URLS in the To field are relative to your domain and must exist.
  8. Query results can not be used to redirect to another site.

Comments

There are no comments yet.