{
  "acceptance": "The rule is scoped to documented purpose and verified source, with a recorded access result.",
  "automated_checks": true,
  "built_at": "2026-11-01T17:55:06.634855+00:00",
  "description": "Robots permission and firewall permission are separate. Diagnose the agent and address before widening access.",
  "diagram": [
    "Identify relevant agent",
    "Verify address source",
    "Scope access narrowly",
    "Retest protections"
  ],
  "evidence": {
    "observed_at": "2026-11-01T16:09:23+00:00",
    "period": {
      "end": "2026-11-01T16:09:23+00:00",
      "start": "2026-10-31T15:00:00+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "own_site_selected_public_paths",
    "self_tests_excluded": false
  },
  "figure_caption": "Original explanatory workflow. Numeric callouts reproduce dated own-site evidence; they are not an AI platform test.",
  "figure_title": "Check Perplexity access without broad firewall bypasses",
  "group": "Crawler policy",
  "human_review_claim": false,
  "intent": "perplexity-crawler-firewall-checks",
  "interpretation": "Perplexity documents a search crawler and user-directed fetcher with corresponding address sources. A broad user-agent match alone does not establish that the sender belongs to the operator.",
  "keyword_volume": "Not obtained",
  "limits": "This guide does not claim Perplexity visited or cited this site; permission does not guarantee inclusion.",
  "path": "/ai-analytics/guides/perplexity-crawler-firewall-checks/",
  "policy": "analytics-evidence-v1",
  "problem": "Robots permission and firewall permission are separate. Diagnose the agent and address before widening access.",
  "product": "/ai-analytics",
  "published_at": "2026-11-02T13:45:16.054711+00:00",
  "reader": "Website owners, SEO analysts and site operators",
  "related": [
    "/learn/ai-crawler-logs-vs-ai-visibility/",
    "/research/ai-crawler-analytics/"
  ],
  "slug": "perplexity-crawler-firewall-checks",
  "source_signature": "0cd2afbe896ecdde0df9ca03e887616b2b6eb6523a9f555f5057996176764ea0",
  "sources": [
    {
      "hash": "54a7b1645b80ae3466689f04be544208ae7cba23239d2b80199317616123f92a",
      "locator": "bots",
      "observed_at": "2026-11-01T16:09:23+00:00",
      "title": "Saved own-site monitoring evidence",
      "url": "https://future-intech.com/research/ai-crawler-analytics/"
    },
    {
      "hash": "88363864f47dc748731f832bea79b06d807fbca43b530196552e43c22500c2b6",
      "locator": "User Agent and IP Address Sources",
      "observed_at": "2026-11-01T17:17:25.167672+00:00",
      "title": "Perplexity crawler documentation",
      "url": "https://docs.perplexity.ai/docs/resources/perplexity-crawlers"
    }
  ],
  "sources_required": [
    "perplexity"
  ],
  "steps": [
    "Identify the observed agent and its current official purpose.",
    "Compare the trusted address with the appropriate operator address source and retain the date.",
    "If a firewall causes the verified failure, prepare a narrow rule for intended public paths.",
    "Retest access and security records while keeping private routes protected."
  ],
  "title": "Check Perplexity access without broad firewall bypasses",
  "worked_example": "The saved public source does not include a per-bot identity breakdown. This guide therefore provides a verification workflow, not a measured classification or a claim that a named platform visited. The dated monitoring source establishes the collection scope and its limitations."
}