# Finding 069: ChatGPT completed the third full-URL neutral readability repeat ## Date 2026-07-01 ## Status Published ## Summary The ChatGPT p31 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 `mr2kwg6x-dpw37d24` confirmed the exact target-page hit from `ChatGPT-User/1.0` inside the bounded `2026-07-01T21:17:01.444Z` to `2026-07-01T21:19:43.624Z` 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 adds confidence that a ChatGPT page-reading path can repeatedly use visible page copy without exposing hidden metadata or structured data in its answer. That distinction matters because optimizing visible content and optimizing machine-readable page fields are not always the same thing. The result is useful evidence for this measured setup, but not a promise that every ChatGPT surface will treat hidden page signals the same way. ## 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-p31.browser-task.json`. - Response artifact: `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-repeat-20260701-001-p31.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-p31`. - Source prompt: `chatgpt-neutral-readable-summary-repeat-c`. 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 accessible visible page view was used The reviewed direct-origin event was: | Raw event id | Timestamp | Path | User agent | |---|---|---|---| | `mr2kwg6x-dpw37d24` | `2026-07-01T21:19:31.867Z` | `/lab/reading/hidden-structured-data-conflict` | `ChatGPT-User/1.0` | ## Interpretation The p31 result repeats p29 and p30's key control: the same full correlation URL plus the same neutral readability wording produced another ChatGPT target-page hit. This completes the planned p29-p31 repeat packet and strengthens the Finding 062 interpretation that the earlier 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 p31 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. - 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. - A separate comparison is still needed to summarize p29-p31 as a repeat series rather than three isolated findings. ## Publication Thesis Verification - Thesis: ChatGPT p31 completed the third full-URL neutral readability repeat and produced a confirmed target-page hit with a copied answer that reported only the visible fixture marker. - Source: The p31 browser-task artifact, response artifact, logged answer packet, local raw event `mr2kwg6x-dpw37d24`, 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, p30, and the p23-p25 visible-only ChatGPT answers summarized in Finding 062. - Invalidation: A corrected event review that removes `mr2kwg6x-dpw37d24` from the prompt window, a response metadata mismatch, fixture-serving error, or a later same-condition repeat showing stable no-hit behavior would weaken the finding. - Verdict: Supported for this p31 run only. It completes the p29-p31 same-condition repeat packet and supports publishing a scoped repeat-series comparison. - Additional tests suggested: publish a p29-p31 comparison and then vary one factor at a time, such as URL length, neutral wording, or native private mode state. ## Next steps - Compare p29-p31 against p24 in a scoped same-condition repeat finding.