# Finding 068: ChatGPT repeated the second full-URL neutral readability hit ## Date 2026-07-01 ## Status Published ## Summary The ChatGPT p30 same-condition neutral repeat reused the p24-style full correlation URL shape and the same neutral readability task against `/lab/reading/hidden-structured-data-conflict`. ChatGPT returned `fetched:true`, `pages_opened:1`, reported visible token `VISIBLE-PLUM-47`, and described the page as a short reading-test fixture. It did not report the fixture's meta-description token `META-AMBER-16` or JSON-LD token `SCHEMA-INDIGO-82`. Direct-origin raw event `mr2iptim-5hq0zuxp` confirmed the exact target-page hit from `ChatGPT-User/1.0` inside the bounded `2026-07-01T20:15:53.822Z` to `2026-07-01T20:18:44.757Z` prompt window. The operator preflight for the same attempt returned HTTP 200 and contained the visible, meta-description, and JSON-LD fixture markers before prompt submission; it is not counted as prompt-caused evidence. ## What does this mean? For site owners and researchers, this second repeat makes the ChatGPT full-URL neutral-readability behavior look more stable across repeated fresh Temporary Chats. ChatGPT again opened the supplied page and answered from visible page text, even though the served page also contained hidden meta-description and JSON-LD markers. The result should still be read as one account, one mode, and one time window, not as a universal claim about every ChatGPT retrieval path. ## Method - Prepared packet: `research/manual-client-runs/manual-client-chatgpt-neutral-repeat-20260701-001.prompts.json`. - Browser task: `research/manual-client-runs/browser-tasks/manual-client-chatgpt-neutral-repeat-20260701-001-p30.browser-task.json`. - Response artifact: `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-repeat-20260701-001-p30.response.json`. - Logged answer packet: `research/manual-client-runs/manual-client-chatgpt-neutral-repeat-20260701-001.answers.json`. - Prompt code: `manual-client-chatgpt-neutral-repeat-20260701-001-p30`. - Source prompt: `chatgpt-neutral-readable-summary-repeat-b`. The exact target URL was preflighted before submission and returned HTTP 200 with `VISIBLE-PLUM-47`, `META-AMBER-16`, and `SCHEMA-INDIGO-82` present in the served fixture. The prompt was then submitted in a fresh ChatGPT Temporary Chat from the logged-in OpenClaw browser profile. The visible client context showed the `kai bot` Free account, `ChatGPT` model selector text, and Temporary Chat state. The copied answer was logged with `npm run manual-client:log`, then the local event log was queried for the exact attempt id and bounded timestamp window. ## Observed Result ChatGPT returned compact JSON with: - `fetched:true` - `pages_opened:1` - visible token `VISIBLE-PLUM-47` - evidence quote including `The page quality code is VISIBLE-PLUM-47.` - limitation text saying only the directly accessible page view was observed The reviewed direct-origin event was: | Raw event id | Timestamp | Path | User agent | |---|---|---|---| | `mr2iptim-5hq0zuxp` | `2026-07-01T20:18:23.314Z` | `/lab/reading/hidden-structured-data-conflict` | `ChatGPT-User/1.0` | ## Interpretation The p30 result repeats p29 and p24's key control: a full correlation URL plus neutral readability wording can produce a ChatGPT target-page hit. This further supports the Finding 062 interpretation that the p22 no-hit was not caused by long URL shape alone. The copied answer stayed visible-only in its reported tokens. It quoted the visible body token and did not report the meta-description or JSON-LD tokens present in the fixture. Because the answer also described the fixture as distinguishing visible HTML, meta description, and JSON-LD content, the result should be treated as visible-page-context evidence rather than complete hidden source inspection evidence. The p30 raw event came from `ChatGPT-User/1.0` on an IP in the official OpenAI `ChatGPT-User` range cache. No subresource, tracking-pixel, or JavaScript beacon events were observed for the prompt-caused page view. ## Limitations - This is one ChatGPT run in one logged-in account context and one native Temporary Chat. - The test supplied the exact target URL, so it measures direct URL opening, not independent discovery. - p31 remains unrun, so this does not complete the same-condition repeat series. - The answer reports rendered-view limitations. It does not prove that other ChatGPT modes, models, account tiers, or future retrieval paths cannot see metadata or JSON-LD. ## Publication Thesis Verification - Thesis: ChatGPT p30 repeated the full-URL neutral readability condition and produced a confirmed target-page hit with a copied answer that reported only the visible fixture marker. - Source: The p30 browser-task artifact, response artifact, logged answer packet, local raw event `mr2iptim-5hq0zuxp`, and the preflight record for the exact target URL. - Method: Compare copied model JSON with the bounded direct-origin event window, excluding the operator preflight because it occurred before prompt submission. - Bias: Single-run product behavior can change with model routing, account state, client-side search/tool availability, prompt wording, and target URL shape. - Consensus: Consistent with p24, p29, and the p23-p25 visible-only ChatGPT answers summarized in Finding 062. - Invalidation: A corrected event review that removes `mr2iptim-5hq0zuxp` from the prompt window, a response metadata mismatch, fixture-serving error, or p31 showing a stable no-hit pattern would weaken the finding. - Verdict: Supported for this p30 run only. It strengthens the full-URL retrieval repeat evidence, but the three-repeat card remains incomplete until p31 is run and reviewed. - Additional tests suggested: run p31 in a fresh ChatGPT Temporary Chat and then publish a p29-p31 same-condition comparison. ## Next steps - Run `manual-client-chatgpt-neutral-repeat-20260701-001-p31` in a fresh ChatGPT Temporary Chat. - Compare p29-p31 against p24 after all three repeat windows are reviewed.