Updated July 19, 2026

humans.txt fields reference

humans.txt credits the people and technology behind a site. There is no formal schema, but these section headers and fields are the widely used convention.

Common fields

Sections are marked with `/* TEAM */`-style comments; each line below is `Label: value`.

Field	Section	Purpose
`Developer`	TEAM	A person's role and name.
`Site`	TEAM	Contact — email, URL, or social handle.
`Location`	TEAM	Where the person or team is based.
`Twitter`	TEAM	Optional social handle, e.g. @jane.
`(name): (credit)`	THANKS	Credit contributors, libraries, or inspirations.
`Last update`	SITE	When the site was last updated.
`Language`	SITE	Content language(s), e.g. English.
`Standards`	SITE	Web standards used, e.g. HTML5, CSS3.
`Components`	SITE	Frameworks and tools the site is built with.

Example

The three common sections together.

/* TEAM */
Developer: Jane Doe
Site: jane@example.com
Location: Vienna, Austria

/* THANKS */
Icons: lucide.dev

/* SITE */
Last update: 2026-07-19
Language: English
Standards: HTML5, CSS3
Components: Next.js, React

Location and formatPublish the file at https://example.com/humans.txt as text/plain. Section headers use C-style comments (/* TEAM */); everything else is free-form.

No effect on SEOhumans.txt is a credits file for people. It is optional, has no standard schema, and does not affect crawling or ranking.

References

humanstxt.org — humanstxt.org

Questions

Are any humans.txt fields required?

No. humans.txt has no formal schema, so every section and field is optional. A TEAM section with at least one person is the common minimum.

How do I link to humans.txt?

Publish it at /humans.txt and, optionally, add `<link rel="author" href="/humans.txt">` in your page head so people can find it.