Redirect old doc pages to new locations
See original GitHub issueAs part of the docs restructuring #8443 some pages are moved, so the old URLs now return 404. Some of these pages have a lot of incoming links so I think it’s important to keep them working.
First we need to create a list of pages we want to keep working (TODO).
Then we need to implement the redirects. I think there are two ways to go about that:
- HTTP redirects - requires server configuration. Looks like ReadTheDocs can do it.
- HTML redirects - requires placeholder pages with
<meta refresh>
. Can use a sphinx plugin to do it or implement one ourselves.
I think server redirects are easier and more recommended. I can add them unless someone objects (I would need permissions for RTD though).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Need to ReDirect old document URL's to new location ... - MSDN
Ideally, we would like insert "/sites/" into the old URL string when the request hits a WFE, redirecting the request to the new...
Read more >How to redirect old URLs to new pages in your Webflow site ...
Open Site Settings · Go to Hosting tab · Scroll down to 301 Redirects section · Add old URL (/old-url) · Add new...
Read more >The Ultimate Guide to Redirects: URL ...
Redirects send users & search engines from one URL to another. Find out how to use each type here.
Read more >Redirects and Google Search
Redirecting URLs is the practice of resolving an existing URL to a different one, effectively telling your visitors and Google Search that a ......
Read more >Redirect Users to New Pages : TechWeb
If you have pages in your static content (non-WordPress) site that will no longer be used, or pages that have been moved to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I like the stub approach, and I suppose it could even stay around “forever” given how much those links exist over the web. 👍
I went ahead and added a RTD redirect from
/en/latest/warnings.html
->/en/latest/how-to/capture-warnings.html
, so at least that one works correctly. There’s probably more, and I have no idea how to handle this for multiple versions (there’s a “page redirect”, but doing that redirect for the old versions would be wrong…).