# adr.smlcompany.ca
# AI crawlers are deliberately allowed. Being read by an assistant that counsel
# is using to shortlist a neutral is the point. See docs/04-seo-spec.md.

# EXACTLY ONE THING IS DISALLOWED, AND IT IS A SUBSTITUTE FOR A MECHANISM THIS
# DISTRIBUTION IS NOT ALLOWED TO HAVE.
# The bio PDF duplicates /bio/. The intended fix was `X-Robots-Tag: noindex` on
# *.pdf via a CloudFront response-headers policy, which the distribution's
# pricing plan forbids — AGENTS.md §7, and docs/09 Part 3 for the three failed
# attempts. Disallow is the remaining lever and it is NOT the same instrument:
#   - it stops the PDF being FETCHED, so its contents are never indexed and the
#     duplicate-content problem it was raised for is solved;
#   - it does NOT de-index the URL. The PDF is linked from /bio/ and /about/, so
#     a search engine can still list the bare URL with no snippet.
# That residual is accepted deliberately: a bare link to a bio PDF is not the
# harm the noindex was for. Revisit if the pricing plan ever changes.
#
# /legal/* is still NOT disallowed, and that reasoning is unchanged — it is the
# general rule this one path is the exception to. A crawler forbidden to FETCH a
# URL never reads the `noindex` on it, so the two cancel; the legal pages are
# linked from every footer, so they are discovered regardless, and the pair would
# have produced bare "no information available" listings with the directive that
# would have suppressed them sitting unread behind the wall.
# `noindex` is what de-indexes; `Disallow` is what prevents fetching. Use the one
# that matches the problem, and never both on the same path.

User-agent: *
Disallow: /pouya-lajevardi-bio.pdf
Allow: /

Sitemap: https://adr.smlcompany.ca/sitemap-index.xml