[vitonsky]

> The old URL redirects to the new one, so in theory existing posts/backlinks keep working. We also agreed the original creator wouldn’t reuse the “unity-mcp” repo name under his GitHub profile, which could break redirects.

Why?

A lot of times I faced with page 404 when clicked GitHub links that have been moved.

Isn't it good idea to do it like that - Move repo to new org (to move stats and activity) - Create repo with the same name that are fork of a target repo - Update readme to explain repo was moved - Archive the repo to place a warning on top of the repo

This way make users have to click link in original github repo, to go on your repo.

So it would be a problem if you need to show a numbers and you need to fake activity. But if you don't need fake activity, it is not a problem, because a real people who really looking for solution will be able to click one more link.

On the other hand, this way ensure that whole content will be available by indexed links.

How to prevent 404 and why people still faces with it on GitHub?

[8organicbits]

I've always seen the redirect when the repo is moved. The GitHub docs mention the redirect as well. Are you sure you're not seeing another scenario like a fork and the original repo is deleted?