# Content Signals (contentsignals.org) — a declared preference, not access
# control. Cloudflare's AI bot settings are what actually enforce this; these
# three must be kept in step with them or we are saying one thing and doing
# another.
#
#   search=yes     index us and link to us — the whole point of the site
#   ai-input=yes   AI assistants MAY use our content to answer questions.
#                  Deliberately YES: being cited in an AI answer is traffic we
#                  want, and this mirrors Cloudflare's "Agent: Allow". The
#                  boilerplate example on contentsignals.org uses ai-input=no,
#                  which would opt us out of exactly the visibility we are
#                  chasing. Do not copy it.
#   ai-train=no    no scraping to train models — mirrors Cloudflare
#                  "Training: Block". Nothing is given back for it.
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Disallow: /*?utm_source=
Disallow: /*?ref=
Disallow: /chat-widget.html

# /products search results and the watchlist are per-visitor views of pages
# that are already indexed at their clean facet URLs (/products/laptops,
# /products/laptops/under-50000, /products/brands/samsung). js/products.js also
# writes `noindex` on these; this is the belt to that pair of braces, and it
# stops the crawl budget going into an infinite filter space.
Disallow: /products/*?q=
Disallow: /products/*?view=
Disallow: /products/*?features=
Disallow: /products/*?deals=
Disallow: /products?q=
Disallow: /products?view=
Disallow: /products?features=
Disallow: /products?deals=

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