Shared Chats Showed Up on Google.

Over the weekend, people found shared Claude chats and Artifacts sitting in ordinary Google search results.

This was not a hack of private accounts. It was the share button.

What showed up in search

On July 25, a Reddit user on r/ClaudeAI posted that a simple Google query, site:claude.ai/share, was returning other people's shared Claude conversations. VentureBeat and TechCrunch both covered what followed. By July 26, people were also finding shared Artifacts, the documents, dashboards, and mini apps you can build inside Claude, through paths like site:claude.ai/public/artifacts.

VentureBeat independently verified that some third-party Claude Artifacts were searchable and open without a login. They could not open the shared chat pages themselves by the time they checked.

TechCrunch, citing Futurism, said material that turned up before the cleanup included a detailed medical report for a real patient, clinical trial results with patient names, documents with the names and phone numbers of primary school-aged children, internal company files, and employee reviews with personal worker information. Gizmodo, citing 404 Media, also pointed to meeting notes, medical billing data, and a vibe-coded AI therapy app among the finds people were talking about.

Fast Company said it saw an Artifact that looked like a medical trial comparison with names, ages, and treatment dates, and another that looked like a database of access codes for Irish apartment buildings. They chose not to republish those links.

I build real projects with this stack every day. That is the kind of stuff people paste into Claude when they trust the product.

How the share feature actually works

Claude chats are private by default. The share feature is something you turn on. You create a public link, and the interface warns that "anyone with the link can view." Anthropic requires that step. It is not on unless you flip it.

A lot of people read "anyone with the link" the way they read an unlisted Google Doc or an unlisted YouTube video: send the URL to a friend, and strangers are not supposed to find it by searching. What they got, for a stretch of the weekend, was closer to a public webpage.

Anthropic spokeswoman Amie Rotherham told TechCrunch the company does not hand chat directories or sitemaps to Google. The share links are "not guessable or discoverable unless people choose to share them themselves." When you share a conversation, she said, you are making that content publicly accessible, and like other public web content it may get archived by third-party services. Anthropic also told outlets that a link only shows up in search if it has been posted somewhere crawlers can see, like a forum or social post, and that a link sent privately should stay out of search.

Google spokesperson Ned Adriance told TechCrunch that search engines do not decide which pages are public, that these pages were indexed across many search engines, and that Google gives site owners controls for crawling and indexing and respects those directives.

The robots.txt / noindex mess

Search Engine Journal checked Claude's crawl rules on July 27 and found a conflict that Google has been warning about for years.

Claude's robots.txt blocks /share/*. Live share URLs were also returning an x-robots-tag: none header, which Google treats like noindex plus nofollow. The problem is the pairing. Google's own guidance says a noindex only works if the crawler is allowed to open the page and read it. If robots.txt blocks the crawl, Google can still list the URL when it finds the link somewhere else on the web, because it never gets far enough to see the noindex instruction.

SEJ also noted that the /public/artifacts/ path was not listed in robots.txt at the time of their check. Independent IT consultant Daniel J. Glover had flagged the same robots.txt / noindex conflict a day earlier.

So the plain-English version is: blocking a crawler is not the same thing as keeping a page out of search. Anthropic's share pages were public URLs. Once those URLs showed up on places Google already crawls, search could pick them up.

What got cleaned up, and what still matters

By Sunday morning, VentureBeat said many of the original Google results for shared Claude chats had disappeared or gotten much harder to find. As of Monday afternoon, July 27, TechCrunch ran the same site:claude.ai/share test and got no results.

That does not mean every shared link is gone from the open web. Unsharing a chat kills the live link for new visitors. Getting a URL out of a search index is a separate process, and as Search Engine Journal pointed out, a regular Claude user cannot submit the removal request for Anthropic's domain. Unsharing a chat and unpublishing an Artifact from that chat are also separate actions.

This is also not Claude's first time around this block. TechCrunch noted that Forbes reported a similar Claude indexing issue last year, when Google estimated it had indexed just under 600 conversations before they disappeared from results. ChatGPT went through a shared-chat indexing mess too. Fast Company covered OpenAI's version in July 2025. Google's own Bard had shared transcripts show up in search back in 2023.

The checklist for anyone who has ever hit share

I pay $200 a month for this product. I use Claude for real work, not toy prompts. TechCrunch, Search Engine Journal, and Gizmodo all pointed people to the same place: Settings, then Privacy, then Shared Chats (and the matching Shared Artifacts controls). If you have ever created a public link, that screen is the list of what is still live.

Unsharing stops new visitors from opening the link. It does not automatically wipe every copy that already got indexed or archived. That part sits with Anthropic and the search engines.

The factual rule the coverage keeps landing on is simple. A public share link is a public webpage from the moment it exists. "Anyone with the link" includes search engines if the URL lands on a crawlable page and the site is not set up to keep it out of the index.

I am still on Claude. I still pay the $200. I am just not going to treat the share button like a private handoff anymore.