Redirect request
Do not request redirects for content not under your department's purview.
If a website URL is changed or removed, only the original content owner can request a redirect related to that URL.
- Determine which redirect option meets your needs
- Download and submit the (excel file) redirect request spreadsheet
- Before redirects are put in place, old URLs must be deleted and new URLs must be activated
- Submit your request three to five business days in advance
- Review redirect submission guidelines
- Redirects are removed after six months, unless a shorter duration is requested.
- PDF and other DAM assets cannot be redirected.
- If you are using Google Analytics campaign tracking, please consult with University Relations before submitting redirect requests.
- Maximum number of redirects per site is 10
- If a large number of redirects (>40) are submitted, this work effort may become a chargeable item if significant troubleshooting is required
- You are responsible for testing all redirects after implementation
- A 'file to file' redirect must supersede a 'replace multiple' redirect that includes its parent folder
- Example: The redirect /ccs/connecting/secure/RU-VPN must be listed before the redirect of /ccs/connecting
For more, see Redirect Order tab
- Example: The redirect /ccs/connecting/secure/RU-VPN must be listed before the redirect of /ccs/connecting
In your redirect list, if a parent page is listed before its children, it will overwrite the children. If you provide redirects in the wrong sequence, conflicts are inevitable. Children must be listed BEFORE the parent in your list of redirects.
Sequence matters
Provide the redirect list in a specific order with children before parents
Example, where (a) and (b) are children of parent (c):
(a) torontomu.ca/campusfacilities/departments/help-desk/* -> torontomu.ca/facilities-management-development/contact/
(b) torontomu.ca/campusfacilities/random-filename -> torontomu.ca/facilities-management-development/random-filename
(c) torontomu.ca/campusfacilities/* -> torontomu.ca/facilities-management-development/service-requests
Do not include index.html or .html in source or target URL
In our current system configuration, all of the following are the same file:
campusfacilities = campusfacilities.html = campusfacilities/index.html
The request should look like this:
torontomu.ca/campusfacilities/* -> torontomu.ca/new-site-name
We cannot redirect the same file to different targets. That is, you cannot include the following in addition to the example above:
torontomu.ca/campusfacilities/index.html -> torontomu.ca/new-site-name/file-1.html
torontomu.ca/campusfacilities.html -> torontomu.ca/new-site-name/child/file-eight.html
Avoid submitting redirects that create an endless loop
The following redirect will create an infinite loop as the destination will match the condition "learn" and continue to redirect in an infinite loop.
torontomu.ca/learn -> torontomu.ca/learning
To break the loop a "/" must be added to the end of the redirect: torontomu.ca/learn/