{
  "acceptance": "The handoff names a failing layer only when a matching record supports it. A dated successful response and subsequent observation document recovery separately.",
  "automated_checks": true,
  "built_at": "2026-11-01T17:32:50.400276+00:00",
  "description": "A traffic report shows gateway errors. Locate the failing path and time window before changing bot rules or rewriting content.",
  "diagram": [
    "Locate error window",
    "Match upstream evidence",
    "Check exact public path",
    "Observe a later interval"
  ],
  "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": [
      {
        "detail": "2026-11-01T04:57:29+00:00 to 2026-11-01T14:29:05+00:00",
        "label": "/ · HTTP 502",
        "unit": "requests",
        "value": 28
      },
      {
        "detail": "2026-10-31T15:20:32+00:00 to 2026-11-01T02:15:59+00:00",
        "label": "/ai-analytics · HTTP 502",
        "unit": "requests",
        "value": 6
      }
    ],
    "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 502 responses before changing crawler rules",
  "group": "Access diagnostics",
  "human_review_claim": false,
  "intent": "ai-crawler-502-investigation",
  "interpretation": "A saved 502 establishes a failed request in the observed layer. It does not identify the visitor, prove a bot was blocked, or locate the failing upstream component. Separate the access incident from the visibility question.",
  "keyword_volume": "Not obtained",
  "limits": "The source includes controlled checks; affected people, verified AI crawlers and ranking effects were not measured.",
  "path": "/ai-analytics/guides/ai-crawler-502-investigation/",
  "policy": "analytics-evidence-v1",
  "problem": "A traffic report shows gateway errors. Locate the failing path and time window before changing bot rules or rewriting content.",
  "product": "/ai-analytics",
  "published_at": "2026-11-01T17:33:16.659688+00:00",
  "reader": "Website owners, SEO analysts and site operators",
  "related": [
    "/learn/ai-crawler-logs-vs-ai-visibility/",
    "/research/ai-crawler-analytics/"
  ],
  "slug": "ai-crawler-502-investigation",
  "source_signature": "129a40bfdc11046607958b36a9a5914657c63acc4a6cc112bd91954088690fcf",
  "sources": [
    {
      "hash": "54a7b1645b80ae3466689f04be544208ae7cba23239d2b80199317616123f92a",
      "locator": "paths",
      "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": [
    "Export the path, status, first and last timestamp, count and timezone. Preserve the source edition.",
    "Match the window to authorized proxy errors and application health records. Treat deployment timing as a hypothesis until a matching error supports it.",
    "Repeat a normal anonymous request to the exact path, retaining the final status and body. A forged crawler label cannot prove identity.",
    "After a verified fix, inspect a later complete collection interval and record any recurrence."
  ],
  "title": "Investigate 502 responses before changing crawler rules",
  "worked_example": "The linked monitoring report retains error windows for the homepage and Analytics page. Start with those exact locations. A successful request now does not erase earlier errors; keep both the incident window and recovery check."
}