Are your shared Claude chats and artifacts on Google? How to check, and how to share safely instead

Yes, it is possible, and checking takes about two minutes. In late July 2026, people found that publicly shared Claude conversations and artifacts were showing up in Google results, some of them containing resumes, internal company documents, and medical information. Anthropic addressed the Google side within about 48 hours. The underlying lesson did not go away: a share link is a public URL, and a public URL is one forward, one post, or one crawler away from being permanently readable.

This page covers three things: how to check what you have shared, what to do if something is exposed, and how to share an AI-built app when the link needs to stay private.

What actually happened

• 25 to 27 July 2026. Reddit users noticed that a search for site:claude.ai/share returned hundreds of shared conversations and artifacts. Reporting followed from 404 Media, TechCrunch, Axios and VentureBeat.
• What was in them. Reports described resumes, financial spreadsheets, internal documents, clinical records, and in some cases personal details of named individuals.
• The fix. By 28 July the Google results were gone. Anthropic's position, quoted in the coverage, is that it does not hand chat directories or sitemaps to search engines, and that share links surface only when they have been posted somewhere a crawler can reach.

That last point is fair and worth stating plainly: this was not a breach, and nothing was shared that a user did not choose to share. It is a design property. A share link is unlisted, not private. Unlisted means anyone holding the URL can open it, and a URL leaks the moment it lands in a Slack channel that syncs somewhere, a public ticket, a forwarded email, or a screenshot posted to a forum.

How to check what you have shared

1. In Claude: open Settings, then Privacy, then Shared Chats. That list is every conversation you have published a link for. Delete the ones that should not be public.
2. In Google: search site:claude.ai/share plus a term of your own, such as your company name or a project name. Do the same on Bing and DuckDuckGo, since remediation on one engine does not clear the others at the same speed.
3. In ChatGPT, if you also use it: the same category of exposure was reported there in 2025. Check your shared links in Settings and remove what should not be public.
4. Ask the practical question about each surviving link: would I be comfortable if this URL were posted publicly tomorrow? If the answer is no, the link is the wrong container for that content.

What to do if something is already indexed

• Delete the share link at the source first. Removing the link is what makes the page stop resolving.
• Then request removal from the index. Google's Remove Outdated Content tool handles pages that are already gone. Bing has an equivalent in Webmaster Tools. Deleting the share alone does not clear a cached search result.
• Treat credentials in the content as compromised. If an exposed conversation contained an API key, a password, or a token, rotate it. You cannot know who read the page before it came down.

Unlisted links versus access control

The distinction that matters is not "private or public". It is whether access is a secret URL or an actual rule.

An unlisted URL is a reasonable way to send someone a recipe. It is a poor way to send someone a dashboard with customer data in it, because the security of that dashboard is now the security of every inbox, channel, and browser history the URL has passed through.

How to share an AI-built app when the link has to stay private

If what you built is a real tool that people will keep using, the fix is not a better secret URL. It is deploying it as an app that decides who gets in. On White Ghost that looks like this:

1. Install the CLI: npm install -g ghosty-cli.
2. Run ghosty init. The app is scaffolded as a normal repository in your own GitHub account, with a managed PostgreSQL database.
3. Keep building with the assistant you already use. Claude Code and Codex drive the CLI directly, and every command supports --json.
4. Choose the access mode for the app: public, a shared invite code, or your own sign-in written into the app.
5. git push. The app builds and goes live on its own URL, and later on your own domain with SSL handled for you.

Two things are true at once here, and both are worth saying:

• The gain is real. The link stops being the credential. Viewers never need a Claude or ChatGPT account, the app keeps working after the conversation that produced it is gone, and it can store data and be updated instead of being a frozen snapshot.
• The limits are real too. The invite code option is a single shared code, not per-person invitations: there is no list of guests and no way to revoke one person without changing the code for everyone. Per-user identity is something you implement yourself with the sign-in option. We would rather you know that before you pick a mode than discover it later.

The rule worth keeping

Sharing a conversation is publishing. Sharing an app is granting access. Any time the content would embarrass you, breach a client agreement, or expose a customer if it appeared in a search result, use the second one.

Frequently asked questions