Use 301 redirect to preserve SEO (Google ranking) in Github Pages

[ge0ffrey]

We have a few urls that rank high on Google (ranking which took 10+ years to get), for example:
…mydomain.org/learn/useCases/myKeyword.html.
Now, we want to change its url to improve it:
…mydomain.org/use-cases/my-keyword.html

However, when we would make this change, we would loose all Google ranking, unless we redirect. Now there are 2 ways to redirect:

• meta redirect, done in the html file. This is not recommended and several SEO videos state it hurts your page ranking, aside from increasing the page load time.
• a 301 redirect. Google recommends this approach.

Does GitHub Pages support a 301 redirect?

[yoannchaudet]

Hello,

Unfortunately GitHub Pages does not support HTTP (e.g. 301) redirections today.

[trusktr]

GitHub, can you please add support for URL rewrites in a safe way?

GitHub pages for single page apps (SPAs) without pre-generated HTML pages is really bad: the only way to do it is to redirect to a 404.html page, and Google will ignore indexing these pages, making the content invisible.

[weizman]

Hi @ge0ffrey did you ever manage to solve this? I'm having the same problem sadly..

[webketje]

Would replacing the file with a symlink to the new location and a rel="canonical" href="/new/location/" do the trick for SEO?
Untested but this may be worth a try

[QaisarRajput]

Guys is there any update on this. Any other method to achieve this.?

[XBEAST1]

This really sucks

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐