On-demand Webinar: Improve the efficiency of your team through better Content Platform usability Learn More
Easily manage and test your redirects across your site without requiring a developer. URL Redirections in Agility CMS provides a way for you to redirect a user from one URL to another URL.
A URL redirection, also known as URL forwarding, is a method that allows a web page to be accessed from several URL addresses. When a web browser tries to open a redirected URL, it is redirected to a page with a different URL.
Implementing redirects on a website is essential to managing your sitemap and preventing dead links. Typically, they are used to redirect an old URL to a new URL or provide a vanity URL (alias) that can be easier for users to remember.
URL Redirections and their uses may also include:
A website might be accessed using both a secure HTTPS URI scheme and ordinary HTTP.
A URL might be mistyped by a user. These "misspelt" domains are frequently registered by businesses and redirected to the "right" site.
Incoming links to an old URL can be redirected to the proper site using URL redirects.
Most web servers maintain extensive information about where visitors came from and how they visited the hosted site in their access logs. They do not, however, keep track of which links were left by visitors. This data can be gathered in a variety of ways. URL redirection is one method.
Long descriptive characteristics that describe data hierarchies, command structures, transaction routes, and session information are frequently included in the URLs of web applications. This approach produces a URL that is unattractive and difficult to remember.
Even though the content of a page remains the same, the URL may change. As a result, URL redirection can assist users with bookmarks.
The Post/Redirect/Get (PRG) web development design pattern eliminates certain duplicate form submissions if the user clicks the refresh button after submitting the form, giving user agents a more natural interface.
Client-side redirects or non-cacheable server-side redirects are used for device targeting. Geotargeting is usually done via server-side redirects, but depending on your needs, client-side redirects may be a possibility as well.
Redirects have been used for immoral purposes, such as URL hijacking, to influence search engines.
URL redirection is frequently used in phishing attempts to trick users into thinking they're viewing a different website.
When a link is clicked, the browser includes a field called referrer in the HTTP request that specifies the link's source. This field is filled with the current web page's URL, and it will be recorded in the logs of the server that is delivering the external link. The referrer URL should not leave the organization since sensitive sites may include sensitive URLs. A referrer-hiding redirection page may be included in all external URLs.
To navigate to the URL Redirections section in Agility CMS, first click the "Settings" link on the left hand global navigation panel.
Next, click the "URL Redirections" link on the left hand settings navigation panel.
This will take you to the URL Redirections page.
Click the New button to create a new redirect.
Enter a value for Origin URL - this represents the URL that you want to redirect to another location. The Origin URL can be a relative or absolute URL.
http://www.mysite.com/mobile
This URL represents an absolute URL, and only full URLs (including that domain) will be matched, while ~/mobile
(or /mobile
) represents a relative URL and it will be matched to any URL that has that path, regardless of domain.
Enter a value for Destination URL - This represents the URL that you want to redirect the user to.
The Destination URL can be a relative or absolute URL, just like the origin. If you specify a relative path, the domain portion of the URL will remain the same.
Select the HTTP Code - This represents what type of redirect you want to perform.
Click Save to create the redirect.
Origin URL:
~/page-a
Destination URL:
~/page-b
HTTP Code: 301
This will redirect ALL users on ANY domain from ~/page-a
to ~/page-b
using a permanent redirect. This is the recommended practice of handling cases where a page's name has changed.
Origin URL:
http://www.mysite.com*
Destination URL:
http://mysite.com*
HTTP Code: 301
In this example, we are using a wildcard redirect to redirect all traffic from thewww.mysite.com
domain to the mysite.com
domain. For example, a request tohttp://www.mysite.com/contact-us
will be redirected to http://mysite.com/contact-us
.
Agility CMS makes it easy to test all of your URL redirections so you can identify when they aren't working and take action to fix them or remove them.
Learn how to test your URL Redirections
You can delete one or many URL redirections by selecting them from the grid and clicking Delete.
Agility gives the user the ability to import URL Redirections. This is very helpful when trying to update multiple URL's at the same time.
You can import URL redirections by formatting an Excel file (.xlsx) file with the following columns:
You can Export your items and then modify the excel sheet, or download this sample file to get started.
Any existing URLs that do not have changes that are re-imported will be ignored and unchanged.