Infrastructure

# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI 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.

# BEGIN Cloudflare Managed content

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

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

# PotentialSpouse is a private matchmaking application — profile
# data, codenames, chat content, and any signed-in route MUST NOT be
# indexed by search engines. The public marketing surface (homepage,
# /about, /use-cases, /support, /terms, /privacy, /blog) is fair game
# and helps people find the product when they have a real need; the
# rest is denied.
#
# See `project/PRD.md` §3 and `project/reveal_ladder.md` for the
# anti-recognition posture these rules reinforce.

User-agent: *

# Authenticated app surface — never indexable.
Disallow: /wall
Disallow: /notifications
Disallow: /connections
Disallow: /connections/
Disallow: /profile
Disallow: /profile/
Disallow: /settings
Disallow: /settings/
Disallow: /report
Disallow: /admin
Disallow: /admin/

# Auth + onboarding surfaces — also denied so a returning user's
# codename never appears in a search snippet via cached state.
Disallow: /users/
Disallow: /auth/
Disallow: /onboarding/

# Operational endpoints.
Disallow: /api/
Disallow: /health
Disallow: /readiness
Disallow: /dev/

# Everything else (homepage + public marketing pages + blog) is
# allowed by default — Allow lines exist so robots that read both
# rules pick the most permissive match.
Allow: /
Allow: /about
Allow: /use-cases
Allow: /support
Allow: /terms
Allow: /privacy
Allow: /blog
Allow: /blog/

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