Claude Shared Chats on Google? Audit and Unshare Them

Claude chats are private by default. The late-July 2026 exposure reports involved conversation snapshots and artifacts that users had explicitly made public with Claude's Share feature, not private chats that were never shared.

If you have ever clicked Share, open Settings > Privacy > Shared chats, review every entry, and unshare anything that no longer needs a public link. If a snapshot contained an API key, password, session token, wallet secret, customer data, or internal plan, revoking the link is only the first step. Rotate the credential, review access logs, and handle the event as a possible disclosure.

What Happened

On July 25, 2026, Claude users showed that public share pages could appear in Google results. The discussion spread across Reddit, X, Hacker News, YouTube, and technology publications over the next several days.

Anthropic's documentation is precise about the sharing boundary:

• chats are private by default;

• creating a share link publishes a snapshot of messages sent before sharing;

• anyone with the link can view that snapshot;

• attached files and raw MCP tool-call data are not included, but the conversation, Claude's responses, and artifacts are;

• changing the chat from Public to Private disables the direct link.

Axios reported on July 27 that it could still find some publicly shared Claude artifacts in Google, although it could not find the chat conversations it tested. Anthropic said it does not provide chat directories or sitemaps to search engines and that public links become discoverable after users share them somewhere a crawler can see.

The practical lesson is not that every Claude chat was exposed. It is that a public bearer link is publication, even when you intended to send it to one person.

Prerequisites

Before you start, gather:

• access to the Claude account that created the share links;

• a private or signed-out browser window for verification;

• access to revoke any credentials that may appear in a snapshot;

• the security or privacy contact for your organization, if regulated or customer data may be involved;

• a simple incident log for the chat title, shared date, action taken, and verification result.

Do not copy sensitive content into another chat, ticket, or search query while investigating it.

Step 1: Inventory Every Shared Chat

In Claude:

1. Open Settings.

2. Select Privacy.

3. Find Shared chats and click Manage.

4. Review the title, date shared, and link for every entry.

Expected result: the modal lists every shared snapshot for supported Free, Pro, and Max accounts. If it says No shared content found, the account has no shared snapshots in that log.

For each entry, classify the highest-risk content that appears in the conversation or artifact:

Treat an unfamiliar chat title as unknown risk until you inspect the snapshot. Do not assume an old link is harmless because you no longer remember sharing it.

Step 2: Unshare the Snapshot

You can revoke a shared snapshot from either location:

1. In Settings > Privacy > Shared chats, click Unshare next to the entry; or

2. open the chat's Share menu, open the visibility dropdown, and change Public to Private.

Expected result: Claude disables the direct link to the last shared snapshot.

Record the time, chat title, and person who performed the action. If several people manage a shared account or workspace, assign one owner and work through the list once. Parallel cleanup without a shared log creates gaps and duplicate work.

Team and Enterprise plans use organization-scoped sharing rather than public sharing according to Anthropic's current documentation. Still review the intended audience and remove links that are no longer needed.

Step 3: Verify the Link Is Disabled

Open the old share URL in a private or signed-out browser window.

Expected result: the public snapshot is no longer available. Test the exact URL rather than trusting the settings toggle alone.

If the page still renders:

1. confirm you changed the same snapshot to Private;

2. close authenticated Claude sessions in the verification browser;

3. retry from a different browser profile or network;

4. capture the non-sensitive time and status, then contact Anthropic support if the public URL remains accessible.

Do not paste a secret-bearing URL into a public issue, social post, or third-party scanner to prove that it exists.

Step 4: Check Search Results Without Re-Exposing the URL

After revoking the link, search for a distinctive but non-sensitive title or phrase that appeared in the result. You can also review searches such as:

site:claude.ai/share "non-sensitive unique title"

Expected result: the revoked page eventually disappears from current search results. A missing result is useful evidence, but it is not proof that nobody copied, cached, or archived the snapshot.

If Google still shows a result after the source page has been disabled, use Google's Refresh Outdated Content tool with the old URL. Google explains that this process updates results for a page that no longer exists or no longer contains the indexed content. It does not erase copies held by other services.

Search indexing controls such as noindex are implemented by the page owner, not by the user who created a Claude snapshot. Revoking your public link is the control you own.

Step 5: Rotate Anything That Could Grant Access

Deleting or unsharing text does not make a copied credential safe. For every secret that appeared in the snapshot:

1. revoke the old credential at its provider;

2. issue a replacement with the smallest required scope;

3. update the legitimate consumer;

4. test the new credential;

5. verify the old credential fails;

6. review access logs from the share date through the revocation time.

OWASP recommends centralized secret storage, least privilege, logging, revocation, and rotation. Apply the provider's own incident procedure for the specific credential. A database password, GitHub token, cloud service-account key, session cookie, and cryptocurrency seed require different containment steps.

Do not postpone rotation because you cannot prove someone opened the page. Public discoverability means the exposure window is not measurable from your browser history alone.

Step 6: Review the Data Blast Radius

Use the snapshot itself to build a factual exposure list:

• which messages and artifacts were included;

• the share date and revocation time;

• whether the link was posted in a forum, social network, document, or ticket;

• which people, systems, customers, or repositories were named;

• which credentials were valid during the exposure window;

• what access or transaction logs show;

• which notifications or regulatory steps your policy requires.

Anthropic says attached files and raw MCP tool-call data remain outside the shared snapshot. Do not extend that fact too far. A response can still repeat or summarize sensitive values from a file or connected tool, and an artifact is part of the snapshot.

Step 7: Stop Pasting Provider Secrets Into Chats

The safest cleanup is to reduce what a future snapshot could contain.

• Prefer OAuth or a managed connection over a long-lived API key in a prompt.

• Give an agent the narrowest Action it needs instead of a broad credential.

• Keep credentials in a vault and keep raw values out of prompts, chat output, logs, and screenshots.

• Use read-only access for research and inspection.

• Separate the approval for a write from the conversation that planned it.

• Review external access with the same discipline you use for MCP API keys versus OAuth and an MCP gateway.

Aident Loadout lets an agent execute connected Actions without putting the provider credential in the prompt. The setup pattern is covered in How to Connect Claude Code and Codex to Real-World Tools. This does not make a public chat safe to share, but it removes one common class of secret from the transcript.

Common Failure Modes

Treating a Public Link as a Private Message

An unguessable URL is not access control. Anyone who receives it can forward it, post it, or expose it to a crawler.

Unsharing Without Rotating Secrets

Revocation closes the source URL. It does not invalidate a credential that someone already copied.

Searching With the Full Sensitive URL Before Revoking It

That can disclose the link to another system. Revoke first, then search with a non-sensitive phrase or use the provider's removal process.

Assuming Search Results Are a Complete Exposure Log

Search engines can omit, delay, cache, or remove results. Use provider access logs and your own share inventory as the evidence base.

Calling Never-Shared Chats Public

The reported incident concerned public share snapshots and artifacts. Keep your incident statement exact so users can take the right action without unnecessary panic.

Why This Fix Works

Claude's share control creates a public snapshot with its own URL. Changing the visibility to Private disables that origin URL. Search engines eventually refresh or remove results when the underlying page disappears, and Google's outdated-content workflow can request another crawl.

Credential rotation solves a different problem. It makes a copied secret stop working. You need both actions when a public snapshot contained access material: revoke the page and revoke the secret.

This guide follows the repeatable structure behind Aident's Ollama networking guide: name the exact symptom, answer it early, give reproducible steps and expected results, cover failure modes, and explain the mechanism.

Run One Secret-Free Action

Connect one read-only integration through Aident Loadout, run aident vault vault --action status, then execute one harmless read Action without pasting a provider key into the prompt. Success means the Action returns a provider result, the credential never appears in the chat, and your Shared chats inventory has no unowned public link.

Sources

• Share and unshare chats, Anthropic, updated June 15, 2026 and accessed July 30, 2026

• Users' Claude creations are showing up in Google search, Axios, published July 27, 2026

• Refresh outdated content, Google Search Help, accessed July 30, 2026

• Robots meta tag, data-nosnippet, and X-Robots-Tag specifications, Google Search Central, accessed July 30, 2026

• Secrets Management Cheat Sheet, OWASP, accessed July 30, 2026

• You can view a lot of shared conversations via Google, Reddit, published July 25, 2026

Refresh this guide if Anthropic changes the Shared chats inventory, public-link behavior, organization sharing rules, snapshot contents, or revocation workflow.