Claude Artifacts
How to share Claude artifacts without a login
Your client doesn’t use Claude — and shouldn’t have to. Here’s how to send a Claude artifact as a branded, password-protected link that opens for anyone you choose, and won’t get indexed on Google.
The short answer
Can someone open a Claude artifact without an account?
Yes — a native Claude share can be viewed without an account, but only if you make it public. And that “public” part is the problem, not the solution. For a client-facing artifact, you want it open for the people you sent it to — not open to the whole internet.
[ answer ]
Viewers don’t need to log in if the artifact is public — but a confidential proposal or deck shouldn’t be public at all. The fix is a link-gated, password-protected, noindex link: no account for your viewer, and not discoverable by anyone else.
Native Claude sharing and its limits
Sharing an artifact straight from Claude is quick, and it’s genuinely useful for casual sharing. But for client work, a native share leaves a few gaps worth knowing about before you hit send.
No branding
A native share carries the host’s look, not yours — no logo, no domain, no premium impression for your client.
No password
Anyone with the URL can open it. There’s no gate for a confidential proposal, pricing sheet, or deck.
No analytics
You can’t tell whether the client opened it, when, or how long they read — so you’re following up blind.
Can be public
A “shareable” link is often a public web page. That’s the part most people miss — and the reason it can end up discoverable.
A risk most people miss
A “shareable link” can be a public link
The easy free way to put a page online usually publishes it as a public web page that Google can index by default — a risk most people miss when they’re just trying to send a client a link. Fine for a personal site; risky for a proposal, deck, or anything confidential.
A client-ready link should be the opposite of public. It should be link-gated (only people with the URL get in), password-gated when it’s sensitive, and noindex so it never surfaces in search.
See how Pagelive keeps it private →Illustrative demonstration of default behaviour. No real customer data.
Client-ready links with Pagelive
Pagelive turns a Claude artifact into a link you can actually send to a client: no Claude login for the viewer, your branding, an optional password, and tracking so you know it landed.
No login for viewers
Your client clicks the link and the page opens in any browser — no Claude account, no app, no sign-up.
Your branding
A clean link on your own domain with Founding — your logo, your name. It looks like your studio sent it, not a generic host.
Password + noindex
Lock it with a PBKDF2-hashed password and keep it out of Google — pages are noindex by default on an isolated content plane.
Tracked opens
See the moment the client opens it, how long they read, and from where — so you follow up while you’re top of mind.
Public vs password-protected sharing
Both have their place — the trick is knowing which one a given artifact deserves. Here’s a simple way to decide.
Public link (no gate)
A landing page, a marketing demo, a portfolio piece — content you want anyone to find and Google to index.
Password-protected link
A client proposal, pricing, a pitch deck, an investor update — anything confidential that should open only for the people you sent it to, and never on Google.
With Pagelive every page is noindex by default, so a public link still won’t show up on Google unless you opt it in — and a password adds the gate when it matters.
How Pagelive keeps it private →Branded delivery
Custom domains and a white-label impression
On Pro, publish to a link on your own domain — like proposals.yourstudio.com — with no host badge. The artifact arrives looking like your studio built and delivered it, which is exactly the premium impression you want a client to have.
Know when a client opens it
A native share leaves you guessing. With Pagelive you see the moment the client opens the artifact, how long they spent reading, which day, and roughly where from — so you follow up at the right time instead of into the void.
Sharing FAQ
Do viewers need a Claude account? +
No. A Pagelive link opens in any browser — your client never needs Claude, an app, or any login. If you add a password, they just enter that one password; there’s still no account to create.
Will my shared artifact show up on Google? +
No — pages are noindex by default. Pagelive sends the robots meta tag and X-Robots-Tag header that tell search engines not to list the page, so a client-facing artifact stays out of search results unless you explicitly opt it into indexing.
Can I revoke access after I’ve shared it? +
Yes. You can unpublish the page at any time so the link stops serving, or add (or change) a password to re-gate it. Because every page lives on the isolated content plane, a single flip at the edge takes it down.
Send your Claude artifact as a link they can just open.
No viewer login, your branding, password-protected, noindex by default.