Transforming UB’s digital communications.
Redirects and Vanity URLs
Provide alternate paths to your page.
On this page:
Last reviewed: February 7, 2025
Overview
Visitors can be automatically switched from one URL to another, using server redirects, UBCMS 'vanity URLs' or redirect pages, or third-party URL shorteners. These solve problems from previously published links or help to promote a alternate path to your pages.
UBCMS Vanity URLS
Unlike server redirects, a Vanity URL is set up in the UBCMS and can be created and managed by your own Web team.
A Vanity URL will redirect visitors to a page on your site; e.g. from www.buffalo.edu/abc to www.buffalo.edu/yoursite/somepath/targetpage.
The URL people start at can be fictional and does not need to correspond to a real, published page, but the final target page does need to be an actual page in the UBCMS.
You can create a Vanity URL to direct visitors to any site you manage, but the URL you provide to your visitors must be one of the domains that the UBCMS controls, such as www.buffalo.edu or one of the subdomains already established within the UBCMS (e.g. nursing.buffalo.edu).
If your URL is already being adjusted by a server redirect, speak to the DCT Help Team for advice. For example, cas.buffalo.edu and sphhp.buffalo.edu are already handled specially, which will complicate how the Vanity URL is built. Please also see the additional restrictions and exceptions that are noted below.
Before you start...
- Open your proposed Vanity URL in a browser first to be sure it does not hijack someone else's page.
- Only use wording that falls within your own area of authority; e.g. Dining Services should not use "UB Bulls" without authorization.
- Open the page you want visitors to land on.
- Open the Properties and the Advanced tab and scroll down to Vanity URL.
- Click the plus sign (+) and enter the reference path of the page your visitors will start at -- this is the reference path to the page as if it existed in the UBCMS and NOT an actual URL; e.g., /content/www/site/page
NOT https://www.buffalo.edu/site/page
NOT www.buffalo.edu/site/page
NOT buffalo.edu/site/page - To enter more than one Vanity URL – each must be on its own line.
- Select Redirect Vanity URL so the browser shows the actual location in its location bar (not the link that was clicked or entered to reach your page). While this is currently optional, we suggest you always select it.
- Click OK then Publish the page to enable it on your published site.
- Be sure to test the redirect to be sure it works as expected. The Author environment should redirect immediately but the public version may take a minute or two to establish. You may also need to clear your browser cache or at least do a full page reload (Control + F5).
| Actual Desired URL | Equivalent UBCMS Path |
|---|---|
| www.buffalo.edu/abc | /content/www/abc |
| www.buffalo.edu/brand/abc | /content/www/brand/abc |
| nursing.buffalo.edu/abc | /content/nursing/abc |
Vanity URLs can handle many URLs including a variety of filename extensions, if needed, such as:
- https://www.buffalo.edu/home/academics
- https://www.buffalo.edu/home/academics/
- https://www.buffalo.edu/home/academics.html
- https://www.buffalo.edu/home/academics.php
- https://www.buffalo.edu/home/academics.php3
- https://www.buffalo.edu/home/academics.asp
- https://www.buffalo.edu/home/academics.aspx
- https://www.buffalo.edu/home/academics.shtml
- https://www.buffalo.edu/home/academics.htm
- https://www.buffalo.edu/home/academics.jsp
- https://www.buffalo.edu/home/academics.cgi
- https://www.buffalo.edu/home/academics.cfm
Do not include the file extension in the path of the Vanity URL. For the above examples, all would simply be "/content/www/home/academics" (no slash, no ".", no extension).
The option to Redirect Vanity URL causes the browser to update the location bar so that it shows your preferred URL path instead of the URL that the visitor entered or clicked to arrive on your site.
Changing the URL in the location bar may be confusing to visitors, since they may not notice that the URL has changed, or appreciate why it has changed. However, this setting will encourage visitors to remember (and bookmark) your preferred URL.
While this is currently optional, we suggest you always select it. (Not selecting it may cause your page to load without some of its images or styling.)
While the Redirect Vanity URL setting is currently optional, we suggest you always select it. Not selecting it may cause your page to load without some of its images or styling.
- Do not use a Vanity URL on a Shared Content page.
- Do not use the same URL as your actual page. Doing so can produce a loop that locks you and your visitors out of the page!
- If higher level redirects or URL mapping already exist for your site, the Vanity URL may not act as expected. If you believe this is happening, contact the UBCMS Help Desk.
- For technical reasons, we request you always select Redirect Vanity URL.
- Each Vanity URL will only redirect one page and will not affect links to pages beneath that location. For example, it is not possible to redirect all requests under "/content/www/about_ub/*" (.../about_ub/at-a-glance, .../about-ub/visit-ub, etc.) to a single new page. If you would like to request this functionality, contact the UBCMS Help Desk.
- All URLs in UBCMS including Vanity URLs are case sensitive, so "/content/www/UBCares" will not match "/content/www/UBcares" (lower case 'c'). Add additional Vanity URLs for common variations.
- A Vanity URL will only work for pages with certain file extensions. It will definitely work for no extension as well as .html. In most sites, depending on specific site configurations, it will also work for URLs ending in: /, .asp, .apsx, .php, .php3, .shtml, .htm, .jsp, .cgi, .cfm. For example, a Vanity URL of "/content/www/about/test"
- will match a request for /content/www/about/test.html
- will match /content/www/about/test
- will match /content/www/about/test/ (in most sites)
- will match /content/www/about/test.php (in most sites)
- will match /content/www/about/test.asp (in most sites)
- but will NOT match /content/www/about/test.pdf - Vanity URLs may interact with other rules only in effect on your published site (such as to transform URLs from /content/www/about to www.buffalo.edu/about), so it is recommended that you test Vanity URLs after activating them, and pay special attention to testing Vanity URLs when your site is first launched.
- Vanity URLs cannot be applied to files in digital Assets. To get around this limitation, create a regular website page using the Redirect Template.
- A Vanity URL cannot normally handle these cases:
- regex regular expressions for a pattern of URLs (e.g. multiple related paths routing to one page)
- redirects from or to a non-UBCMS site
- redirects from a UB subdomain that does not exist in the UBCMS
- URLs that require additional parameters (e.g. '?variable=value')
- It is not possible to add a working Vanity URL to an authenticated page ('-pw') unless your Vanity URL also ends in '-pw.' If a short URL without '-pw' is desired for outreach or to handle common usage, we suggest you create a Redirect Page with that URL instead.
- Create a new page using the Redirect Template.
- Set the URL through the UBCMS to the actual secure page (/content/www/etc/page-pw).
- Then add any desired Vanity URLs to the Page Properties of the redirect page, and NOT in the secure page itself.
UBCMS Redirect Pages
The UBCMS supports a special type of page that simply serves as a built-in redirect from its apparent location to the actual page on your site. These can be built in Shared Content or as a regular Web page, using the appropriate template.
- Click Create and Page and choose the Redirect template.
- Open the page and then open the single editable spot on the page: Redirect to.
(NB. because no components can be added to this page, your Sidekick will look empty.) - In the settings dialog box, choose between:
- Redirect to file - Provide an asset from the DAM or uploaded from your desktop.
- Redirect to page - Enter an external URL, with the 'https://' prefix, or use the magnifying glass chooser to select an internal UBCMS page.
- Redirect to file - Provide an asset from the DAM or uploaded from your desktop.
- Click OK and activate this page.
Create Page process with available templates
A redirect page, opened for editing.
Redirect page settings.
For standard UBCMS pages, while you can set a redirect in page Properties, we do not recommend this solution, because nothing in Author shows that the page is being used as a redirect.
Known Issue
Redirect pages cannot have working children. You can create a child page, but will not be able to edit its contents, because the UBCMS knows that its parent will effectively block access to that child page. Read more about this known issue.
Server Redirects
Server redirects are created and managed by UBit.
These higher order paths guide how people access any UB website, not just those in the UBCMS, provided UB manages that domain or server. Set for a temporary (one-year) or persistent (three year renewable) period, they must be supported by a good business case.
A server redirect is the only method to handle:
- regex regular expressions for a pattern of URLs (e.g. multiple related paths routing to one page)
- redirects from or to a non-UBCMS site
- redirects from a UB subdomain that does not exist in the UBCMS
- URLs that require additional parameters (e.g. '?variable=value')
If you would like to request a server redirect, please assemble your business case and contact the DCT Help Team.
After you retire this tactic, or as an alternative, consider implementing a custom 404 error page. This will load when the ‘wrong’ URL is requested, with your unit’s branding and additional clarification how to find the content that is sought. > Read more about custom error pages
Temporary Redirect
- Purpose: To support a short-term business need such as a website migration, or marketing campaign (hard copy or sent email).
- Duration: One year. Normally non-renewable.
- Requires a business case.
- Examples:
- geology.buffalo.edu -> arts-sciences.buffalo.edu/geology.html
- facilities.buffalo.edu -> buffalo.edu/administrative-services/managing-facilities.html
Persistent Redirect
- Purpose: To support user expectations, industry standards, or institutional needs (including brand, legal requirement or contract).
- Duration: Three year, renewable on request.
- Requires a strong business case.
- Examples:
- education.buffalo.edu -> ed.buffalo.edu
- news.buffalo.edu -> buffalo.edu/news
- cas.buffalo.edu -> arts-sciences.buffalo.edu
URL Shorteners
A final option is to use a 'URL shortener' service, like Bit.ly or TinyURL.com. These free services allow you to choose a specific URL, if it's not already taken, such as http://bit.ly/UBCareerFair, as an equivalent to one of your Web pages. And if you register, you can track the clicks on the link, which is very handy for assessing the effectiveness of links sent out in emails.