Developer docs
Developer docs
Breadcrumbs

Full site redirect from Subdomain to VA.gov

Up to date as of: March 3, 2025

This document helps you to better understand a full site redirect from a Subdomain to VA.gov. 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:

  1. File a redirect request ticket on GitHub.

  2. Read the Design System guidance for redirects.

This is a Server-side redirect

Full site, Subdomain to VA.gov redirects are server-side redirects. A server-side redirect sends a status code to the browser. This status code lets the browser know that the requested page has moved – or is no longer available – and points the browser toward the page’s new URL. Server-side redirects can be temporary or permanent.

Server-side redirects are preferred.

Full site, Subdomain to VA.gov redirects are complex redirects with a HIGH degree of difficulty.

Information Table: Full site redirects from Subdomainto VA.gov

Below is a table that outlines the details of a full site, Subdomainto VA.gov redirect.

Full site redirects from Subdomain to VA.gov

When to use this redirect:

When a full site is ready to migrate content to the modernized VA.gov site.

  • Requires technical contacts and access to the hosting server.

Real world examples:

  1. http://pittsburgh.va.gov/

  2. http://explore.va.gov

How it works:

Option 1: The platform team takes control of the entire subdomain. Traffic to http://pittsburgh.va.gov hits the VA gateway and gets routed to other servers, where a server-side permanent redirect is put in place that forwards the traffic along to VA.gov and our servers.

Option 2: For a .NET website, modify the .NET web.config (XML file). Example: http://explore.va.gov

Option 3: If a full site is in TeamSite, the WebOps team can redirect the site. Follow WebOps KB article steps (PIV required to access) to request the redirect.

Additional Info:

This redirect is dependent on VA stakeholders.

Authority to Operate (ATO) and Enterprise Security External Change Council (ESECC) approval must be considered.

Team Responsibilities:

If a subdomain or .NET site: The owners of the public website are responsible along with Platform Devops, and whatever veteran-facing team requests the redirect.

If a TeamSite: WebOps is responsible along with whatever veteran-facing team requests the redirect.

Additional Resources

Help and feedback