Guide · Claude Code
Claude Code built your website. Here’s how to ship it.
Free for 2 public pages.
> take the report in dist/ and publish it
as a Pagelive page
⏺ pagelive · publish_page
✓ live → https://pagelive.app/p/k3x9m2
noindex · view countThe short version
Claude Code websites, in one paragraph
Claude Code is Anthropic’s coding agent for the terminal, and websites are among the most common things it builds: landing pages, dashboards, reports, demos. The output is HTML, so you don’t need a deploy pipeline to ship it: upload the file to Pagelive, or add the Pagelive connector and Claude Code publishes it for you. (As of October 2026, Claude Code can also publish session output as a Claude artifact at a private URL; viewers of a shared artifact need a Claude account.)
Working in the claude.ai chat instead? See can Claude build a website: the workflow, or start at the Claude artifacts hub.
What it produces
What Claude Code builds that wants a link
One-page sites & landing pages
Marketing pages, waitlists, microsites: usually a single index.html with inline styles.
Dashboards & reports
Data pulled, charted, and written up as static HTML, ideal for a weekly client link.
Demos & prototypes
Interactive proofs-of-concept a stakeholder should click, not clone and npm install.
Client deliverables
Proposals, audits, and decks generated from your repo or data, ready to send.
Going live
Two ways to put it live: neither is a deploy
1 · Upload the file
Take the built HTML (dist/index.html, report.html, whatever Claude Code wrote) and drag it into the Pagelive dashboard. Live link in seconds: noindex by default, with a view count; Solo adds a password and reading time.
All the ways to publish artifact HTML →2 · Let Claude Code publish it
Add Pagelive as a connector (it’s MCP, so it works in Claude Code the same as on claude.ai). From then on, publish and update pages in natural language without leaving the session.
# one-time setup, in your terminal
claude mcp add --transport http pagelive \
https://app.pagelive.io/api/mcp
# inside Claude Code: authenticate once
/mcp# from then on, publishing is a sentence
> publish dist/index.html as a Pagelive page
> update the live page with the new version,
keep the same linkHonest fit
When a Pagelive link is the right call, and when it isn’t
Ship it as a Pagelive link
- ✓Static one-pagers, landing pages, and microsites
- ✓Client reports, dashboards, and audits
- ✓Demos and prototypes you want opened, not deployed
- ✓Proposals and decks that need view tracking and, on Solo, a password
You also get what a pipeline doesn’t give you: a view count on every page, and on Solo and Team who opened it, for how long, behind a password if you want one.
Use a full host or your own pipeline
- –Apps with a backend, database, or user accounts
- –Multi-route SPAs with build pipelines and APIs
- –Anything that needs server code to run
If it has a package.json that matters at runtime, it wants real infrastructure, and that’s fine.
Claude Code publishing FAQ
Both. It’s the same connector URL (app.pagelive.io/api/mcp): add it as a connector on claude.ai, or in Claude Code with claude mcp add. You authenticate once with OAuth and the publishing tools show up in either place.
A Pagelive page is one self-contained HTML file. Ask Claude Code to inline the CSS and JavaScript and reference images by URL (or as data URIs for small ones). For a multi-page site, publish each page and link between them. On a custom domain with custom slugs it reads as one site.
Not by default. Every published page, on every plan, is noindex: we send the robots signals that tell search engines not to list it. That matters for client work: most free hosts publish pages publicly where Google can index them.
Yes. As of October 2026, Anthropic says Claude Code can publish its session output as an artifact, “a live interactive page at a private URL” that updates as the session continues, and you can share it. Like other shared artifacts, viewers need a Claude account. Pagelive is for when the page should open for anyone, in any browser.
Free for 2 public pages. Solo is $15/mo ($150/yr): the whole product, including up to 5 custom domains and lead capture. Team is $49/mo per workspace, up to 10 members, with 25 domains.