-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate a sitemap for SEO #11429
Comments
For big instances that would be large file |
@lafriks Yeah, that's right. Because of the size of the sitemap, this feature should be optional and disabled by default. Also a good caching system needs to be implemented, so that a few accesses to the sitemap does not overload the server. |
If site didn't enable always login, then all public repositories' public routers could be generated to the sitemap file. |
A sitemap with public repositories, profiles and organizations should suffice. Without any limitation, the sitemap will explode in size. |
Also, the sitemap could be limited by an additional setting defining that the sitemap only contains the N repositories with the newest changes. |
An alternative would be a sitemap per repository and per user. And of course a global sitemap, as sitemaps can be recursive and may specify additional sitemap files. They could be generated dynamically. |
An example of a sitemap that references other sitemaps: https://www.google.com/sitemap.xml |
Gitea could generate a sitemap for SEO, so crawlers can search through public repositories more easily. It could be useful for some admins that their instances will be crawled and ranked by search engines. A good explanation for the format of
sitemap.xml
can be found on Wikipedia.In my opinion this feature should do the following:
/sitemap.xml
.lastmod
should be the date of the last commit to the README file / the wiki page itselfThe text was updated successfully, but these errors were encountered: