Page-level cross-domain redirect

Last Updated: October 22, 2024

This document helps you to better understand aSubdomain to Subdomain page-level redirect. For more information about redirects, return to the Redirect Implementation Strategy page.

The Sitewide Content, Accessibility & Information Architecture team (CAIA) reviews all URL redirects before routing them to the appropriate engineer.

Before you attempt a redirect, follow these two important steps:

File a redirect request ticket on GitHub.
Read the Design System guidance for redirects.

This is a client-side redirect

Subdomain to Subdomain redirects are client-side redirects that require identifying subdomain admins. This is a complex redirect with a HIGH degree of difficulty.

Client-side redirects should only be used when absolutely necessary.

Information Table: `Subdomain`to `Subdomain` Redirects

Below is a table that outlines the details of a Subdomainto Subdomain redirect.

Page-level cross-domain redirect: `Subdomain` to `Subdomain`
When to use this redirect:	When a subdomain page needs to redirect to a different subdomain. Requires identifying the subdomain admin, whether TeamSite or otherwise.
Additional Info:	This redirect is dependent on VA stakeholders.
Team Responsibilities:	If the source subdomain is NOT a TeamSite: The owners of the subdomain may be able to perform the redirect. This requires stakeholder involvement and a technical contact with admin access to the source server, to implement the redirect. If the subdomain is a TeamSite: Requesting team must follow WebOps KB article (PIV required to access) steps to file a WebOps ticket to start the process. WebOps must help identify the owner of the TeamSite. TeamSite admins who are identified will then be asked to execute the redirect. If the TeamSite admins are unable to update the site, they may request a client-side redirect. Contact the CAIA team for more information. This redirect is dependent on VA stakeholders.

Special Note

❌ Do not archive redirected TeamSite pages. Instead, product team should implement the client-side redirect, with additional ask of VA stakeholder to:

✅ Replace their page content with a 'redirect' message and
✅ Update their print materials and nav links with the new URL

Additional Resources

To learn more about redirects, visit Redirect Implementation Strategy page.
To learn about redirects involving Drupal, visit Drupal Redirects.
For information on redirecting forms like PDFs, visit Redirecting static documents.
For any questions regarding redirects, contact the CAIA team in their Slack channel #sitewide-content-accessibility-ia.

Help and feedback

Suggest content changes to this page.
Submit new Platform Website content.
Get help from the Platform Support Team in Slack.
Submit a feature idea to the Platform.

This is a client-side redirect

Information Table: Subdomainto Subdomain Redirects