How to Stop Claude Chats from Being Shared Publicly

How to stop Claude chats from being shared publicly

Last weekend, Reddit users showed that searching site:claude.ai/share in Google surfaced hundreds of shared Claude conversations. Before the search queries stopped returning results by Monday, Futurism as cited by TechCrunch found a real patient's medical report with their name attached, clinical trial data, children's names and phone numbers, and company documents marked for internal use only. No accounts were breached. The exposure affected only conversations users had already made shareable via a link, which means how to stop Claude chats from being shared publicly is something you can fix yourself, right now, in your account settings.

TechRepublic confirmed that individual links already posted publicly remained live and reachable after the search results disappeared. Revoking them is your job, not Anthropic's.

This guide walks you through three things: auditing and revoking your shared chat links, checking your Claude Artifacts separately, and escalating correctly if the exposed content included information about students, patients, or colleagues.

What you need before you start

A Claude account and access to claude.ai in a desktop browser. The steps below reflect the web interface as of this week. Mobile app navigation may differ open Settings and look for Privacy controls if the path doesn't match.

Step 1: Audit and revoke your shared chat links in Claude settings

1. Go to Settings > Privacy > Shared Chats. Log in to claude.ai. Open your profile or account menu in the upper right corner and select Settings. Navigate to Privacy, then Shared Chats. Anthropic directs users to this path to review active links (TechRepublic). This page lists every conversation for which you've generated a public share link.

2. Review each entry with one question: Has this link been posted anywhere beyond a direct private message a forum, social media, a team channel, a blog? If yes, or if you're unsure, revoke it. If the content included health information, credentials, student data, or internal documents, revoke it regardless.

3. Revoke links you no longer need. Select the revoke or disable option next to each link you want to close. Once revoked, the URL stops working. Anyone who visits it afterward should no longer be able to view the conversation.

Gotcha revoking cuts the live link but doesn't erase cached copies. If a search engine indexed the page before you revoked it, a cached version may still appear temporarily in search results. If an archiving service captured the page, that copy may persist independently. Revoking is still the essential first step; follow the cache cleanup step below after you've finished.

4. Check whether your links still appear in Google. Search site:claude.ai/share in Google and scan the results. If you recognize any of your own conversations, note the exact URLs and submit each one to Google's Remove Outdated Content tool to request cache removal. These pages were reported as indexed across multiple search engines, not Google alone (TechRepublic). If the conversation contained particularly sensitive content, run the same search on Bing and review Bing's current content-removal options.

Step 2: How to prevent Claude chats from being indexed via Artifacts

Artifacts use a different URL path from shared chats, so they need a separate check. VentureBeat independently verified that shared Artifacts interactive apps, dashboards, documents, and other outputs Claude generates alongside conversations were searchable and accessible without any authentication.

5. Search for your Artifacts in Google. Run site:claude.ai/public/artifacts in Google and check the results. VentureBeat also found results under site:claude.ai/public/artifactslaunch, so run both queries. If anything looks familiar, note the URLs and submit them to the Remove Outdated Content tool as above.

6. Review Artifact sharing controls in Claude. Open Claude and locate your Artifacts panel. Sharing controls for Artifacts may differ from the conversation share path under Settings. If you can't find a consolidated revocation list:

• Revoke any visible sharing controls you can locate within the Artifacts panel
• Document the URLs of any Artifacts you found in your Google search
• Check Claude's Help Center for current guidance on bulk Artifact revocation
• Contact Anthropic support directly if no revocation list appears

VentureBeat reported that Anthropic appeared to have begun limiting visibility of at least some shared pages in Google Search, though cached copies, archived pages, and indexing by other search engines may persist. Verify the current state of these controls in Claude's Help Center before assuming the platform has fully resolved the underlying issue.

Step 3: If sensitive information was exposed, escalate appropriately

Revoking a link and clearing a cached page addresses your own exposure. If the shared content included information about other people patients, students, employees, clients those people and the institutions responsible for their data need to know.

Students and educators: If a shared conversation contained student names, assignment details, grades, school records, or contact information, notify your school's technology coordinator or privacy officer before taking any other steps. State privacy laws frequently require schools to publicly share information on what student data they share and who receives it, as the Future of Privacy Forum noted in guidance published in fall 2024. This matters especially for data involving minors. If you used a school-provided Claude account or entered school records into the tool, report the issue before deleting your own evidence of the shared link. Your school's tech or legal office has final authority on what steps are required.

Employees and workplace users: If a shared conversation included internal company documents, proprietary information, API keys, login credentials, or employee data, notify your IT or security team immediately. Don't wait to see whether the cached link disappears on its own your organization may have disclosure or incident-response obligations that move faster than cache removal allows.

Healthcare and clinical contexts: Patient names, medical records, and clinical trial data appeared in the indexed conversations, as TechCrunch reported last weekend. If you shared a conversation containing any patient information, contact your organization's privacy officer or compliance department. The appropriate next steps depend on the regulations that apply to your specific role and institution. This guide cannot substitute for that guidance.

Parents: If you shared a conversation that included your child's name, school, contact information, or any other identifying details, revoke the link immediately, submit a cache removal request, and notify the relevant school or organization if the information relates to the child's enrollment or records.

Why shared Claude links ended up in search results

Claude's interface warns "anyone with the link can view" language that most users read the way they'd read a Google Docs share prompt: an unlisted document reachable only by people you send it to. TechCrunch made the same comparison directly: Google Docs link-sharing does not produce publicly indexed pages. Claude's did.

Any page accessible without authentication can be indexed by search engines unless the site explicitly prevents it not just through robots.txt, but through a noindex tag on the page itself. According to TechRepublic, Anthropic had robots.txt rules in place since at least September 2025, but WIRED reviewed exposed Claude pages and found no noindex tag present. That gap meant once a share link appeared on a public forum or social post, search engines could index it. Google spokesperson Ned Adriance placed the responsibility squarely on Anthropic, telling TechCrunch that site owners control whether their pages are crawled or indexed.

This same failure has surfaced before. Last year, Google estimated it had indexed just under 600 Claude conversations in a nearly identical incident. The same basic problem has now hit multiple major chatbots: roughly 100,000 ChatGPT conversations turned up in Google search last year, and Elon Musk's Grok has been caught in similar territory, according to TechRepublic.

Until Anthropic confirms it has addressed both the robots.txt and noindex gap, treat any Claude share link you post publicly as a public webpage, not an unlisted document.

Before creating any Claude share link, run through this checklist:

• Remove names and other identifying details from the conversation
• Remove credentials, API keys, and any internal documents
• Avoid posting the link on public websites, forums, or social media
• Send links only through direct messages to specific recipients
• Revoke the link after the intended recipient has seen the conversation

Anthropic confirmed to TechCrunch that a link sent privately to one person stays out of search. A link posted to a crawlable public location may eventually be indexed. That distinction is the whole issue.

Verify and confirm

The interface paths in this guide reflect claude.ai as of today, July 29, 2026. Anthropic may update privacy settings, move controls, or add new revocation tools following the incident.

• Confirm the Settings > Privacy > Shared Chats path is still accurate in your own account
• Check Claude's Help Center for updated Artifacts sharing controls and any new revocation tools added since this week
• If you're a student, educator, parent, or employee and sensitive data about others was involved, contact the relevant school privacy office, IT department, or compliance team before assuming cache removal is sufficient

If you've ever used Claude's Share button, run this audit today, then save the Help Center page so you can recheck the process if Anthropic changes the interface.