Redirects

Redirects

Reasons for Redirects

  • A web site has been restructured
  • Pages on a site are moved to another location
  • A section of the site is renamed
  • A shorter URL is required for an offline media campaign

Benefits of Redirects

  • Helps to ensure existing links to your site continue to work
  • Helps to ensure bookmarks to your site continue to work
  • Helps to ensure search engine rankings are maintained

HTTP 301 Redirects

  • The server sends back an HTTP reply, with a response code and with a new URL
    • Response code 301 is used for items that have been permanently moved
    • Response code 302 is used for items that have been temporarily moved
  • Used when an item is moved and you want to make sure a 404 Item Not Found does not occur
    • The response code tells search engines that the item is not missing, it has just been moved
    • This is important for Search Engine Optimization (SEO)

Sitecore Redirects

  • Redirects are normally managed from within IIS
  • Sitecore doesn’t provide redirect functionality by default
  • Consider adding redirect functionality to Sitecore
    • Enables business users to manage redirects from within Sitecore
    • Enables business users to manage redirects even when they do not have access to IIS 

Sitecore Redirect Options

  • Clone items: avoids redirects but adds clutter to the Content Tree
  • Custom solution: usually a Sitecore Pipeline to intercept requests and redirect if they match certain rules
  • IIS URL Rewrite Tool: provides redirection before the request reaches Sitecore
  • 301 Redirect Module: Sitecore Shared Source module that uses items to specify what redirects are in place, so Business Users can add, edit and remove redirect rules without developers getting involved
  • Redirect Manager Module
  • Sitecore Redirect Manager Module

Sources