# Richport Media Inc. — richportmedia.ai
#
# Until this file existed the site had no origin robots.txt at all, so
# Cloudflare's managed one was served in its place: 1,248 bytes of content-
# signals boilerplate with no User-agent, no Allow and no Sitemap line — a
# robots.txt that Search Console could not follow to the sitemap. Keep
# Cloudflare's "Managed robots.txt" toggle OFF: it replaces this file rather
# than appending to it, and would drop the Sitemap line again.
#
# The whole site is crawlable. There is nothing here to hide from search —
# fourteen public pages, eight sales and six legal, plus an error page — and
# the pages themselves no longer carry the pre-launch noindex tag that kept
# all of them out of the index.
#
# Content signals are open on purpose, including training. The site is a
# calling card: being indexed, cited, referenced and recommended is the entire
# job, and presence in the standing knowledge of future models serves that.
# The method is already withheld at the source — the pages state plainly that
# targeting and the media mix stay proprietary — so what is public is the
# category, the documented record and the operator. The defensibility is the
# record and the relationships, neither of which is a capability a model can
# transfer to someone else.
#
# Note what ai-train=yes gives up: under the Content Signals spec an omitted
# signal neither grants nor restricts and reserves rights under Article 4 of
# EU Directive 2019/790. An explicit yes waives that reservation. Change it to
# `no` to take the reservation back; nothing else here depends on it.
#
# These signals are advisory — honored by companies that would have behaved
# regardless. Anything actually abusing this site ignores robots.txt by
# definition, so abuse is a job for edge enforcement (Cloudflare AI Crawl
# Control), not for this file.

User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=yes
Allow: /

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