How we do it
We use various Cloudflare products for our redirects, due to ease of use and speed1.
How we add redirects
Cloudflare Pages (primary)
This setup allows us to use the same workflow for redirects as for any other documentation change. We implement a redirect in the same pull request as the content change and can test these changes in our preview branches.
Bulk redirects (secondary)
Normally, bulk redirects only come up when another team is adding a large number of individual redirects to our site, such as when all of our previous
support.cloudflare.com content was migrated and needed individualized redirects per locale.
When we add redirects
Our team adds redirects in two situations: during the course of normal content and as needed based on data.
During content work
During normal content work, you want to add redirects when you do the following to a page:
- Change any part of the URL (filename, folder).
- Delete the page.
Based on data
Another time to add redirects is when you see a lot of
404 response codes on certain paths of your docs site. These
404 responses might be due to a missing redirect or mistyped link.
Performing redirects through Cloudflare lets you implement redirects on the Cloudflare global network instead of making requests travel all the way to an origin server. ↩︎