Are Your Shared Claude and DeepSeek Chat Links Public on Google? How to Check and Protect Yourself
What to know about Claude and DeepSeek shared chat links showing up in Google search results, how to check if any of yours are exposed, and how to stop it happening again.
If you've ever used the "Share" button on a Claude or DeepSeek conversation, there's a real chance that link is sitting in Google's index right now, alongside everyone else's who did the same thing.
In late July 2026, reports surfaced that shared Claude conversations had been indexed by Google Search — some containing API keys, personal details, and other information users almost certainly didn't intend to publish. DeepSeek had a similar problem reported days earlier, with shared chats turning up as searchable pages. Neither is a hypothetical risk. Both were reported by independent outlets, and both point to the same underlying issue: a "share" feature that quietly behaves like "publish."
This post covers what actually happened, why it matters even if you think you've never shared anything sensitive, how to check whether any of your own links are exposed, and what to do about it going forward.
What happened
Claude has a "Share" feature that generates a public link to a conversation — useful for showing someone a chat without giving them account access. The problem reported by TechRepublic and IBTimes UK is that some of these shared links were crawled and indexed by Google, meaning they became findable through ordinary search queries, not just by whoever the link was sent to. Some of the indexed conversations reportedly contained things like API keys and other personal data that the original user likely never expected to be public, let alone searchable.
DeepSeek had a related issue a few days earlier. Cybernews reported that Google had been indexing shared DeepSeek chats too, meaning conversations that users assumed were private-by-link were, in practice, searchable by anyone.
The common thread: a "shareable link" is not the same thing as a "private link." If a page is reachable without a login and nothing tells search engines to skip it, a search engine will eventually find it and index it. That's just how the web works, and it applies to AI chat platforms exactly as much as it applies to any other website. The precise mechanism in Anthropic's case is worth understanding, because it's more specific than a simple missing tag: Claude's robots.txt blocks crawlers from opening share pages at all, which means Google never sees any noindex instruction that might be sitting inside them — and a page blocked that way can still be listed in results by URL alone if it's linked from somewhere else, just without a content preview.
Why it matters, and who's affected
The obvious group affected is anyone who has ever clicked "Share" on a Claude or DeepSeek conversation and sent the link somewhere, even privately — a Slack message, a Discord server, a support forum. If that page was indexable, it doesn't matter how few people you sent it to. A crawler doesn't need your explicit permission, only a discoverable link.
This matters more than it might first seem, for a few reasons.
Chats contain things people don't think of as "shareable." A conversation you shared to show a friend a funny answer might also contain a code snippet with a hardcoded API key, a snippet of a work project, or a personal detail you mentioned three messages earlier and forgot about by the time you hit share.
You may not remember what you shared. Shared links accumulate over time, especially if you use "Share" as a quick way to send a conversation somewhere rather than exporting it properly. Most people don't keep a running list of every link they've ever generated.
Search indexing is invisible until someone finds it. There's no notification that says "your shared chat is now on Google." You'd only find out by searching for it yourself, or by someone else stumbling on it and telling you.
If you've pasted crypto material into a shared chat, treat it as urgent. Anyone who has used a shared conversation for wallet debugging — seed phrases, private keys, recovery phrases — is in a categorically worse position than someone whose password leaked. A leaked password can be rotated in under a minute, and the old one instantly becomes worthless to whoever has it. A compromised private key cannot be rotated: whoever holds it controls the wallet, permanently, and there is no reset, no support line, and no way to revoke it. If that describes any conversation you've ever shared, move the funds to a freshly generated wallet before working through anything else on this page.
None of this means Claude or DeepSeek are uniquely unsafe compared to other AI platforms — ChatGPT and Grok have their own privacy tradeoffs worth understanding too, covered in our broader look at what happens to your AI chat history. But this specific issue — sharing features producing publicly indexed pages — is worth checking for directly, because it's the kind of exposure you can actually search for and fix.
How to check if you're affected
There's no dashboard that tells you "3 of your shared chats are indexed." You have to check manually, but it's quick.
1. Search Google for your own shared links. Claude shared links typically follow a pattern like claude.ai/share/.... Try a site-restricted search:
site:claude.ai/share [your name, email, or a distinctive phrase from a chat you shared]
Do the same for DeepSeek, adjusting the domain pattern to whatever the platform uses for shared conversations. If nothing comes up, that's a good sign but not a guarantee — indexing is inconsistent and depends on when Google's crawler last visited.
2. Review your own "Shared" or "Shared links" list. Both Claude and DeepSeek keep a record of conversations you've shared, usually somewhere in account or conversation settings. Go through it. If you don't remember creating a link, or don't remember what was in the conversation, open it and check.
3. Search for distinctive content from chats you're worried about. If you recall sharing a chat that mentioned a specific project name, client name, or unusual phrase, search Google for that exact phrase in quotes. Distinctive text is far more useful for this than a generic search.
4. Check whether the platform has already acted. Following press coverage like this, platforms sometimes retroactively de-index affected pages or add noindex tags. That's a good outcome, but it doesn't undo the fact that a link was public and crawlable for some period of time — anyone who found it before the fix still has access to whatever was in it.
If you find one of your own shared links indexed, revoke or delete the share from your account settings on the platform, then request removal from Google via Google's Remove Outdated Content tool if the page still appears in results after you've deleted it.
How to protect yourself going forward
Stop treating "Share" as "send privately." Assume any link a platform generates for a conversation is closer to "publish to the internet" than "send a private message," unless the platform explicitly states otherwise and you trust that statement. If you want to send a chat to one specific person, copy and paste the relevant text instead of generating a link.
Never share a conversation containing keys, credentials, or personal data. This sounds obvious, but it's the exact failure mode reported with Claude — people shared debugging conversations without noticing an API key was visible in the code they'd pasted earlier in the thread. Read back through a conversation before sharing it, not just the part you meant to show.
Revoke old shared links you no longer need. If you've been using AI chat tools for a while, you likely have shared links floating around that you generated once and forgot about. Go through your account's sharing history periodically and revoke anything you don't actively need public.
Keep your own local copy instead of relying on shared links. If the reason you're sharing a conversation is to keep a record of it, or to reference it later, a shared link is the wrong tool for that. A local export gives you the same content without putting it on a public URL. This is the same underlying advice covered in our guide to backing up AI conversations — the safest copy of your chat history is the one that never touches a server you don't control.
Be extra cautious with DeepSeek specifically. Beyond the shared-link indexing issue, DeepSeek stores data on servers in China, which brings its own set of considerations independent of this incident. Our DeepSeek data safety breakdown goes into that in more detail if you use the platform regularly.
FAQ
Did Anthropic or DeepSeek confirm this was a bug rather than intended behaviour? Based on the reporting from TechRepublic, IBTimes UK, and Cybernews, this behaved like an oversight in how shared links were handled with respect to search engine crawling, rather than a deliberate design choice to publish conversations. Regardless of intent, the practical result for affected users was the same: a conversation they thought was link-private turned out to be publicly searchable.
If I never used the Share button, am I affected? No. This issue is specific to conversations that were explicitly shared via a generated public link. Conversations you never shared were not affected by this particular incident. That said, it's a good moment to review your general chat privacy habits, not just your sharing history — see our broader piece on AI chat history privacy.
Will deleting a shared link remove it from Google immediately? Not immediately. Deleting or revoking the share on the platform side stops it from being live, but Google's cached copy of the page can persist until the index is refreshed, which isn't instant. If a stale copy is showing up after you've revoked the link, use Google's removal request tool to speed that up.
Is it still safe to use the Share feature at all? It's safe for content you'd be comfortable with anyone finding, the same way you'd think about posting on a public forum. It's not a substitute for private messaging or for keeping a personal record of a conversation. If in doubt, don't share the link — copy the text you need instead.
If you want a private record of your Claude, DeepSeek, ChatGPT, or Grok conversations that never depends on a shared link or a platform's server, AI Chat Importer Desktop turns your exports into a searchable local archive that stays on your own machine. If you'd rather try it without installing anything first, the free web app runs the same import entirely in your browser, no account needed.