Skip to content
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

Closed
Zocker1999NET opened this issue May 15, 2020 · 7 comments · Fixed by #18407
Closed

Generate a sitemap for SEO #11429

Zocker1999NET opened this issue May 15, 2020 · 7 comments · Fixed by #18407
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@Zocker1999NET
Copy link

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:

  • The sitemap should be available at the path /sitemap.xml.
  • The sitemap should at least list the main page of each public repository and group. The main page of the wiki's / all wiki's pages could be optional.
  • lastmod should be the date of the last commit to the README file / the wiki page itself
@lafriks
Copy link
Member

lafriks commented May 16, 2020

For big instances that would be large file

@Zocker1999NET
Copy link
Author

@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.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label May 17, 2020
@lunny
Copy link
Member

lunny commented May 17, 2020

If site didn't enable always login, then all public repositories' public routers could be generated to the sitemap file.

@turbopixel
Copy link

A sitemap with public repositories, profiles and organizations should suffice. Without any limitation, the sitemap will explode in size.

@Zocker1999NET
Copy link
Author

Also, the sitemap could be limited by an additional setting defining that the sitemap only contains the N repositories with the newest changes.

@sijanec
Copy link

sijanec commented Dec 14, 2020

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.

@techknowlogick
Copy link
Member

may specify additional sitemap files.

An example of a sitemap that references other sitemaps: https://www.google.com/sitemap.xml

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants