Build a website with Claude Artifacts and share it by link

Claude builds websites as Artifacts, which are self-contained interactive pages that render live inside the conversation. You describe the page, it appears, you click around, you say what is wrong, it changes. Since 13 July 2026 you can publish an Artifact to a public link that opens for anyone, including people who have never used Claude.

That last part is what turned this from a preview trick into a real way to get something live. The loop from idea to shareable URL is one conversation, with no hosting setup, no build step, and no deploy.

What can you build this way?

Artifacts are strongest where the page does something rather than only saying something. That covers more of a small business site than people expect.

One-page business sites work well: what you do, proof, and one clear action. So do landing pages for a single offer, interactive tools like calculators and assessments, client-facing planners and trackers, and event or waitlist pages.

Where Artifacts stop being the right answer: anything needing visitor logins, a database of customer records, or a payment flow on the page itself. Payment can sit in front of an Artifact as a checkout link, and that works fine for a first product, but the transaction does not happen inside the page.

How do you brief the first build?

Describe the visitor and the single action. Interface instructions come in round two, once something exists to react to.

Build this as an interactive artifact.

What I do: [your offer, one plain sentence]
Who visits: [who they are, what they are trying to figure out]
The one action I want: [book a call, join the list, message me, buy]
What they need to believe first: [the objection standing in the way]
My real proof: [testimonials, numbers, credentials, names. Only real ones.]

Structure: headline, one paragraph on what changes for them, three proof points,
what happens after they contact me, the action button. Repeat the action at the
bottom.
Style: [two or three adjectives, brand colors, fonts if you have them]
Requirements: phone-first layout, no stock-photo placeholders, and do not invent
testimonials, statistics, or client names. Leave a marked blank if I have not
given you the proof.

That final instruction earns its place. Every AI site builder writes plausible fake testimonials from invented people when you leave a gap. A marked blank is useful. A fabricated quote is a liability.

Why does the iteration loop matter more than the prompt?

Because you cannot brief a page you have not seen. The first build is a starting point, and the value comes from five rounds of specific correction against the live thing.

Open it on your phone. Read it as a stranger who has never heard of you. Then give Claude precise fixes: this headline describes me instead of their problem, the button is below the fold on mobile, this section is three paragraphs where one would do, this proof point has no number in it.

Five rounds of that beats any amount of effort on the opening prompt.

How do you publish and share it?

Publish the Artifact and Claude gives you a public URL that opens in any browser with no account needed. Public links are available on every plan since 13 July 2026.

For a real business you want your own domain in front of that eventually, and that is the moment to move the page onto a platform you control. Treat the Artifact link as the version that gets you live today and gets you feedback this week.

Where does Claude beat ChatGPT Sites?

Both build and host a page from a conversation, and they differ in three ways that matter.

Availability is the biggest one. Artifacts publish publicly on every Claude plan. ChatGPT Sites is in public beta on paid plans only, excluding Free and Go, and it is unavailable in the European Economic Area, the United Kingdom, and Switzerland as of July 2026. If you are in those regions or on a free tier, Claude is the available path.

Design control is the second. Artifacts respond well to detailed style direction and to a brand suffix you paste into every build, which makes it easier to get pages that look like they came from one brand.

Ownership is the third, and neither wins outright. Both are hosted by the model provider. Both are the fast route to live rather than the permanent home.

The full comparison across tasks beyond websites sits in ChatGPT vs Gemini vs Claude, and the ChatGPT Sites walkthrough is in build a website with ChatGPT.

What about the copy?

Write it separately. Claude will produce competent generic website copy by default, and generic copy does not convert.

You are my website copywriter. My offer is [describe it and the price]. My buyer
is [who they are, what they have already tried, what they are afraid of].
Write the page: headline naming their problem in their words, one paragraph on
what changes, three proof points, what happens after they reach out, button text.
Rules: no superlatives, no "passionate about," no jargon. Every claim names a
number or gets cut. Then read it back to me as a skeptic and tell me what you
would not believe.

The skeptic pass at the end is the useful part. It surfaces the claims that sound like marketing before a visitor decides the same thing.

What order should this happen in?

The site is not step one. Sell the thing in conversations first, then build the page to scale what already worked. Get your first customer before you build a website has the method, and it holds even when building the site takes an afternoon, because a fast site pointed at an unvalidated offer is still a fast way to reach nobody.

If you want your Artifacts to look like your brand instead of a default, the Claude design starter kit has the style prompts and the brand suffix to paste into any build. And once the page is live, the WorkSmart Scale Plan covers the traffic and follow-up that make it part of a revenue path.