What happened
On July 27, 2026, TechCrunch and WIRED reported that shared Claude chats and Artifacts were discoverable through Google and Bing search results.
Claude's share feature creates a public snapshot at an anyone-with-link URL. Anthropic told TechCrunch these links appear in search only when posted somewhere web crawlers can reach, such as a public forum. Anthropic said it does not submit shared-chat directories or sitemaps to search engines, and that privately sent links stay out of search results.
WIRED found Anthropic's robots.txt disallowed direct crawling of shared chats, but sampled pages lacked a noindex tag. Those two controls work differently. robots.txt asks crawlers not to visit a URL, but a search engine can still index that URL if it appears as a link on another page, learning the URL exists without visiting the share link itself. A noindex tag tells the engine not to show the page in results, but only when the crawler can fetch and read the page. When robots.txt blocks crawling, the noindex directive goes unseen.
ZDNET noted that Claude chats are private by default. The issue concerned only snapshots created when a user intentionally activated a share link, not ordinary private conversations.
TechCrunch said Google results were gone during its Monday afternoon check. WIRED reported Bing still showed results at its review time.
Why it matters
Many users treat a share link as something only a specific recipient will see. The reports clarify that if that URL is posted where a crawler can find it, a search engine may index it. This reflects how public URLs and search engines generally work.
No confirmed count of affected chats or users was published. Anthropic did not describe this as a breach, hack, or database leak, and there is no report of Anthropic publishing a directory of share links. WIRED's finding that sampled pages lacked a noindex tag while robots.txt was present highlights a configuration gap in how the share feature was set up.
Disabling a share link removes access through Claude, but copies already indexed, cached, or archived may persist independently.
What to do next
- Open Settings, go to Privacy, then Shared Chats. Review every active link and disable any you no longer need, especially older ones. ZDNET and TechCrunch both recommend this step.
- If you keep a link active, anyone who finds the URL can read the contents.
- Assume any snapshot you shared could have been copied or archived before you disabled it. Disabling stops new access through Claude but does not erase third-party copies.
- Do not paste API keys, passwords, customer data, personal identification, medical records, or legal records into any page you might share.
- If you shared a conversation containing sensitive data, rotate or revoke exposed credentials immediately and inform anyone whose data was included.
This briefing summarizes TechCrunch, WIRED, and ZDNET reporting from July 27, 2026. It covers intentionally created public share-link snapshots and Artifacts that appeared in search results. Ordinary private Claude conversations and account history were not reported as affected. No confirmed count was published. These reports do not establish a hack, database leak, or unauthorized access to private chats. Search results and cached copies may have changed since reporting.