{
  "acceptance": "The closure links the original incident, implemented change, dated response and subsequent monitored interval.",
  "automated_checks": true,
  "built_at": "2026-11-01T18:05:16.005402+00:00",
  "description": "A healthy page now and an earlier failure can both be true. Retain the incident and add dated recovery evidence.",
  "diagram": [
    "Preserve failed window",
    "Check public response",
    "Observe a later interval",
    "Check indexing separately"
  ],
  "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": "Document recovery without rewriting an incident",
  "group": "Access diagnostics",
  "human_review_claim": false,
  "intent": "analytics-incident-recovery-evidence",
  "interpretation": "Current HTTP success establishes one response. It does not prove uninterrupted availability between checks, identify affected users or establish that Google processed the recovered page.",
  "keyword_volume": "Not obtained",
  "limits": "No cause is asserted without matching operational evidence. Recovery does not guarantee search rankings.",
  "path": "/ai-analytics/guides/analytics-incident-recovery-evidence/",
  "policy": "analytics-evidence-v1",
  "problem": "A healthy page now and an earlier failure can both be true. Retain the incident and add dated recovery evidence.",
  "product": "/ai-analytics",
  "published_at": "2026-11-02T03:35:03.639582+00:00",
  "reader": "Website owners, SEO analysts and site operators",
  "related": [
    "/learn/ai-crawler-logs-vs-ai-visibility/",
    "/research/ai-crawler-analytics/"
  ],
  "slug": "analytics-incident-recovery-evidence",
  "source_signature": "777d3aededa76adeef9990a35db332327092f4a9aa19a1538dde62c861016aa5",
  "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": [
    "Preserve interval, paths, statuses and relevant service records.",
    "After a scoped fix, check the real public HTTPS URL and expected body anonymously.",
    "Observe a later complete interval, distinguishing no observed recurrence from guaranteed availability.",
    "Check search-system state separately when indexing matters."
  ],
  "title": "Document recovery without rewriting an incident",
  "worked_example": "Earlier errors for exact public paths remain in the source. A later successful check belongs in a separate recovery record, not a replacement failure count."
}