If you have ever tapped Share on a Claude conversation, that chat may still be readable by anyone holding the link — even now that Google has stopped showing it. Over the weekend of 25–26 July, users discovered that Claude shared chats and Artifacts were turning up in Google and Bing search results, and while the search listings have since disappeared, deindexing is not the same thing as revoking access. The only way to actually close a shared link is to unshare the chat yourself.
What happened with Claude shared chats
A Reddit user flagged over the weekend that a simple site-scoped Google query against claude.ai/share returned pages of real conversations. TechCrunch, which reported the issue on Monday, 27 July, described what was visible: medical records, clinical trial results, children’s names and phone numbers, internal company documents and employee reviews. None of those people had published anything deliberately. They had used a Share button.
By Monday afternoon the same searches returned nothing, indicating Anthropic had changed its configuration. Anthropic’s own statement, given to TechCrunch, put the emphasis elsewhere:
“We give people control over sharing their Claude conversations publicly, and in keeping with our privacy principles, we do not share chat directories or sitemaps with search engines like Google. These shareable links are not guessable or discoverable unless people choose to share them themselves.”
That is technically accurate and beside the point. A share link is not guessable, but it is also not access-controlled — one paste into a public forum, a Discord server, a support ticket or a social post and a crawler can find it. Claude’s own help article describes what sharing does in terms of the conversation snapshot; it does not tell you the resulting page is a plain public web page that search engines may index. Users who sent a link to one colleague were not choosing to publish. Framing that as user choice shifts a design failure onto the people it affected.
Why robots.txt did not stop it
Reports differ on exactly which headers were live on the share pages that weekend, so treat the specifics with caution. The mechanism, though, is well documented by Google and worth understanding, because plenty of sites get it wrong. Checking claude.ai’s robots.txt today shows Disallow: /share/* under the wildcard user-agent. A disallow rule tells a crawler not to fetch the page — which means the crawler never reads any noindex instruction inside it. If Google finds that URL linked from somewhere else on the web, it can index the URL anyway, because a block on crawling is not a block on indexing. Disallow and noindex do different jobs, and using the first while relying on the second is a common and consequential mistake.
How to check and unshare your Claude chats
These steps come from Anthropic’s own help documentation. Do this even if you only ever shared one chat.
- Open Claude on the web and click your profile in the bottom-left corner, then click Settings.
- Go to Privacy and click Manage next to Shared chats. This opens a list of every chat you have shared, with its title, the date it was shared and the link.
- Review the list properly. Anything containing personal details, client information, credentials or code you would not post publicly needs to go.
- To unshare an individual conversation, open the chat, click the Share menu, click the visibility dropdown, and change it from Public to Private. That disables the direct link.
One clarification worth noting: Anthropic’s documentation states that users on Team and Enterprise plans can only share chats with other members of the same organisation, not publicly. The public-link behaviour applies to free, Pro and Max accounts.
What to take from this
This is the second time in as many years that an AI assistant’s share feature has ended up publishing user conversations to Google. OpenAI went through its own version in 2025, when shared ChatGPT chats turned up in search results; OpenAI eventually pulled the discoverability option, calling it a short-lived experiment that “introduced too many opportunities for folks to accidentally share things they didn’t intend to.” The pattern is the lesson: in these products, “share” frequently means “publish to a public URL,” not “send privately to one person.” Until vendors label that clearly in the share dialog itself, assume any share link is a public web page, and keep anything sensitive out of a conversation you intend to share at all. If you are tightening up your browsing privacy more generally, our look at what Firefox 153’s built-in Containers do and do not isolate is a useful companion.
Sources: TechCrunch, Anthropic Help Center, Search Engine Journal
