How to publish a Claude artifact as a real website

You asked Claude for a landing page, and the artifact looks right. Now you want it at www.yourbrand.com, with a form that keeps the emails people leave and a count of who showed up. This guide covers what Claude's own sharing gives you, where it stops, and how to publish the same page with Convika without copying any code.

What Claude's own publishing gives you

Claude has two ways to put an artifact on the web. Both keep the page on a claude.ai address.

• Artifacts from the Claude app. You share them with a link. According to Anthropic's help center, everyone who opens a shared artifact needs a Claude account. The exception is an artifact published with the older Publish button, which anyone can open. Published artifacts can also be embedded on another site with an embed code.
• Artifacts from Claude Code. A public link opens for anyone without signing in. Claude Code's docs describe the page as "one self-contained page with no backend," and its scripts can only call its own origin.

Neither set of docs mentions custom domains, storing form submissions, or visitor analytics. That's fine for showing a draft to a friend. It's a problem for a page you want to send ad traffic or a launch post to.

Publish your artifact with Convika in 6 steps

You don't copy code or upload files. Claude does the handoff through a connector, which is Claude's name for a remote MCP server.

Create a free Convika account

Sign up at app.convika.com. The Free plan needs no credit card and covers 10 pages.

Add Convika to Claude as a custom connector

In Claude on the web or desktop, open Customize → Connectors, click +, then Add custom connector. Enter https://mcp.convika.com and sign in to Convika when asked. Anthropic's connector guide notes that the Claude Free plan allows 1 custom connector.

Ask Claude to save the page and show you a preview

In the chat that has your artifact, write: “Save this page to Convika and give me a preview link.” Claude sends the page's HTML to Convika and returns a private preview URL. Nothing is public yet. Convika stores each page as one HTML document, so if your artifact is a React component, ask Claude to convert it to plain HTML first and check the result in the preview.

Add a signup form

Write: “Add an email signup form under the headline.” Claude creates the form in Convika and places it on the page. Submissions sent from the preview are checked but not stored, so your list stays clean until launch.

Publish it and connect your domain

Write: “Publish it.” The page goes live at an address like yourbrand.convika.com. Then write: “Connect www.yourbrand.com.” Convika gives you one CNAME record to add at your DNS provider, and the SSL certificate is issued for you. Automatic setup works with subdomains such as www or launch, not a bare yourbrand.com.

Ask how the page is doing

A day later, write: “How many people visited, where did they come from, and how many signed up?” Claude reads Convika's analytics: visits, traffic sources and UTM tags, devices, button clicks, and form submissions. Export the signups as a CSV whenever you need them.

Other ways to host an artifact

Convika is one option. Pick by what the page has to do.

• Embed the published artifact on a site you already run, using Claude's embed code. The page still lives on claude.ai inside a frame on your site.
• Copy the code to a static host. Save the artifact's code as index.html and upload it to a host such as Netlify, Cloudflare Pages, or GitHub Pages. You get a URL and a custom domain, then add a form service and an analytics script yourself. See free hosting options compared.
• Use Convika when you want the form, the analytics, and the domain in one place, and want to keep editing the page by talking to Claude.

Convika is the wrong fit for apps that need a login, a database, or several routes. It hosts landing pages.

Frequently asked questions

Can I put a Claude artifact on a custom domain?

Not from inside Claude. A shared artifact stays on a claude.ai link, and the most you can do is embed it on another site. To use your own domain, host the page's HTML somewhere that supports custom domains. With Convika, Claude publishes the page and sets up a subdomain such as www.yourbrand.com; you add one CNAME record.

Do visitors need a Claude account to see my page?

For artifacts shared from the Claude app, yes, unless the artifact was published with the older Publish button. Public Claude Code artifacts open without signing in. A page on Convika is an ordinary website, so anyone can open it.

Can a Claude artifact collect email signups?

Claude Code's docs describe an artifact as a static page with no backend whose scripts can only reach its own origin, so a form on it has nowhere of yours to send entries. On Convika, the form stores every entry in your account, and you can export them as a CSV.

What does it cost?

Convika's Free plan needs no card: 10 pages with a small “Powered by Convika” badge, 50 form submissions a month, and 1 custom domain. Pro costs $12 a month after a 14-day free trial and removes the badge and the submission cap.

Does publishing from Claude use Convika's AI credits?

No. Credits pay for Convika's built-in AI, which writes pages inside the dashboard. When Claude writes the page and saves it through the connector, no credits are used.

My artifact is a React app. Will it work?

Convika hosts each landing page as a single HTML document, with CSS and scripts inline or loaded from a CDN. Ask Claude to convert the component to plain HTML before saving, then check the preview. Anything that needs a server, a database, or several routes needs a different kind of host.

Can I edit the page after it's live?

Yes. Ask Claude for the change, or type it into Improve with AI on the page's dashboard screen, which uses Convika's AI credits. Either way, Convika saves a new version with a preview before you publish, and you can roll back to an earlier version if an edit goes wrong.