Honest time-to-impact: days–2 weeks (bots recrawl quickly once allowed)

• robots: PerplexityBot: blocked. blocking removes Perplexity citation eligibility within hours-days

# Allow AI answer-engine crawlers that drive buyer discovery
# Add the following lines to your brightfield.example file.
# Lines beginning with # are comments and are ignored by crawlers.

# --- AI answer-engine crawlers (explicitly allowed) ---
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

# --- Optional: uncomment the block(s) below if you also want to allow
#     training/indexing crawlers (separate from answer-engine access).
#     Review your content licensing position before enabling.
#
# User-agent: GPTBot
# Allow: /
#
# User-agent: ClaudeBot
# Allow: /
#
# User-agent: Google-Extended
# Allow: /
# ---

curl -s https:///brightfield.example | grep -A2 "PerplexityBot\|OAI-SearchBot\|Claude-SearchBot"

  grep -E "OAI-SearchBot|ChatGPT-User|Claude-SearchBot|Claude-User|PerplexityBot|Perplexity-User" /var/log/nginx/access.log

Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini) (typical range)

• You can't pitch a rival's own page — publish your own answer the engines can cite instead.
• upcheck.example (owned by Upcheck) — cited gemini×3, perplexity×2, claude×4 for q09, q18, q02, q01, q14
• beacon-uptime.example (owned by Beacon Uptime) — cited claude×1, gemini×1, perplexity×1 for q10
• Engines' stated reason Upcheck wins: "best budget-friendly all-rounder; easiest low-cost recommendation" (×1)
• [q09] Engines pick Upcheck here — stated reason: "Managed, easy setup, useful free tier and low ops overhead"
• [q18] Engines pick Falconware AI here — stated reason: "AI platform for platform engineering and incident monitoring"
• [q02] Engines pick Beacon Uptime here — stated reason: "best overall for most software teams; combines uptime monitoring, incident management, on-call, and status pages"
• [q01] Engines pick Beacon Uptime here — stated reason: "All-in-one solution combining monitoring, incident management, and status pages"
• 100% of the pages the engines cited are third-party — 0% are saylent-kestrel.vercel.app

Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini) (typical range)

• Beyond the pitches above, 2 more third-party pages the engines cite lack Kestrel Uptime — the SAME outreach playbook applies to each.
• brighthollow.example — cited claude×2, perplexity×1
• quiethollow.example — cited claude×1, gemini×1, perplexity×1 · quiethollow.example
• 100% of the pages the engines cited are third-party — 0% are saylent-kestrel.vercel.app

Honest time-to-impact: hours–days (Perplexity) → 2–4 weeks (Claude) (typical range)

• [q09] chatgpt: "Kestrel is probably overkill for this use case"
• [q09] chatgpt: "Kestrel potentially higher leverage later, but more platform/process surface area to manage."
• [q09] chatgpt: "I did not find a clearly named official 'Kestrel Uptime' product page in the search results"
• [q18] chatgpt: "couldn't find a well-established, clearly documented product called "Kestrel Uptime" by that exact name"
• [q18] chatgpt: "may be a very new, small, private-beta, or lightly indexed tool rather than a broadly known uptime-monitoring platform"
• [q18] chatgpt: "couldn't find enough authoritative documentation, pricing, feature breakdowns, customer references, or independent reviews"
• [q18] chatgpt: "the public evidence is too thin to judge well"
• [q18] chatgpt: "I'd be cautious"
• [q18] chatgpt: "the exact product identity was ambiguous and the public documentation appears sparse"
• [q09] claude: "my search results did not return any reliable, specific information about a product called "Kestrel Uptime" as a standalone uptime monitoring service."
• [q09] perplexity: "If your team needs on-call scheduling, better incident management, or more polished team workflows, comparison pages point to tools in the “Beacon Live/Beacon Uptime” category"
• [q18] perplexity: "the results here are mixed because “Kestrel” refers to multiple unrelated things, including the ASP.NET Core web server, a cyberthreat-hunting language, and other products, so the answer depends on wh"
• [q09] chatgpt: "If by “Kestrel Uptime” you mean Kestrel’s incident-response / platform-engineering automation product, then for a small engineering team without dedicated monitoring staff…"
• [q18] chatgpt: "I couldn’t find a well-established, clearly documented product called “Kestrel Uptime” by that exact name. Search results were mostly unrelated “Kestrel” products, plus a couple of status/monitori"
• [q09] claude: "I want to be upfront with you: my search results did not return any reliable, specific information about a product called "Kestrel Uptime" as a standalone uptime monitoring service. It's possible "
• [q09] Engines pick Upcheck here — stated reason: "Managed, easy setup, useful free tier and low ops overhead"
• [q18] Engines pick Falconware AI here — stated reason: "AI platform for platform engineering and incident monitoring"

Honest time-to-impact: 2–6 weeks (typical range)

• Missing on saylent-kestrel.vercel.app: Organization, Product, FAQPage
• JSON-LD Organization: No Organization schema found on any crawled page. Engines can't resolve who you are.
• JSON-LD Product: No Product schema found on crawled pages.
• JSON-LD FAQPage: No FAQPage schema found on crawled pages.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Kestrel Uptime",
  "url": "https://saylent-kestrel.vercel.app",
  "description": "Kestrel Uptime — Uptime monitoring and status pages"
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Uptime monitoring from four global regions",
  "brand": {
    "@type": "Brand",
    "name": "Kestrel Uptime"
  },
  "url": "https://saylent-kestrel.vercel.app",
  "category": "Uptime monitoring and status pages"
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Kestrel Uptime?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "TODO-VERIFY: one-sentence description of Kestrel Uptime (Uptime monitoring and status pages)."
      }
    }
  ]
}
</script>