{
  "acceptance": "The request-to-representation matrix is reproducible and matches the intended behavior. The report includes the selection context, rather than treating every response at one URL as interchangeable.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Accept-Language communicates language preferences."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Vary lists request headers used in representation selection so caches can account for them."
    }
  ],
  "description": "Compare language and representation selection before labeling different responses at one URL as an indexing or analytics defect.",
  "diagram": [
    "Request A: selected language preference",
    "Request B: different controlled preference",
    "Vary: declared selection inputs",
    "Responses: compare intended variants"
  ],
  "draft_hash": "e56694cd28bb205815fbb33fde3bd0fd9b34062c8c0f1a596985e5b7cfc46c1d",
  "evidence": {
    "observed_at": "2026-11-02T19:15:16.193992+00:00",
    "period": {
      "end": "2026-11-02T19:15:16.193992+00:00",
      "start": "2026-11-02T19:15:16.193992+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "comparison",
  "figure_notes": [
    "Save the first request’s relevant selection headers.",
    "Change one input while keeping the other conditions fixed.",
    "Check which request fields the cache must distinguish.",
    "Compare language and response fingerprints against intent."
  ],
  "figure_title": "Explain different crawler responses using Vary",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "vary-language-crawler-responses",
  "interpretation": "Content negotiation allows a server to choose a representation using request headers. MDN describes Accept-Language as a language preference and Vary as the response header that names request fields used in selection. A URL-only comparison can therefore overlook meaningful request context. Record the relevant request headers and response language or content fingerprint before interpreting differences as a crawler-specific failure.",
  "keyword_volume": "Not obtained",
  "limits": "Vary is a declaration used by caches, not proof that every cache honored it. User-agent names and language preferences do not establish the identity or purpose of an AI platform request.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/vary-language-crawler-responses/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "Two requests to one URL receive different language or content representations and the report assumes they received identical pages.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T12:40:22.415748+00:00",
  "reader": "Site owners and analysts investigating two requests to one URL receive different language or content representations and the report assumes they received identical pages.",
  "related": [
    "public-path-inventory-coverage",
    "crawler-user-agent-verification"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/public-path-inventory-coverage/",
      "title": "Audit which public paths analytics actually covers"
    },
    {
      "path": "/ai-analytics/guides/crawler-user-agent-verification/",
      "title": "Separate crawler names from verified request identity"
    }
  ],
  "research_document_ids": [
    "89d9f6cf9a30f8860b9196d9eef421e1"
  ],
  "slug": "vary-language-crawler-responses",
  "source_signature": "901620e70d87a47d15d213309862cd8301d72464e3739901ce0602e652b70c88",
  "sources": [
    {
      "hash": "80ffa5045dd6dcc8a06c739d1763f157d8cc6bd01e552e8d47a099cc646d7ce5",
      "locator": "The Accept-Language header / b24; The Vary response header / b31",
      "observed_at": "2026-11-02T19:15:16.193992+00:00",
      "title": "Content negotiation",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Content_negotiation"
    }
  ],
  "sources_required": [],
  "steps": [
    "Capture the exact public URL and relevant request headers for each comparison. Keep cookies and authorization information out of the exported evidence.",
    "Inspect Vary and record the delivered language or a response fingerprint. Change one selection input at a time so the comparison can identify which input matters.",
    "Repeat equivalent requests through the actual delivery path. Compare the observed variants with the intended site behavior, including any explicit language selector.",
    "If the variants are unintended, correct the narrow negotiation or cache configuration and rerun the same matrix. Keep language selection separate from canonical and indexing checks."
  ],
  "title": "Explain different crawler responses using Vary",
  "worked_example": "Hypothetical example: a browser requesting one language receives a localized page while a diagnostic client with a different preference receives another version. The first question is whether representation selection is intentional and consistent. If a shared cache serves the wrong version under repeated controlled conditions, investigate how its cache selection matches the documented Vary behavior. Do not jump from a language mismatch to a claim that an AI service was misled."
}