Organization site to redirect old GitHub Pages URLs.
Renaming or transferring a repository has an impact on URLs:
https://github.com/<new_org>/<new_repo>
is created.https://github.com/<org>/<repo>
will automatically redirect to the new repo URL.https://<new_org>.github.io/<new_repo>
is created.https://<org>.github.io/<repo>
returns a 404 error.Any reference to the old Github Pages URL https://<org>.github.io/<repo>
is now broken.
This https://github.com/<org>/<org>.github.io
repository has an associated organization site, served from https://<org>.github.io
. By creating subdirectories, we can redirect old GitHub Pages URLs:
<repo>
. This will break the old GitHub Pages URL https://<org>.github.io/<repo>
.<repo>
(see the repo for examples).index.html
to that directory, with the following content (replace the URL
with the new GitHub Pages URL):<html>
<head>
<meta http-equiv="refresh" content="0;URL=https://<new_org>.github.io/<new_repo>/">
</head>
</html>
https://<org>.github.io/<repo>/
. It will redirect without delay to the new GitHub Pages URL.Note that only the homepage https://<org>.github.io/<repo>/
will be redirected. This is typically sufficient, since subpages are seldom referenced elsewhere. To redirect subpages, either:
404.html
with the same content as index.html
to redirect all subpages to the new homepage.path/to/subpage/index.html
file (with specific URL
) to redirect a specific subpage.