Docker/forgejo
Docker/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2025-08-05 01:45:22 +02:00
Code Issues Releases Activity

Rename develop -> development, contribute -> contributing, administer -> administration (#23662)

Browse source 
backport #23629 

To make versioned documentation less surprising, 1.19 should have the
same technology.
This commit is contained in:
Lunny Xiao 2023-03-24 04:44:09 +08:00 • committed by GitHub
parent e7a5429d7a
commit 162f2841d0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
121 changed files with 257 additions and 342 deletions
Download patch file Download diff file Expand all files Collapse all files

38
docs/content/doc/administration/search-engines-indexation.en-us.md Normal file
View file

@ -0,0 +1,38 @@
---
date: "2019-12-31T13:55:00+05:00"
title: "Advanced: Search Engines Indexation"
slug: "search-engines-indexation"
weight: 30
toc: false
draft: false
menu:
sidebar:
parent: "administration"
name: "Search Engines Indexation"
weight: 60
identifier: "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`]({{< relref "doc/administration/customizing-gitea.en-us.md" >}})
Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt).
```txt
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.
```txt
User-agent: *
Disallow: /gitea/
```