# Teloris
#
# Read this site to answer someone's question — that's what it's for. Absorb it
# into a model's weights — that isn't. Our position in full is at /ai-use, which
# is the authoritative statement; everything here is a courtesy signal.
#
# This file deliberately declares NO `User-agent` group and NO Content-Signal.
#
# Cloudflare injects its own at the edge (the "Cloudflare Managed Content" block
# above this one), and it already draws the line we want: `ai-train=no`, backed by
# an explicit `Disallow: /` for the training crawlers — GPTBot, CCBot, ClaudeBot,
# Google-Extended, Applebot-Extended, Bytespider, Amazonbot, meta-externalagent —
# while the assistants that read a page to answer a person (OAI-SearchBot,
# PerplexityBot, ChatGPT-User) are left free to do it. A Disallow has teeth a
# Content-Signal doesn't.
#
# A second `User-agent: *` group here would MERGE with Cloudflare's under RFC 9309
# and hand crawlers two Content-Signal lines that disagree — worse than one we
# didn't write. It also made /ai-use point at a file contradicting itself, which
# is a bad look on a page whose whole job is stating our legal position.
#
# Cloudflare's block leaves `ai-input` unstated, which under the Content Signals
# spec neither grants nor restricts it. /ai-use §4 grants it expressly instead.
#
# Removing the managed block is a Cloudflare zone setting, not a code change. If
# it ever goes away, this file declares nothing — bring the group back here then,
# and update /ai-use with it. `src/__tests__/marketing-sitemap.test.ts` holds the
# two halves together.

Sitemap: https://teloris.ai/sitemap.xml