# Static on purpose: the live site deploys via Firebase Hosting web frameworks,
# whose SSR function 404s the prerendered app/robots.ts metadata route (the
# Dockerfile/standalone builds on dev and demo served it fine). A public/ file
# is served directly by Firebase Hosting and by Next in standalone output.
# Cloudflare's managed robots.txt (content signals + AI-crawler blocks) is
# prepended to this on ventaz.ai — its per-bot Disallow groups can conflict
# with the explicit Allow groups below, so disable that block in Cloudflare
# for these allows to take effect reliably.

User-agent: *
Allow: /

# --- LLM & Search Crawlers to Allow ---
User-agent: Googlebot
Allow: /

User-agent: bingbot
Allow: /

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: CCBot
Allow: /

User-agent: Amazonbot
Allow: /

User-agent: Applebot
Allow: /

User-agent: Meta-ExternalAgent
Allow: /

User-agent: Twitterbot
Allow: /

User-agent: YouBot
Allow: /

User-agent: DuckDuckBot
Allow: /

Sitemap: https://ventaz.ai/sitemap.xml
Sitemap: https://ventaz.ai/images_sitemap.xml