AI Workflow ยท Portfolio

Creating a Redirect-Only Repository for Old github.io Links

How the old github.io address was restored only as an index.html and 404.html redirect shim while the real site stayed on Cloudflare Pages.

June 1, 2026

Decision

After the old GitHub Pages URL was disabled, old links returned a 404. Keeping the 404 was clean but unfriendly, so the better practical option was to recreate the github.io repository as a redirect-only shim.

Implementation

  • Created a public ytkim4558.github.io repository with only README, index.html, 404.html, robots.txt, and .nojekyll.
  • Used meta refresh and JavaScript location.replace to forward users to the same path on https://ytkim4558.pages.dev/.
  • Kept noindex,follow and canonical metadata pointing to the Cloudflare Pages URL.
  • Recorded the distinction in agent-ops so future agents do not put real content in the redirect repository.

Constraint

GitHub Pages does not provide a custom server-level 301 rule for this static user-site setup. Deep links use the custom 404 page, so browsers redirect correctly but the HTTP status remains 404.