Core format · included on every plan

Humans.txt

Attribution for the people behind the site.

3 / 5GEO score
TXT · Geordyhumans.txt
Why it matters

humans.txt is a tiny, well-known plain-text file that names the real people, tools and credits behind a site. Its value is that the address is conventional and the answer is in one place: anyone who needs to know who maintains this site, or when it was last touched, has somewhere to look that is not an about page written in marketing voice. Nothing consumes it automatically, and that is worth knowing before you spend time on it.

Geordy generates this format for every page on your site that warrants it - auto-detected by page type, served from your subdomain, and refreshed on the cadence below.

Sample outputhumans.txt
/* TEAM */
Site: Geordy
Role: AI visibility platform
Contact: https://geordy.ai/

/* SITE */
Standards: Schema.org, JSON-LD, YAML
Components: Next.js, React, TypeScript
Doctype: HTML5
Get it right

How to make this format work for AI.

DoBest practices
  • Save the file as /humans.txt (always lower-case) at the site root, UTF-8 encoded.
  • Reference it from the document head with `<link rel="author" type="text/plain" href="/humans.txt">` so crawlers discover it.
  • Use the conventional /* TEAM */, /* THANKS */ and /* SITE */ section headers so parsers and humans both recognise the structure.
  • Include role, name, contact (handle or URL - avoid raw email to limit spam), location, plus a Last update line in /* SITE */.
AvoidCommon pitfalls
  • Naming it Humans.txt or humans.TXT (case matters on Linux web servers) so the file 404s.
  • Putting raw email addresses in the file, which attracts spam scrapers - use "name [at] domain" or social handles.
  • Letting it go stale: the only signal that the site is human-maintained loses credibility once the Last update date is years old.
Where it shines

Use cases, scored for AI visibility.

Agency attributionGEO 4/5
Product company credibilityGEO 3/5
Content publisher transparencyGEO 3/5
Used in production by

Real sites already shipping Humans.txt.

Working with it

Tools & resources for Humans.txt.

The trade-offs
Strengths
  • Simple format requiring no special tools
  • Promotes transparency
  • Puts authorship and a maintenance date at one fixed address
Limitations
  • No AI engine or search engine documents consuming it
  • Limited adoption
  • Requires manual updates
  • Minimal traditional SEO impact
Spec sheet
Filename
humans.txt
Refresh cadence
monthly
Released
2011 · Abel Cabans
Written forPeople who open itAnything following your rel=author link

No AI engine publishes that it reads humans.txt, and this page will not name one that has not. What humans.txt is: one public, conventional address stating who stands behind the site and when it was last maintained, so that answer is the same wherever it is asked for instead of being scattered across bylines and an about page. Cheap to publish, and worth having when somebody asks who is behind a claim.

Written for these readers. Which of them actually request it is measured, not assumed: see how we measure.

Documented support
  • humanstxt.orgAn initiative for knowing the people behind a website, using a plain text file in the site root that credits who built it.
Observed requests

Not measured yet. Geordy will publish which crawlers request this file once enough independent sites are covered. See how we measure.

Other core formats

Generate every format at once.

Geordy emits 8 formats on every plan and 16 on Growth, auto-selected per page type and live on Geordy the moment they are written.

Humans.txt (.txt) format - spec, examples and AI readers | Geordy