Currently, RVX Manager repository is not indexed in Google Search.
This is because Google Search will never index a forked repository if it has the same name as the original repository.
Changing the repo name will allow the repo to be indexed in Google Search.
This reduces the risk of users seeking RVX Manager landing on dangerous fake sites.
Basis
There is some basis for this.
For example, inotia00/revanced-patches repository was previously not indexed because it had the same name as upstream, but is now indexed because the upstream repo was renamed to "revanced-patches-template".
https://www.google.com/search?q=inotia00+patches
ReVanced/GmsCore is also not indexed because it is same name as upstream.
(In this repository, some pages such as the Security Overview and the latest release are indexed, so this isn't a problem. But the top page is still not indexed.)
Last year, I renamed my "revanced-manager-android6-7" repo to "revanced-manager" as a test.
As a result, my repository became completely invisible to Google search within a few weeks.
I then renamed the repository to "revanced-manager-android5-7" and it slowly started to appear in search results.
(However, there is an exception.)
There seem to be exceptions when there is a big difference in page popularity.
inotia00/VancedMicroG was the exception.
For some reason, Google indexed inotia00/VancedMicroG instead of TeamVanced/VancedMicroG.
I think this is based on the popularity of the page, the number of inbound links, etc.
But TeamVanced's sites are now indexed again for its' top page.
Easyness
There is very little you have to do to rename the repository.
All access to the old repository name will be redirected so even the in-app update function in RVX Manager will continue to work.
(This is confirmed with my manager fork)
So you can rename the repo without any preparation.
If you find any old links, you can gradually change them.
(However, I don't know anything about Webhooks and stuff, so there is a possibility that unexpected problems may occur here if you didn't changed the repo name...)
The description should also be changed
Also, if you decided to rename repo, I recommend to change the repo description as well.
The repo description will be shown as a page title in Google search result.
Acknowledgements
[X] This issue is not a duplicate of an existing suggestion.
[X] This is not a feature request.
[X] I have chosen an appropriate title.
[X] All requested information has been provided properly.
[X] I have written the title and contents in English.
Application
Other
Suggestion description
Currently, RVX Manager repository is not indexed in Google Search.
This is because Google Search will never index a forked repository if it has the same name as the original repository.
Changing the repo name will allow the repo to be indexed in Google Search.
This reduces the risk of users seeking RVX Manager landing on dangerous fake sites.
Basis
There is some basis for this.
For example, inotia00/revanced-patches repository was previously not indexed because it had the same name as upstream, but is now indexed because the upstream repo was renamed to "revanced-patches-template". https://www.google.com/search?q=inotia00+patches
ReVanced/GmsCore is also not indexed because it is same name as upstream. (In this repository, some pages such as the Security Overview and the latest release are indexed, so this isn't a problem. But the top page is still not indexed.)
Last year, I renamed my "revanced-manager-android6-7" repo to "revanced-manager" as a test. As a result, my repository became completely invisible to Google search within a few weeks. I then renamed the repository to "revanced-manager-android5-7" and it slowly started to appear in search results.
(However, there is an exception.)
There seem to be exceptions when there is a big difference in page popularity. inotia00/VancedMicroG was the exception. For some reason, Google indexed inotia00/VancedMicroG instead of TeamVanced/VancedMicroG. I think this is based on the popularity of the page, the number of inbound links, etc. But TeamVanced's sites are now indexed again for its' top page.Easyness
There is very little you have to do to rename the repository.
All access to the old repository name will be redirected so even the in-app update function in RVX Manager will continue to work. (This is confirmed with my manager fork)
So you can rename the repo without any preparation.
If you find any old links, you can gradually change them.
(However, I don't know anything about Webhooks and stuff, so there is a possibility that unexpected problems may occur here if you didn't changed the repo name...)
The description should also be changed
Also, if you decided to rename repo, I recommend to change the repo description as well. The repo description will be shown as a page title in Google search result.
Acknowledgements