How to get a public link from Claude
Claude is good at producing a finished page — a dashboard, a report, a small site. It cannot, on its own, put that page on the internet. Turning what it made into something you can paste into a message is a separate step, and there are a few ways to take it.
Artifacts are a preview, not a public URL
When Claude builds something visual you often get it as an artifact you can see and interact with. That is a preview inside the conversation. It is genuinely useful for iterating, but it is not the same as a page anyone on the internet can open, and the distinction matters the moment you want to send it to a client.
Copy it out and host it
Ask for the full HTML, save it as index.html, and put it on any static
host — Netlify, Cloudflare Pages, GitHub Pages. All free for something this size.
This works and it is worth knowing how to do. The cost is that you do it again every time you change anything, and every revision means another trip out of the conversation.
Let Claude publish it
Claude supports connectors over MCP, which means it can use an outside tool as part of the conversation. Connect one that publishes, and the exchange becomes:
you: make me a dashboard of last quarter and share it
claude: it's live — https://q3-sales.example.comClaude Code users can add a connector with a single command; in the Claude apps it is a URL pasted into connector settings, followed by a sign-in and an approval. Either way it is a one-time setup.
What to check before you send the link
- Does it contain anything private? Generated pages pick up whatever was in the conversation — keys, internal names, real customer data.
- Will the link still work next month? Some tools expire links by default. If you are sending it to a client, find out which kind you have.
- Can you change it later without changing the URL? If the address moves every time you edit, you will be re-sending links forever.