Publish a Claude artifact on your own domain

Decide whether sharing the artifact already solves the task

Claude has its own artifact publishing and sharing features. If you need to show a concept, share an interactive explanation, or collect feedback on a draft, those options may be enough. Anthropic explains the current behavior in its artifact sharing documentation.

A business landing page creates additional questions. Do you want it on a hostname you control? Does the contact form deliver an enquiry? Can you revise the page while keeping its address? Where do the images live? Answer those questions before choosing another host.

This guide concerns a static landing-page artifact. An artifact that calls AI services, stores application data, or relies on an application runtime is not automatically portable as a single HTML page.

Inspect the output before moving it

Ask Claude to identify what it created: plain HTML, React components, or a more complex project. Keep a copy of the original so you can return to it. Then review the dependencies.

Dependency	What to establish
Images	Are they owned or authorized, and can they be hosted at durable URLs?
Fonts and styles	Can the page render without local files or a missing build step?
Form	Is there a real submission endpoint or just a visual control?
External services	Does the page require a backend, credentials, or a database?
Links	Do they work outside the artifact preview?

For Pageree, the assistant must adapt the page to one HTML document with inline CSS and JavaScript and properly hosted images. This can involve rebuilding the static layout from a React prototype. It is not an arbitrary-app importer.

Adapt the existing page, rather than regenerate the offer

Take this existing landing-page artifact and prepare it for Pageree.

First identify its format and dependencies. Keep the approved copy and overall visual direction. Explain any behavior that cannot work as a single static HTML page. Ask before removing or replacing it.

Follow Pageree's page, asset, form, privacy, and publishing skills. Replace any mock form with a real Pageree form and ask where enquiries should go. Do not embed secrets in the HTML. Save a private preview and show me the changes before publishing.

Use this request after connecting Claude. Supply approved copy and assets rather than asking the model to reconstruct details it can no longer see. If the artifact is mainly a design concept, the Claude Design handoff guide covers that starting point.

Check the adapted preview

Compare the new preview against the artifact: headline, section order, image crop, mobile layout, and primary action. Some visual differences may be necessary when replacing a prototype framework, but the visitor’s task should remain clear.

Click the links. Complete the form with test data. Ask what its draft behavior can verify and what must wait for the published page. In particular, a private preview does not establish that production analytics or an external CRM destination is functioning.

When you approve the result, publish it to the chosen Pageree address. Open that public URL independently. A local preview or an assistant’s description of a URL is not a substitute for checking the page itself.

Connect the hostname you own

Tell the assistant the exact hostname, such as a campaign subdomain of your business domain. Pageree returns the DNS record to add. Do not copy a target from an unrelated tutorial: use the value returned for your actual configuration.

Add the record at your DNS provider, check the domain status, and open the HTTPS address after it becomes active. The custom-domain guide explains apex domains and existing records in more detail.

Verify the business behavior

Submit a marked test on the published page and confirm that the final inbox or configured destination receives it. Check the required fields and error message as well as the successful case. If the button only changes the screen, use the form troubleshooting guide.

Keep the page identity for future edits. Ask Claude to revise the existing page, show a preview, and publish the approved version. That is a more reliable maintenance workflow than creating a fresh project every time the offer changes.