Redirect Users to a New Location Automatically

Recently, while working with a client, I noticed they had purchased a 3rd party web part to redirect users from one location to another.  There are other posts that describe a simple, out of box, solution; however, I wanted to include it here for my readers and clients.

There isn’t any need to write custom code or purchase a 3rd party product to redirect users from one location to another.

To accomplish this, use the following steps:

Let’s say, for example, you are in the process of migrating your SharePoint environment to a newer version.  As you perform the migration, you may wish to have a redirect on the old site sending the user to the new (migrated) site.

1 – On the site you wish to perform the redirect, add a Content Editor Web Part.

Add Content Editor Web Part

I’ve given the web part a title of “Redirect to New HR Site”.

2 – On the ribbon bar, in the Format Text tab, click the Edit Source button.  Then enter the redirect source.

RedirectUsers02

 

The actual redirect is the <meta …/> tag line, everything else is simply telling the user what will happen.  I feel it is always a good idea to inform the user of what is about to happen and ask them to update their bookmark.

The actual redirect is formatted as follows:

<meta http-equiv=”refresh” content=”{seconds};url={target URL}“/>

Replace {seconds} with the number of seconds to delay before redirecting the user.  10 seconds is a very common delay.

Replace {target URL} with the URL of where you with to redirect the user to.

Example, delay 10 seconds and redirect to HR site:

<meta http-equiv=”refresh” content=”10;url=https://cks.sharepoint.com/sites/contoso/departments/hr/”/>

 

 

 

Bob Mixon

Senior SharePoint Solution Architect, Senior Information Architect, 5-year Microsoft SharePoint MVP (2006, 2007, 2008, 2009, 2010). Family man, father, grandfather and cook. You can read my entire profile here.

More Posts - Website

Follow Me:
TwitterLinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *