- How to See If Your Claude Chats Were Indexed by Google
- What happened with Claude shared chats and Google indexing
- Step 1: Audit your shared links inside your Claude account (do this first)
- Step 2: How to see if your Claude chats were indexed by Google or Brave
- Step 3: What revoking a link fixes, and what it doesn't
- How to avoid this going forward
- What to do now
How to See If Your Claude Chats Were Indexed by Google
If you've used Claude's Share feature, the fastest way to see if your Claude chats were indexed by Google is to check your Shared Chats list in your account settings first, then run a site:claude.ai/share search in both Google and Brave. This guide walks through both steps, explains what to do if you find exposed content, and covers what revocation actually fixes.
Before starting, you'll need:
- Access to your Claude account at claude.ai
- A few minutes to review your shared links and run search checks
What happened with Claude shared chats and Google indexing
This past weekend, Reddit user -void1 posted to r/ClaudeAI demonstrating that the query site:claude.ai/share surfaced numerous publicly accessible Claude conversations. The post spread quickly across Reddit and X, drawing thousands of upvotes and comments, per VentureBeat (this week). VentureBeat independently verified that Claude Artifacts were searchable and accessible without any login.
No private Claude conversations were breached or leaked, per IBTimes (yesterday). Claude conversations are private by default. They become public only when a user clicks Share and generates a public link, at which point Claude creates a web page containing a snapshot of that conversation. Anyone with the link can view it.
The indexing problem traces back to how those links become discoverable. Anthropic's robots.txt file instructs crawlers not to index shared conversations, but reports claimed the shared pages may also have lacked noindex tags that would reinforce that instruction. Once a share link is posted anywhere a crawler can reach, such as a forum, a blog, or social media, it can get picked up regardless of how long or random the URL looks. Indexing didn't create access to these conversations; it made already-public links much easier for strangers to find, per Moneycontrol (yesterday).
Users who shared résumés, school assignments, research notes, or business documents via the Share button may have had that content discoverable by anyone running the right search. Reported examples included API keys, cryptocurrency wallet details, internal company documents, and personal data, per IBTimes (yesterday), based on user reports and screenshots. Artifacts carry particular risk: unlike a chat transcript, an Artifact can be a complete interactive application, dashboard, or formatted document, making exposed Artifacts more immediately usable by whoever finds them.
By Sunday, many Google results had begun disappearing, suggesting de-indexing was underway per VentureBeat (this week). Developer Ziwen Xu reported finding Claude conversations through Brave Search even after Google results dropped off, per IBTimes (yesterday). A blank Google result is not clearance. A live public URL continues to work for anyone who has it saved, which is why revoking your own links is the step that matters most.
Step 1: Audit your shared links inside your Claude account (do this first)
Search results are incomplete and change quickly. Your account settings hold the only complete record of every public link you've created. Start here.
- Log in to your Claude account at claude.ai.
- Click your profile or account icon to open Settings.
- Select Privacy. (Menu labels can change, so look for a Shared Chats or similar section if Privacy doesn't appear.)
- Select Shared Chats.
- Review every link listed. For each one, ask whether the conversation contains any of the following:
- API keys, passwords, or credentials
- Cryptocurrency wallet information
- Personal identifiers such as name, address, phone number, or account numbers
- Documents you would not post on a public website: résumés, school assignments, research notes, business strategy, client data, meeting notes
- Legal questions, medical information, or financial details
- Anything you typed or pasted in from another document or system
Decision rule: If a conversation is old, work-related, contains pasted content you wouldn't email to a stranger, or has no current reason to stay public, revoke it. Treat unused share links as something to remove, not something to leave active. Anthropic allows users to manage or revoke public conversation links directly from the Shared Chats section of their account privacy settings, per IBTimes (yesterday).
On attached files: Attached files are not included in shared conversation snapshots, according to Anthropic's support documentation cited by IBTimes (yesterday). The exposure risk comes from what you typed or pasted directly into the chat.
If you don't remember what a conversation contained: That's reason enough to revoke it. Any link you can't clearly identify as safe should come down.
Students and employees: Shared Claude links are public web pages. Check whether your school or employer has policies about sharing AI-generated work, research notes, or internal documents through public links. If the content belongs to an institution or employer, revocation is urgent, and you may need to notify a supervisor, instructor, or IT contact as well.
Step 2: How to see if your Claude chats were indexed by Google or Brave
Run these searches after reviewing your account list, so you can cross-reference anything you find.
- Open Google in a browser where you are not logged into any account, so you see the same public results anyone else would.
- Search:
site:claude.ai/share - Review the results. Look for conversation titles, topics, or visible text you recognize as yours.
- Search for Artifact-related pages. On July 26, X user Om Patel reported that searches such as
site:claude.ai/public/artifactssurfaced publicly shared applications, dashboards, and documents, per VentureBeat (this week). VentureBeat independently verified Artifact pages appeared in search results using the querysite:claude.ai/public/artifactslaunch. Try both variations and look for Artifacts you recognize.
If you find a result: Copy the full URL before doing anything else. You may need that exact link for a removal request or an internal report. Then go back to your account settings and revoke the link.
If you find nothing: That doesn't confirm your links were never indexed. Google may have already removed results following action by Anthropic or Google. The account audit in Step 1 is the more reliable check.
- Repeat both searches at Brave Search. Developer Ziwen Xu reported finding Claude conversations specifically through Brave after Google results began disappearing, per IBTimes (yesterday).
Step 3: What revoking a link fixes, and what it doesn't
Revoking a link makes the URL inactive. Anyone clicking it will no longer see the conversation or Artifact. That stops ongoing access through the live URL.
It does not automatically clear the page from search engine caches, archived copies, or any third-party site that may have saved the content before you revoked it. Cached versions from similar incidents have persisted after de-indexing, per Snyk (August 2025), and privacy experts note that previously shared links may continue to work unless the service provider disables them, per Moneycontrol (yesterday).
To clear a specific URL from Google: Submit it to Google's Remove Outdated Content tool. This works best when the underlying page no longer loads, which revoking the Claude link should cause. For Brave, check whether Brave's webmaster tools accept removal requests for your specific URL.
If the exposed content was high-risk:
- API keys or credentials: Treat them as compromised now. Rotate or revoke them immediately, without waiting to confirm whether anyone viewed them.
- Personal identifiers or financial information: Monitor relevant accounts for unusual activity. Consider whether a fraud alert fits your situation.
- Employer or client material: Notify your supervisor or your organization's IT or privacy contact. They may need to take additional steps.
- School or student data: Notify your instructor or your institution's data privacy contact if the content falls under school policy or student privacy requirements.
How to avoid this going forward
This isn't the first time Claude share links have turned up in search results. A similar incident occurred in September 2025, when Google estimated it had indexed just under 600 Claude conversations, per Forbes Australia (September 2025). Anthropic said at the time it instructs crawlers not to index shared conversations and does not share chat directories or sitemaps with search engines, but conversations still appeared. Anthropic spokesperson Gabby Curtis told Forbes that the conversations were visible because users had posted the links online or on social media, per Forbes Australia (September 2025). That explanation remains the working explanation for this weekend's incident as well.
The same pattern has run through AI platforms generally. In late July 2025, ChatGPT shared conversations appeared across Google, Bing, and DuckDuckGo, including content about mental health, legal issues, and career concerns, through a "discoverable" sharing feature, per Snyk (August 2025). OpenAI's Chief Information Security Officer said the feature "introduced too many opportunities for folks to accidentally share things they didn't intend to" and removed it, per Forbes Australia (September 2025). Similar problems affected Bard links in 2023-2024 and Grok transcripts in August 2025, per Snyk (August 2025).
The consistent lesson across all of these incidents: a share link is a public web page. How long or random the URL looks doesn't protect it once that link appears somewhere a crawler can reach.
Apply these habits going forward with any AI platform that offers sharing:
- Before clicking Share, ask whether you'd be comfortable posting the content on a public website. If not, don't create the link.
- Don't paste API keys, passwords, or credentials into any AI chat, shared or not.
- Don't post share links on public forums, social media, or anywhere you don't control who sees it.
- Revoke share links once their purpose is done rather than leaving them active indefinitely.
- Audit your shared links every few months. They accumulate faster than most people expect.
What to do now
Anthropic had not issued a public statement about this weekend's incident at the time of publication, per Moneycontrol (yesterday). Check Anthropic's status page and privacy documentation for updates on any indexing protections added to shared pages.
Complete these in order:
- Log into claude.ai > Settings > Privacy > Shared Chats. Review every link. Revoke anything old, work-related, containing sensitive content, or no longer needed.
- Search
site:claude.ai/shareand Artifact-related queries in Google and Brave. Copy the full URL of anything you recognize before revoking it. - Rotate or revoke any API keys or credentials that appeared in shared conversations. Do not wait.
- Submit specific indexed URLs to Google's removal tool after revoking the underlying Claude link.
- If the content involved employer, client, or school data, notify the appropriate contact at your institution or organization.
- Check Anthropic's privacy documentation to confirm what page-level indexing protections, if any, have been added to new and existing shared pages.