Redirects
Redirects protect against web links that reference obsoleted (moved, deleted, or consolidated) content on your site. Redirect URLs map source links to target links, where source links are URLs to obsoleted assets, and target links are URLs to new, replacement assets. Redirects can be either permanent (301 redirects) or temporary (302 redirects).
You can add redirect URLs at the asset level or the site level.
There are a number of ways you can add redirects in Brightspot.
Asset redirects
A prerequisite for setting a redirect URL is that the URL itself no longer exist on the obsolete asset. This is accomplished in one of the following ways:
- Delete the obsolete asset. However, note that deleting assets can impact your data retention efforts (see Archiving and deleting assets).
- Remove the permalink from a published or archived asset (see Deleting a URL) .
Using target permalinks is one of the more common ways to create an asset level redirect. This is accomplished directly on the content edit page for the asset that is being redirected; however, you can also use vanity URL redirects and wildcard redirects for assets.
Site redirects
Site redirects are used when publishers need to redirect a legacy domain to a new domain or path.
For example, a publisher wants to close the site https://www.example.com. All requests should now go to https://www.brightspot.com. By creating a site redirect, a publisher is able to ensure that when visitors access https://www.example.com, they are re-routed to https://www.brightspot.com.
Additionally, site redirects can redirect legacy domains to URL paths. Using the example above, the site redirect routes a visitor from https://www.example.com to https://www.brightspot.com/example.
Site redirects can be created from any site or from the Global site.
For more information on the types of redirects, see Types of redirects.