# 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: /why-a-registry
Allow: /use-cases
Allow: /trust
Allow: /support
Allow: /terms
Allow: /privacy
Allow: /blog
Allow: /blog/

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