Open a new tab and search Google for this: site:claude.ai/public/artifacts.
You will get pages of real work that people published from Claude. Board decks with revenue tracking below plan. Compensation bands by level. Client financial models with the actual assumptions still in them. None of these people set out to publish to the open web. They hit a button that said Publish, copied a link, and sent it to one person. The button did exactly what it says. The web did the rest.
If you share artifacts from Claude for work, this is worth understanding once, properly, because the fix is easy and the default is not on your side.
"Public" means public, including to crawlers
When you publish an artifact, Claude puts it at a real URL on claude.ai with no login in front of it. That is the whole point of Publish: anyone with the link can open it. But "anyone with the link" and "anyone" become the same thing the moment a search engine finds the URL. Crawlers follow links. Pages with no noindex instruction get indexed. Indexed pages turn up when someone searches, browses, or runs a site: query like the one above.
None of that is a hack or a leak in the dramatic sense. It is how the public web works. The gap is between what Publish sounds like, share this with a person, and what it does, put this on the internet. For a "look what I made" to a friend, those are the same thing. For a page you built for a client, a candidate, or your board, they are very much not.
What Publish does not give you
The built-in share is one setting: public, forever, as-is. There is no:
- password, so a forwarded link is a public link
- expiry, so the page outlives the project that needed it
- noindex, so search engines are free to keep a copy
- your branding, so the client sees claude.ai around work they are paying you for
And on Team and Enterprise plans, Publish is disabled entirely, which is its own kind of answer. The plans built for companies do not want you public-sharing at all. Our guide to sharing a Claude artifact walks through every option, including for those locked-down plans.
The two things a private share actually needs
If a page is for specific people, it needs to be two things Publish is neither of:
- Not indexed. Search engines should have no page to crawl and no reason to keep one.
- Not readable by anyone without the link, including the host.
Most "unlisted link" tools give you the first and skip the second. The link is not indexed, but the file sits in plaintext on someone's server, one misconfiguration or legal request away from being read. If the work is sensitive enough that Google finding it would be bad, a server holding it in the clear is the same risk with extra steps.
The version worth using does both. That is the model we built commentable on, so here is exactly what it does. Hold any tool you pick to the same bar:
- The page is encrypted in your browser before it is uploaded. The key that decrypts it lives in the link fragment, the part after the
#, and never reaches our server. We store ciphertext. We cannot read your page, which means a crawler, a leak, or a court order gets nothing readable either. - The page carries noindex headers, so search engines are told not to list it, and there is nothing to list anyway.
- You can add a password and an expiry date, so a forwarded link is not a permanent public one.
- It wears your logo and your domain, not ours and not Anthropic's.
Encrypted and unindexed are not the same property, and you want both. Unindexed keeps the page out of search. Encrypted keeps it unreadable if it ever gets out anyway. Together they are the difference between "hard to find" and actually private.
Getting the same work out of Claude, privately
You do not have to give up Claude to get this. The artifact is just HTML. Two ways to move it:
- Copy and paste.Every artifact has a copy button. Paste the code into a private sharing tool and get a controlled link. This works on every plan, Team and Enterprise included, because copying your own code out is always allowed. Only Claude's own hosting is restricted.
- Skip the copy entirely. Claude supports connectors, and commentable ships one. Once connected, you say "publish this as a commentable link" in the chat and Claude hands back a private, encrypted, branded URL. Revise the artifact and it updates the same link, so the version your client already has quietly becomes the new one. The artifact never touches your clipboard, and it never touches the public web.
If you already published something sensitive
Go look. Run the site:claude.ai/public/artifacts search with your own titles, or open your Claude artifacts and check which ones say Published. For anything that should not be public:
- Unpublish it in Claude. The URL stops serving the page.
- That removes the live page, but Google can still show a cached copy for a while. To speed it up, use Google's Remove Outdated Content tool and submit the dead URL. Once the URL returns nothing, Google drops it on the next crawl.
- Re-share the work the private way if someone still needs it.
Then make it a one-time cleanup rather than a recurring chore, by not publishing sensitive work publicly in the first place.
The habit that avoids all of this
Share a link, not a public page. For anything with a name, a number, or a client on it, publish it somewhere unindexed and encrypted, add a password if it is sensitive, and send that. It is the same number of clicks as Publish, and your work stops being one search away from anyone.
You can paste an artifact and get a private link in under a minute, free, with your logo on it and nobody needing an account to open it.