# Finding 075: ChatGPT repeated the short-URL neutral readability hit three times ## Date 2026-07-02 ## Status Published ## Summary Findings 072, 073, and 074 compare three ChatGPT short id-only URL repeats against `/lab/reading/hidden-structured-data-conflict`. All three runs used the same neutral readability task family as p24 and p29-p31, the same fixture, a fresh ChatGPT Temporary Chat, and the logged-in OpenClaw browser profile. Each run returned `fetched:true`, `pages_opened:1`, reported visible token `VISIBLE-PLUM-47`, and had a direct-origin `ChatGPT-User/1.0` target-page hit inside its bounded prompt window. The copied answers again stayed narrow. ChatGPT did not report the fixture's meta-description token `META-AMBER-16` or JSON-LD token `SCHEMA-INDIGO-82` in any of the three short-URL answers, even though operator preflight confirmed those served fixture markers before prompt submission. ## What does this mean? For site owners and researchers, this matched short-URL trio shows that ChatGPT repeatedly opened the same neutral readability fixture when the tracking URL used only a simple id parameter. Compared with the earlier full-correlation trio, the practical result is that both URL shapes could produce repeat target hits in this setup, while the copied answers still stayed with visible page text instead of hidden metadata or structured-data markers. Retrieval success and hidden-field visibility need to stay separate in measurement and reporting. ## Method This comparison reviews the published short-URL repeat findings: - p33: Finding 072, `manual-client-chatgpt-neutral-short-repeat-20260702-001-p33`. - p34: Finding 073, `manual-client-chatgpt-neutral-short-repeat-20260702-001-p34`. - p35: Finding 074, `manual-client-chatgpt-neutral-short-repeat-20260702-001-p35`. - Response artifacts: `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-short-repeat-20260702-001-p33.response.json` through `research/manual-client-runs/browser-tasks/responses/manual-client-chatgpt-neutral-short-repeat-20260702-001-p35.response.json`. - Logged answer packet: `research/manual-client-runs/manual-client-chatgpt-neutral-short-repeat-20260702-001.answers.json`. - Prompt packet: `research/manual-client-runs/manual-client-chatgpt-neutral-short-repeat-20260702-001.prompts.json`. Each run preflighted the exact target URL, submitted the prompt in a fresh ChatGPT Temporary Chat, logged the copied answer with `npm run manual-client:log`, and reviewed direct-origin evidence by prompt code, attempt id, raw event ids, and bounded timestamp window. Operator preflight requests are treated as fixture-readiness checks, not prompt-caused AI-client behavior. ## Comparison Matrix | Prompt | ChatGPT answer | Direct-origin evidence | Field implication | |---|---|---|---| | p33 | `fetched:true`, `pages_opened:1`; reported `VISIBLE-PLUM-47`. | Raw event `mr2rhoel-km9938ef` from `ChatGPT-User/1.0`. | Visible-token answer; meta-description and JSON-LD tokens not reported. | | p34 | `fetched:true`, `pages_opened:1`; reported visible page text including `VISIBLE-PLUM-47`. | Raw event `mr2rt7zm-2zhwxm1o` from `ChatGPT-User/1.0`. | Visible-token answer; meta-description and JSON-LD tokens not reported. | | p35 | `fetched:true`, `pages_opened:1`; reported visible readability and purpose text. | Raw event `mr2tebcf-67sgcb24` from `ChatGPT-User/1.0`. | Visible-token answer; meta-description and JSON-LD tokens not reported. | ## Interpretation The p33-p35 set completes the matched short id-only follow-up proposed after Finding 070. It supports the narrower conclusion that this ChatGPT account and Temporary Chat mode repeatedly opened the fixture when the tracking URL used only `?id=`. Compared with p29-p31, both URL shapes produced three confirmed target hits under matched neutral readability wording. That does not prove URL shape never matters, but it does rule out a simple split where full-correlation URLs fetch and short id-only URLs do not, or vice versa, for these two repeat trios. The answer-field conclusion remains separate from the retrieval conclusion. In all six p29-p31 and p33-p35 repeat runs, ChatGPT copied or summarized visible page text and did not report `META-AMBER-16` or `SCHEMA-INDIGO-82`. That supports a visible-answer pattern for these measured runs, not a universal claim about all ChatGPT retrieval components, modes, or future product states. No subresource, tracking-pixel, or JavaScript beacon events were observed for the prompt-caused page views in the short-URL trio. ## Limitations - This comparison covers three ChatGPT short-URL repeats from one logged-in account context, one native Temporary Chat mode, and one fixture. - The prompt supplied the exact target URL, so this measures direct URL opening rather than independent discovery. - The short-URL trio is compared with p29-p31, but both trios still occurred in a narrow time window and may share product-routing state. - The copied answers report what the ChatGPT client exposed in its response; they do not prove what every underlying retrieval component could inspect. - Origin review used bounded prompt windows. Delayed fetches outside those windows would require separate review before changing these conclusions. ## Publication Thesis Verification - Thesis: ChatGPT repeated the short id-only neutral readability target hit three times in p33-p35, and all three copied answers stayed visible-only for marker evidence. - Source: Findings 072, 073, and 074; their response files; the logged answer packet; browser-task artifacts; and direct-origin raw events `mr2rhoel-km9938ef`, `mr2rt7zm-2zhwxm1o`, and `mr2tebcf-67sgcb24`. - Method: Compare copied model answers with exact prompt codes, confirmation statuses, raw event ids, URL shapes, task framing, and bounded timestamp windows, while excluding operator preflight requests from prompt-caused evidence. - Bias: The result is single-client, single-account, and short-window. ChatGPT retrieval behavior may vary by tier, model selector, region, browsing tool state, prompt wording, target URL, and time. - Consensus: Consistent with Finding 070's p29-p31 full-correlation repeat series and with the individual thesis-verification sections for Findings 072, 073, and 074. - Invalidation: A corrected event review that removes any p33-p35 raw event from its prompt window, a response artifact mismatch, a fixture-serving error, or later same-condition repeats showing stable no-hit behavior would weaken the comparison. - Verdict: Supported for this three-run short-URL repeat series. The comparison supports repeated short-URL retrieval plus visible-only copied answers when retrieval succeeded; it does not identify one definitive cause for earlier ChatGPT no-hit behavior. - Additional tests suggested: run a later mixed-order packet that interleaves full-correlation and short id-only URLs to reduce possible time-window and product-routing confounds. ## Next steps - Compare a future mixed-order packet with p29-p31 and p33-p35 if ChatGPT retrieval starts varying again. - Keep future summaries split into retrieval status, origin evidence, and answer-visible field exposure.