{
  "acceptance": "Close deployment verification when the public response matches the intended revision. Close Google-cache verification only after obtaining matching Google-side evidence; leave it pending if that evidence is unavailable.",
  "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": "The updated robots.txt file must be uploaded to the site’s root location."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google documents periodic robots-cache updates and a Search Console recrawl option."
    }
  ],
  "description": "Keep the uploaded robots file, public response and Google’s cached observation on separate timestamps.",
  "diagram": [
    "Save old and new revisions",
    "Fetch public robots.txt",
    "Request or await refresh",
    "Compare observed versions"
  ],
  "draft_hash": "64a264abcc12f8c299700191348d3f87d27aa2376d079598128ba02101a026ed",
  "evidence": {
    "observed_at": "2026-11-03T03:30:16.249215+00:00",
    "period": {
      "end": "2026-11-03T03:30:16.249215+00:00",
      "start": "2026-11-03T03:30:16.249215+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": "sequence",
  "figure_notes": [
    "Keep fingerprints and timestamps for both file versions.",
    "Verify that the intended revision is publicly served.",
    "A recrawl request is not a completed cache refresh.",
    "Leave Google-side confirmation pending until evidence is available."
  ],
  "figure_title": "Robots changes: distinguish deployment from Google refresh",
  "group": "Crawl access and indexing",
  "human_review_claim": false,
  "intent": "robots-update-cache-verification",
  "interpretation": "Uploading a file, retrieving its public response and observing Google’s cached version are separate events. Google documents periodic refresh of its robots cache and a Search Console recrawl request. That does not justify inventing a confirmation timestamp immediately after deployment. Keep the old and new file fingerprints so a later observation can be matched to the intended revision.",
  "keyword_volume": "Not obtained",
  "limits": "Google describes a normal cache-refresh cadence, not an unconditional deadline under every failure condition. A recrawl request does not itself confirm a changed crawl or indexing outcome.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/robots-update-cache-verification/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "An updated robots file is publicly visible while Google still reports an older version.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T10:45:14.967829+00:00",
  "reader": "Site owners and analysts investigating an updated robots file is publicly visible while Google still reports an older version.",
  "related": [
    "robots-specific-rule-precedence"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/robots-specific-rule-precedence/",
      "title": "Google robots rules: diagnose group and path precedence"
    }
  ],
  "research_document_ids": [
    "4298e43259a033000f409ad832a6fc61"
  ],
  "slug": "robots-update-cache-verification",
  "source_signature": "933bbd2830e7331681359cf6f444d0418c8cca018f14968ed091ec815219b8b4",
  "sources": [
    {
      "hash": "01fdf71d7b1e1315c9fef82316f79e1dbfa4edb4fb8180f33dc13d717ca6d343",
      "locator": "Refresh Google's robots.txt cache / b9; Upload your robots.txt file / b8",
      "observed_at": "2026-11-03T03:30:16.249215+00:00",
      "title": "Update your robots.txt file",
      "url": "https://developers.google.com/crawling/docs/robots-txt/submit-updated-robots-txt"
    }
  ],
  "sources_required": [],
  "steps": [
    "Save the previous response and the proposed revision with hashes. Confirm that the intended file belongs to the correct host and root robots.txt location.",
    "After deployment, fetch the public URL anonymously and compare the body with the proposed revision. Record redirects or non-success responses as separate problems.",
    "Inspect the Search Console robots report when available. If a faster refresh is needed, use its recrawl request and record that request separately from a completed refresh.",
    "Revisit the report and compare the observed version with the public response. Escalate a persistent discrepancy with the exact URL, timestamps and saved bodies."
  ],
  "title": "Robots changes: distinguish deployment from Google refresh",
  "worked_example": "Hypothetical change log: an editor saves revision A at 09:00 and retrieves revision B from the public URL at 09:12 after correcting a deployment mistake. The local save time cannot establish when B became public. If Search Console still shows A, record the mismatch and observation time rather than declaring the change failed permanently."
}