This section provides an overview of the document structure for redirects in our system. Below is a list of common elements and their descriptions.

  • Redirect Path: The path to which requests are redirected.
  • Source Path: The path that is being redirected.
  • Status Code: The HTTP status code that is returned when the redirect occurs.
  • Language: The language of the content to be served.
  • Parameters: Additional parameters that may be included in the redirect.

For more information on managing redirects, please refer to the Redirect Management Guide.


Here are some common redirect scenarios:

  • Permanent Redirect (301): This is used when a page has been moved permanently. It signals to search engines that the page has been permanently moved.

  • Temporary Redirect (302): This is used when a page is temporarily moved. It signals to search engines that the page may be moved back in the future.

  • Found (302): This is similar to the temporary redirect but is used for user agents (browsers) rather than search engines.

  • Not Found (404): This occurs when a requested resource is not found on the server.

For a deeper understanding of HTTP status codes, visit the HTTP Status Codes Reference.


Here is an example of a redirect in action:

  • Source Path: /old-page
  • Redirect Path: /new-page
  • Status Code: 301 - Moved Permanently

When setting up redirects, it's important to ensure they are correctly implemented to avoid any issues with user experience and search engine rankings.

Redirect Example