Claude’s own share link publishes to a page search engines have already crawled. Paste the artifact here instead and the page stays out of search results by default.
Published with noindex by default, and expires in seven days on the free tier.
Claude artifacts are made to be shared, and the built-in share button is genuinely one click. The thing worth knowing before you use it on anything sensitive: in late July 2026, people discovered that shared Claude conversations and artifacts had been indexed by Google and were turning up in ordinary search results — the same failure OpenAI had with shared ChatGPT conversations before it. "Anyone with the link" quietly meant "anyone searching", because the shared pages went out without the one directive that keeps crawlers off them. If the artifact is a client deliverable, an internal draft, or anything with a name in it, that difference matters. Pasting the artifact here gives you the same one-link convenience on a page that ships noindex from the start.
Copy the output straight from your AI tool — the raw HTML or markdown, not a screenshot. There is no file to save and no app to install first.
Paste it into the box above. The preview renders it the way the recipient will see it, so you can confirm the formatting before you share.
Create the link and send it. Whoever you send it to opens a clean, read-only page in their browser — on a laptop or a phone — with nothing else from your chat attached.
Imagine Claude built you a hiring scorecard artifact — a styled HTML table with candidate names, interview notes, and a recommendation column — and you want two colleagues to read it before Friday. Using the native share link puts that page on a public URL under Claude’s domain, which is fine for a demo and much less fine for named candidates. Open the artifact, copy its contents, and paste them here instead. The published page carries noindex in two places at once: the page metadata and an X-Robots-Tag response header, so a crawler that ignores one still sees the other. On the free tier the link then expires by itself after seven days — for a decision that closes on Friday, an expiring link is a feature, not a limitation, and the URL stops resolving without you having to remember to revoke anything. If the notes are sensitive enough that the URL alone should not be enough to read them, password protection is a paid feature; the honest way to think about it is that noindex plus expiry is what you get for free, and a lock on the door is what you pay for.
Yes. In late July 2026 it was reported that shared Claude conversations and artifacts were discoverable through ordinary Google searches, and the same thing had happened earlier with shared ChatGPT conversations. The root cause in both cases was a share page published without a directive telling search engines to stay away, so "unlisted" turned into "public" as soon as a crawler found a path to it. Treat it as a reason to think about where a link lives, not as a reason to distrust the artifacts feature.
Every published document is served with noindex, follow as an X-Robots-Tag HTTP header and carries the matching directive in its page metadata. Two independent layers say the same thing, so a crawler that only reads headers and one that only reads the document both get the message. Documents are also served from a separate cookieless origin from the app itself, so a published page never runs inside your account’s session scope.
Yes. Free links expire on their own after seven days, and you can delete a page at any point before that from the dashboard if you published while signed in. Deleting removes the document rather than hiding it, so the URL stops resolving. For anything sensitive the combination worth having is a password — a paid feature — on top of the default expiry: access is gated while the page is live, and the window closes without depending on anyone remembering to clean up.
For a self-contained artifact, yes — the HTML renders in a sandboxed frame with scripts enabled, so a styled document or an interactive widget behaves the way it did in the artifact panel. Artifacts that pull in resources from Claude’s own interface, or that depend on being inside the chat, are the exception: copy the complete document rather than a fragment and the result is what your reader sees.
Open the artifact, use the share control in its top-right corner, and Claude gives you a claude.ai/public/artifacts/... URL. That is genuinely the fastest route and it is the right one when the reader is another Claude user who wants to fork it. Two things it is not good at: the page is served under Anthropic branding on a URL nobody recognises as yours, and — the reason most people end up here — the publish control is greyed out for artifacts inside a Project, on some managed workspaces, and for a conversation you opened from someone else. Pasting the artifact code here sidesteps all three, at the cost of the fork button.
Los enlaces gratuitos duran 7 días con una cuenta gratuita. Con un plan de pago, cada página que publiques se queda online de forma permanente.
Ver precios