Infrastructure/forgejo
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-29 02:44:08 -05:00
Code Issues Activity
forgejo/docs/content/administration/search-engines-indexation.en-us.md
John Olheiser bd4c7ce578
Docusaurus-ify (#26051) 
This PR cleans up the docs in a way to make them simpler to ingest by
our [docs repo](https://gitea.com/gitea/gitea-docusaurus).

1. It includes all of the sed invocations our ingestion did, removing
the need to do it at build time.
2. It replaces the shortcode variable replacement method with
`@variable@` style, simply for easier sed invocations when required.
3. It removes unused files and moves the docs up a level as cleanup.

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-07-26 04:53:13 +00:00

1.1 KiB
Raw Blame History

date title slug sidebar_position toc draft aliases menu
2019-12-31T13:55:00+05:00 Search Engines Indexation search-engines-indexation 60 false false
/en-us/search-engines-indexation
sidebar
parent name sidebar_position identifier
administration Search Engines Indexation 60 search-engines-indexation

Search engines indexation of your Gitea installation

By default your Gitea installation will be indexed by search engines. If you don't want your repository to be visible for search engines read further.

Block search engines indexation using robots.txt

To make Gitea serve a custom robots.txt (default: empty 404) for top level installations, create a file called robots.txt in the custom folder or CustomPath

Examples on how to configure the robots.txt can be found at https://moz.com/learn/seo/robotstxt.

User-agent: *
Disallow: /

If you installed Gitea in a subdirectory, you will need to create or edit the robots.txt in the top level directory.

User-agent: *
Disallow: /gitea/