# Finding 072: ChatGPT opened the first short-URL neutral readability repeat ## Date 2026-07-02 ## Status Published ## Summary The ChatGPT p33 neutral short-URL repeat reused the p24/p29-p31 neutral readability wording against `/lab/reading/hidden-structured-data-conflict`, but changed the target URL to short id-only correlation. ChatGPT returned `fetched:true`, `pages_opened:1`, reported visible token `VISIBLE-PLUM-47`, and described the page as a readable fixture with a heading, short question, brief fixture text, and control links. It did not report the fixture's meta-description token `META-AMBER-16` or JSON-LD token `SCHEMA-INDIGO-82`. Direct-origin raw event `mr2rhoel-km9938ef` confirmed the exact target-page hit from `ChatGPT-User/1.0` inside the bounded `2026-07-02T00:21:55.104Z` to `2026-07-02T00:24:41.600Z` prompt window. The operator preflight event `mr2rcnx5-ug49plxo` returned HTTP 200 before prompt submission and is not counted as prompt-caused evidence. ## What does this mean? For site owners and researchers, this run shows that shortening the correlation URL did not prevent ChatGPT from opening the same neutral readability fixture. The copied answer again used visible page text and did not expose hidden metadata or structured-data marker values, so URL shape and content-field visibility remain separate questions. A short URL can still fetch successfully, but the answer may stay grounded in what the assistant's page view exposes. ## Method - Prepared packet: `research/manual-client-runs/manual-client-chatgpt-neutral-short-repeat-20260702-001.prompts.json`. - Browser task: `research/manual-client-runs/browser-tasks/manual-client-chatgpt-neutral-short-repeat-20260702-001-p33.browser-task.json`. - Response artifact: `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-short-repeat-20260702-001-p33.response.json`. - Logged answer packet: `research/manual-client-runs/manual-client-chatgpt-neutral-short-repeat-20260702-001.answers.json`. - Prompt code: `manual-client-chatgpt-neutral-short-repeat-20260702-001-p33`. - Source prompt: `chatgpt-neutral-readable-summary-short-repeat-a`. The exact target URL was preflighted before submission and returned HTTP 200 with `VISIBLE-PLUM-47` 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 `/api/hits` and the local event log were 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 page view was used The reviewed direct-origin event was: | Raw event id | Timestamp | Path | User agent | |---|---|---|---| | `mr2rhoel-km9938ef` | `2026-07-02T00:23:59.989Z` | `/lab/reading/hidden-structured-data-conflict` | `ChatGPT-User/1.0` | ## Interpretation The p33 result is the first matched short-URL repeat after the p29-p31 full-correlation repeat series. It keeps the neutral readability wording and fixture constant while changing the target URL shape to `?id=`. The confirmed target hit means short id-only correlation remains runnable for ChatGPT in this measured account and mode. The copied answer stayed visible-only in marker evidence. It quoted the visible body token and did not report the meta-description or JSON-LD tokens present in the fixture. Because the answer repeated the page's visible question about code locations, this should be treated as visible-page-context evidence, not proof of complete hidden source inspection. The p33 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. - p34 and p35 remain unrun, so this does not complete the matched short-URL repeat series. - The answer reports accessible page-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 p33 opened the short id-only neutral readability target and produced a confirmed target-page hit with a copied answer that reported the visible fixture marker. - Source: The p33 browser-task artifact, response artifact, logged answer packet, `/api/hits` raw event `mr2rhoel-km9938ef`, and the preflight record for the exact target URL. - Method: Compare copied model JSON with the bounded direct-origin event window, excluding the preflight event 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 the p23 and p25 short-URL confirmed hits and the p29-p31 full-correlation repeat series, all of which produced visible-token ChatGPT answers after confirmed target-page hits. - Invalidation: A corrected event review that removes `mr2rhoel-km9938ef` from the prompt window, a response metadata mismatch, fixture-serving error, or p34-p35 repeats showing stable no-hit behavior would weaken the finding. - Verdict: Supported for this p33 run only. It starts, but does not complete, the matched short-URL repeat series. - Additional tests suggested: run p34 and p35 in fresh ChatGPT Temporary Chats and then compare p33-p35 against the p29-p31 full-correlation repeat series. ## Next steps - Run `manual-client-chatgpt-neutral-short-repeat-20260702-001-p34` and p35 in fresh ChatGPT Temporary Chats.