Understanding and Managing Redirects for Bookmarked Web Pages

In the ever-evolving digital landscape, website migrations and updates are commonplace. However, these changes can inadvertently break existing bookmarks, leading to frustration for users. Fortunately, several strategies can be employed to redirect users from old, bookmarked URLs to their modern locations, ensuring a seamless online experience. This article explores the common causes of broken bookmarks, the methods for creating redirects and best practices for minimizing disruption.

Why Bookmarks Break: Website Changes and URL Structures

Websites frequently undergo changes, including redesigns, content management system (CMS) migrations, and domain shifts. These updates often necessitate alterations to the underlying URL structure. When a page moves to a new address, any previously saved bookmarks pointing to the old URL will no longer function correctly. This is particularly problematic for users who rely on bookmarks for quick access to frequently visited content.

Redirect Methods: Guiding Users to the Right Place

Several techniques can be used to redirect users from old URLs to new ones:

Client-Side Redirects with JavaScript

For simple redirects, JavaScript can be implemented directly within the old webpage. This method is particularly useful when dealing with HTML bookmarks that include anchor tags (e.g., http://server/old-system/#itemID). JavaScript can extract the anchor tag and redirect the user to the appropriate new URL. For example:

window.location.href.replace('#','?link=');

Alternatively, the specific value can be extracted and used to construct a new URL:

window.location = "http://server?itemID="+window.location.hash.replace('#','');

This approach requires the old system to remain accessible long enough to execute the JavaScript and perform the redirect.

Server-Side Redirects

Server-side redirects are generally more reliable and efficient than client-side methods. They are handled by the web server itself, ensuring that users are automatically redirected without relying on JavaScript. Common server-side redirect methods include 301 (permanent) and 302 (temporary) redirects. ASP.NET MVC2, for example, can utilize RedirectResult to implement these redirects.

CMS-Specific Redirect Tools

Many content management systems (CMS) offer built-in tools for managing redirects. For instance, ServiceNow provides features for redirecting pages between different Service Portals. These tools often allow administrators to map old URLs to new ones, ensuring that users are automatically redirected when they access the old addresses. These are particularly useful when switching between Service Portals or updating page structures within a CMS.

Redirect Files (.htaccess)

On Apache web servers, redirect rules can be defined in a .htaccess file. This allows for flexible and granular control over redirects, enabling administrators to redirect specific URLs or patterns of URLs.

Best Practices for Implementing Redirects

• Choose the Right Redirect Type: Use 301 redirects for permanent moves and 302 redirects for temporary changes.
• Maintain a Redirect Map: Keep a comprehensive record of all redirects implemented to facilitate future maintenance and troubleshooting.
• Test Thoroughly: After implementing redirects, thoroughly test them to ensure they function as expected across different browsers and devices.
• Inform Users: Clearly communicate website changes to users and encourage them to update their bookmarks.
• Monitor for Broken Links: Regularly scan the website for broken links and implement redirects as needed.

Redirects in ServiceNow

When transitioning between ServiceNow Service Portals, redirecting pages is crucial to maintain user experience. While ServiceNow offers out-of-the-box page route maps for redirects within the same portal, switching portals requires a different approach. Using JavaScript Includes, similar to the method described for general web applications, can effectively redirect users from old URLs (e.g., /sp?id=sc_category) to new ones (e.g., /esc?id=esc_sc_category).

Handling Legacy Systems and CMS Migrations

During CMS migrations, such as moving from Percussion to Adobe Experience Manager (AEM), careful planning is essential to minimize bookmark breakage. Retaining old items (like discussion.html) and converting them to redirects can preserve access for users with outdated bookmarks. The Ensemble CMS, for example, provides a process for converting items to redirects by utilizing the Advanced tab within the item’s properties.

Conclusion

Implementing effective redirects is vital for maintaining a positive user experience during website changes. By understanding the various redirect methods available and following best practices, website administrators can minimize disruption and ensure that users can continue to access the content they need, even after URLs have been updated. Proactive planning and thorough testing are key to a successful transition.