On Saturday, July 25, a Reddit user showed that typing site:claude.ai/shareinto Google returned strangers’ shared Claude conversations. By Sunday it was trending on X; by Monday the listings were gone and the query returned nothing. Reporters who clicked through in the meantime found, among the exposed pages: resumes with real names and phone numbers, API keys and login credentials, crypto wallet keys, a lawyer’s notes on a potential ethics case, a patient’s medical report, and employee performance reviews.
We run a job site, which means indexing control is not abstract to us; it is a config file we touch every week. So here is the part of this story most coverage got wrong, and the reason it keeps happening to the entire industry.
The mechanism: blocked from crawling, therefore indexable
The obvious diagnosis, a missing noindex tag, is wrong, and the truth is stranger. Claude’s robots.txt has told crawlers to stay out of /share/ since August 2025. That sounds like protection. It is actually the hole: because Google is forbidden from fetchingthose pages, it can never see the noindex instruction they carry. So when someone posts their share link anywhere public (a forum, a group chat that leaks, a blog), Google indexes the bare URL without ever reading the page. The listings even said “No information is available for this page.” The chat text was never in Google’s index; the link was, and the link was enough, because anyone clicking it got the full conversation.
Robots.txt is a do-not-enter sign, not a do-not-mention sign.
The correct pattern is the counterintuitive one: let the crawler in, and let it read “do not index me.”ChatGPT’s share pages do exactly that: explicitly crawlable, carrying a noindex tag, which is why they stay out of results the boring way. PivotHop’s job detail pages use the same pattern for the same reason. It is standard webmaster craft, and in July 2026 one of the most sophisticated AI companies on earth was still learning it in public.
The fourth time, not the first
Every major chatbot has now had a version of this incident, and the ledger is worth reading in order. Google Bard, September 2023: shared chats indexed; Google’s own search liaison conceded “we don’t intend for these shared chats to be indexed” and blocked them within a day. ChatGPT, July 2025: a share-dialog checkbox labeled “make this chat discoverable” put nearly 4,500 conversations into Google before Fast Company noticed; OpenAI’s security chief killed the feature within two days, calling it “a short-lived experiment,” and a researcher later counted roughly 100,000 indexed conversations: NDAs, contract drafts, and a resume-rewrite chat a reporter traced to a real person’s LinkedIn. Grok, August 2025: over 370,000 conversations indexed by Google’s estimate. Claudehas now had it twice: just under 600 conversations in September 2025 by Google’s count, and this weekend’s rerun.
| Product | Crawler access | Page instruction | Net effect |
|---|---|---|---|
| ChatGPT | Allowed | noindex | Correct: Google reads the no |
| Gemini | Allowed | noindex | Correct (fixed after Bard, 2023) |
| Claude | Blocked | noindex, invisible to crawlers | URL-only indexing stays possible |
| Grok | Allowed | index, follow | Shared chats remain indexable today |
Why this is a careers story
Look at what actually leaked, across all four platforms: resumes, performance reviews, staff names and emails in work transcripts, NDA texts, LinkedIn drafts. People do their work in these tools, and the numbers say so: Harmonic Security’s analysis of 22 million enterprise prompts found sensitive data in roughly one prompt in forty, with employee records among the top categories, and a 2025 National Cybersecurity Alliance survey found 43 percent of workers admit sharing sensitive workplace information with AI tools without their employer knowing. A job search runs on exactly this material: the resume with your address on it, the negotiation strategy, the honest assessment of why you left. A share link mints a public URL for all of it.
A share link is a publish button wearing a different label.
What to actually do
Three moves, none dramatic. Check yourself: run site:claude.ai/share, site:chatgpt.com/share, and site:grok.com/share with your name or a phrase you remember, on Google and on Bing, which cleared slower. Revoke at the source: Claude keeps the list under Settings → Privacy → Shared chats; ChatGPT under Settings → Data Controls → Shared Links, and deleting a chat from history does not delete its shared copy; then Google’s Refresh Outdated Content tool for a listing that lingers. Change the mental model: a share link is publishing, so anything you would not put on a public profile — career material above all — should not travel through one. The instrument on this site runs without an account and stores nothing, which is not a flex; after a weekend like that one, it is just the obvious design.
Timeline and leaked-content reporting: 404 Media (Joseph Cox, July 27, 2026), VentureBeat, Futurism, IBTimes UK, Hackread, The Decoder, and the syndicated BeInCrypto report, all July 26–27, 2026; the originating r/ClaudeAI post is dated July 25, 2026, 18:11 UTC. The robots.txt history (the /share/ block appearing August 1–2, 2025) is from Wayback Machine snapshots; the four-product posture table reflects direct header checks on live share pages, July 27, 2026. Precedents: Search Engine Land on Bard (Sept 26, 2023); Fast Company (July 30, 2025), TechCrunch, and OpenAI CISO Dane Stuckey’s statement (Aug 1, 2025) on ChatGPT; 404 Media’s ~100,000-conversation count (Aug 5, 2025); Forbes on Grok’s 370,000+ (Aug 20, 2025) and on Claude’s ~600 with Anthropic’s statement (Sept 8, 2025). Archive figures: Digital Digging / Henk van Ess (Aug 1, 2025), 404 Media (Aug 7, 2025), Obsidian Security’s 143k analysis. Behavior data: Harmonic Security’s 2025 full-year prompt analysis (22.4M prompts); National Cybersecurity Alliance “Oh, Behave!” (Sept 30, 2025). Where outlets disagreed (“hundreds” vs “thousands” indexed in 2026) or Anthropic stayed silent, the text says so rather than picking a number.