# Finding 046: Gemini temporary chat did not fetch the hidden structured-data conflict fixture

## Date

2026-06-30

## Status

Published

## Summary

Gemini was run against p21, `manual-client-gemini-20260625-001-p21`, in a
fresh Gemini native Temporary Chat. The exact public target URL was reachable
before prompt submission and contained the expected visible code
`VISIBLE-PLUM-47`.

Gemini returned `fetched:false`, `pages_opened:0`, and said the target URL
could not be accessed or retrieved by the current client setup. The bounded
origin review found no matching direct-origin event for the exact attempt id,
`/lab/reading/hidden-structured-data-conflict`, or `/robots.txt` during the
prompt window.

## What does this mean?

For site owners and researchers, this run shows that making metadata and JSON-LD signals available in a public page does not guarantee that a Gemini chat will retrieve or inspect them. The practical result is a no-retrieval outcome: the page may be reachable to ordinary tools, but the assistant surface can still return no page content and leave no matching origin request.

## Method

- Browser task:
  `research/manual-client-runs/browser-tasks/manual-client-gemini-20260625-001-p21.browser-task.json`
- Prompt packet:
  `research/manual-client-runs/manual-client-gemini-20260625-001.prompts.json`
- Answer artifact:
  `research/manual-client-runs/manual-client-gemini-20260625-001.answers.json`
- Response file:
  `research/manual-client-runs/browser-tasks/responses/manual-client-gemini-20260625-001-p21.response.json`

Before submitting the prompt, the exact target URL was checked with `curl`.
The response contained `VISIBLE-PLUM-47`, `META-AMBER-16`, and
`SCHEMA-INDIGO-82`.

Gemini was opened at `https://gemini.google.com/app` in the OpenClaw-controlled
Chrome profile. The UI showed the `kai bot` Google account, Pro tier, a fresh
compose box, and model selector `Flash`. The native `Temporary chat` control
was enabled before prompt submission, and Gemini showed the Temporary Chat
banner plus the temporary-chat retention notice. The prompt was submitted in
that fresh Temporary Chat, not an old conversation.

Direct-origin review checked `data/events.json` for the exact attempt id, the
fixture path, and `/robots.txt` during the bounded prompt window.

## Result

| Field | Value |
|---|---|
| Attempt ID | manual-client-gemini-20260625-001-p21 |
| Client | Gemini (gemini-web) |
| Visible model/context | Flash, Pro, native Temporary Chat |
| Source prompt | reading-hidden-structured-data-conflict |
| Fetched | false |
| Pages opened | 0 |
| Direct-origin events | 0 inside prompt window |
| Raw event ids | none |
| Bounded window | 2026-06-30T21:16:01Z - 2026-06-30T21:16:23Z |
| Confirmed hit from prompt | false |
| Confirmation status | registered_no_hit |

## Raw response

```json
{
  "attempt_id": "manual-client-gemini-20260625-001-p21",
  "source_prompt_id": "reading-hidden-structured-data-conflict",
  "prompt_code": "manual-client-gemini-20260625-001-p21",
  "ai_system": "Gemini",
  "fetched": false,
  "pages_opened": 0,
  "answer": "The target URL could not be accessed or retrieved by the current client setup, resulting in no page content or underlying source code being available for analysis.",
  "evidence_quote": "",
  "limitations": "The web search/retrieval tool returned an empty result for the specific URL, preventing any inspection of the visible page code, meta descriptions, or JSON-LD data.",
  "confidence": "high"
}
```

## Origin evidence

```json
{
  "timestampWindow": {
    "startedAt": "2026-06-30T21:16:01Z",
    "endedAt": "2026-06-30T21:16:23Z"
  },
  "sourcePromptId": "reading-hidden-structured-data-conflict",
  "promptCode": "manual-client-gemini-20260625-001-p21",
  "confirmedHitFromPrompt": false,
  "rawEventIds": [],
  "events": [],
  "preflightEvents": [
    {
      "id": "mr15abj7-gvc7uxh7",
      "timestamp": "2026-06-30T21:14:38.983Z",
      "eventType": "server_page",
      "path": "/lab/reading/hidden-structured-data-conflict",
      "userAgent": "curl/8.7.1",
      "ip": "::ffff:192.168.1.1"
    }
  ],
  "resourceCounts": {
    "htmlPageRequests": 0,
    "robotsRequests": 0,
    "trackingPixelFetches": 0,
    "nonPixelSubresources": 0,
    "clientCapabilityEvents": 0
  }
}
```

## Interpretation

This run does not prove that Gemini cannot fetch the p21 fixture in general.
It shows that this fresh Temporary Chat attempt returned a no-fetch answer and
left no corresponding origin-side request in the bounded window. Because no
page content was retrieved, this run cannot compare Gemini's treatment of the
visible page code, meta description code, or JSON-LD code.

The p21 fixture is useful because its visible prose does not announce the
hidden structured-data conflict. A future confirmed-hit run from any client
can therefore better isolate whether hidden metadata or JSON-LD was actually
observed instead of inferred from the prompt or URL slug.

## Limitations

- This finding covers one Gemini run, one account/session, one model selector
  state, and one fixture.
- The prompt supplied the exact target URL, so the run tests direct opening,
  not independent discovery.
- Gemini's visible model selector was `Flash`; the backend model or retrieval
  implementation may vary across accounts, regions, or time.
- The recorded start and end times are operator-side bounds around submission
  and final answer observation, not service-internal fetch timestamps.
- Origin review used local `data/events.json` during the bounded window; it
  would not capture a delayed fetch outside that window.

## Publication Thesis Verification

- Thesis: Gemini Temporary Chat did not fetch the p21 hidden structured-data
  conflict fixture during this controlled-browser attempt.
- Source: Fresh Gemini Temporary Chat response, generated response and answer
  artifacts, browser-task artifact, preflight output, and bounded
  `data/events.json` review.
- Method: Exact public target preflight, controlled-browser switch to Gemini
  Temporary Chat, prompt submission in a fresh chat, exact attempt-id review,
  fixture-path review, `/robots.txt` review, and bounded timestamp-window
  correlation.
- Bias: Single run, Pro account, Flash selector, and Gemini's web-tool
  availability may not represent every Gemini product surface, model, or tier.
- Consensus: Consistent with Gemini p20, where the same Temporary Chat flow
  returned a no-fetch answer and the origin logs showed no matching request.
- Invalidation: A raw event from Gemini or Google tooling inside the same
  prompt window, a response artifact from the same attempt showing retrieved
  page content, or a fixture/preflight mismatch would weaken this result.
- Verdict: Supported for this run. Gemini's no-fetch answer, empty raw event
  window, and separate operator preflight align.
- Additional tests suggested: run p21 for ChatGPT, Claude, Perplexity, and
  Copilot/Bing; rerun Gemini p21 later to check whether the no-hit result is
  stable.

## Next steps

- Continue the remaining p21 controlled-browser tasks for ChatGPT, Claude,
  Perplexity, and Copilot/Bing.
- Compare any confirmed p21 hits against p20 to see whether removal of the
  visible conflict cue changes hidden metadata or JSON-LD reporting.