{
  "acceptance": "The report distinguishes a request-volume observation from its supported service impact and unknown acquisition meaning.",
  "automated_checks": true,
  "built_at": "2026-11-01T18:05:16.005402+00:00",
  "description": "A larger request count can reflect repeated fetches or operational checks. Investigate the burst before claiming audience growth.",
  "diagram": [
    "Locate narrow interval",
    "Compare status and load",
    "Check controlled activity",
    "Keep intent unresolved"
  ],
  "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": [
      {
        "label": "2026-10-31 UTC",
        "unit": "requests",
        "value": 116
      },
      {
        "label": "2026-11-01 UTC",
        "unit": "requests",
        "value": 342
      }
    ],
    "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": "Investigate request bursts without calling them audience growth",
  "group": "Access diagnostics",
  "human_review_claim": false,
  "intent": "crawler-request-bursts",
  "interpretation": "Aggregate requests lack the context needed to identify unique visitors or intent. A burst may warrant performance investigation even when its acquisition meaning remains unknown.",
  "keyword_volume": "Not obtained",
  "limits": "No attack, bot identity or customer growth is inferred solely from a spike. Avoid publishing raw visitor details.",
  "path": "/ai-analytics/guides/crawler-request-bursts/",
  "policy": "analytics-evidence-v1",
  "problem": "A larger request count can reflect repeated fetches or operational checks. Investigate the burst before claiming audience growth.",
  "product": "/ai-analytics",
  "published_at": "2026-11-02T08:05:03.478333+00:00",
  "reader": "Website owners, SEO analysts and site operators",
  "related": [
    "/learn/ai-crawler-logs-vs-ai-visibility/",
    "/research/ai-crawler-analytics/"
  ],
  "slug": "crawler-request-bursts",
  "source_signature": "7ca20a2803d39617ce4837349c1e7bece2db6724e2d73feee64db1705af143e1",
  "sources": [
    {
      "hash": "54a7b1645b80ae3466689f04be544208ae7cba23239d2b80199317616123f92a",
      "locator": "daily",
      "observed_at": "2026-11-01T16:09:23+00:00",
      "title": "Saved own-site monitoring evidence",
      "url": "https://future-intech.com/research/ai-crawler-analytics/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Locate the narrow time interval and paths responsible using authorized aggregates.",
    "Compare status distribution and service resource records during that interval.",
    "Check known deployments and controlled tests without forcing them to explain every request.",
    "Report unresolved identity and intent separately from any verified operational consequence."
  ],
  "title": "Investigate request bursts without calling them audience growth",
  "worked_example": "Our daily source includes mixed observations and unequal partial days. It can direct an operator to a time window, but cannot identify the cause of a burst by itself."
}