Een privacykwetsbaarheid kwam aan het licht bij Anthropic’s Claude: privégesprekken en "Artifacts" werden doorzoekbaar op Google. Het incident zet

Anthropic maintains that it does not publish chat directories or sitemaps for search engines. A company spokesperson explained that shared links appear in search results only after a user posts the URL on an external, crawlable platform, and emphasized that the URLs are "not guessable." Once a link is deliberately shared online, the company cannot control third-party archiving.

Google’s Stance

Google reiterated that it does not decide what content is public; it indexes what it can find unless a site explicitly blocks crawling. The company said it respects directives such as robots.txt or meta tags that request exclusion. Preliminary tests after the incident suggest the exposed URLs have been removed from Google’s index, though Google did not confirm a permanent fix.

Why This Matters for AI Users

The episode highlights a broader risk as large language models move from personal assistants into enterprise workflows. A "shareable link" is a convenience mechanism that any crawler can harvest. For organizations handling regulated data—health records, employee evaluations, proprietary code—the assumption that a link is safe because it is "only shared" can lead to costly leaks.

Counter-Argument: Platform Limits

Anthropic argues that responsibility lies with users who publish the link. The platform warns that anyone with the URL can view the content and does not expose URLs in a public directory. Google counters that it cannot police every private link that surfaces; its role is to honor site owners’ requests to stay out of search results.

Both positions are technically accurate, yet they leave a gap: the user experience does not make the indexing risk obvious, and the platform does not automatically apply "no-index" directives to shared pages. The burden of preventing accidental public exposure therefore falls on users who may not realize how easily a link can be discovered through a simple search query.

What to Watch Next

Practical Steps for Users

  • Audit Active Links: Open Claude’s settings, navigate to the privacy section for shared chats, and revoke any URLs you no longer need.
  • Treat Every Share Link as Public: Assume that once a link is posted anywhere online, it can be indexed unless explicitly blocked.
  • Enterprise Controls: Deploy monitoring tools that flag the creation of share links containing keywords like "PII," "confidential," or "internal," and enforce approval workflows before such links leave the corporate network.

The Claude incident reminds us that the convenience of instant sharing can become a liability when the web treats those links as ordinary pages. Until platforms automatically protect shared URLs, users must remain vigilant.