# Content signals: the same stance Cloudflare's managed robots.txt expressed,
# now stated here so it survives turning that feature off. Definitions and the
# canonical wording: https://contentsignals.org/
#
#   search:   building a search index and returning links and short excerpts.
#   ai-input: taking content into a model at answer time (RAG, grounding).
#   ai-train: training or fine-tuning models.
#
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
#
# search=yes and use=reference are deliberate, and are the whole point of this
# file: ShotPulled is built to be used from Claude and ChatGPT, so the crawlers
# that build those indexes must be able to read the page that explains how.
# Cloudflare's managed file disallowed ClaudeBot and GPTBot outright, which shut
# the product out of the two assistants it integrates with.

User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /

# The signed-in app (/dashboard, /beans, /equipment, /recipes, /history,
# /settings) is NOT disallowed, on purpose. Every response there carries
# `X-Robots-Tag: noindex` (src/middleware.js), and a crawler can only read that
# header on a path it is allowed to fetch. While these were Disallowed, Google
# indexed /dashboard from the links to it without ever seeing the noindex
# ("Indexed, though blocked by robots.txt"). A crawl of them is a redirect to
# sign-in and nothing more.

Sitemap: https://shotpulled.com/sitemap.xml