User-agent: *
Disallow: /?q=
Disallow: /analytics/
Allow: /
# IETF AIPREF (draft-ietf-aipref-attach / -vocab): the policy in the comment below, stated so a
# machine can read it. Two categories are defined — train-ai and search — with values y/n, and an
# UNSTATED preference means "unknown", NOT "allowed". Saying nothing used to read as permission;
# under a preferences protocol it no longer does, which is why this line exists.
# Unknown directives are ignored per RFC 9309, so this is additive for every crawler that predates it.
Content-Usage: train-ai=y, search=y

Sitemap: https://theofficelines.com/sitemap-index.xml

# AI crawlers are welcome — all of them. At our stage the risk is invisibility, not scraping:
# our content (Office quotes) is already ubiquitous, so blocking training crawlers wouldn't stop
# any AI from answering — it would only remove US from the engines that cite + link back. We
# can't block our way out of zero-click; the clickable payload an AI text answer can't reproduce
# is the synced video clip. So: maximize presence + citation. (AI/LLM policy: see /llms.txt.)

# AI/LLM policy: see /llms.txt