Guide · Claude Code
Claude Code built your website. Here’s how to ship it.
You have an index.html in dist/ and no appetite for git remotes, CI, and DNS just to show someone a page. Skip the pipeline: drop the file on Pagelive, or let Claude Code publish it straight from the terminal.
Free to start · no credit card.
> take the report in dist/ and publish it
as a Pagelive page
⏺ pagelive · publish_page
✓ live → https://pagelive.site/p/k3x9m2
noindex · password optional · trackedThe 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: drop the file on Pagelive, or add the Pagelive connector and Claude Code publishes it for you.
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
Not everything Claude Code writes needs infrastructure. A lot of it just needs to be openable by another human.
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
Route one needs zero setup. Route two is a one-time setup, then publishing becomes a sentence in your session.
1 · Drop the file
Take the built HTML — dist/index.html, report.html, whatever Claude Code wrote — and drag it into the Pagelive dashboard or paste the markup. Live link in seconds: noindex by default, password optional, opens and dwell time tracked.
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
Pagelive serves self-contained HTML on purpose. It’s delivery, not infrastructure.
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 a password and view tracking
You also get what a pipeline doesn’t give you: 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
Does the Pagelive connector work in Claude Code, or only on claude.ai? +
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.
My site is several files — CSS, JS, images. Can I still publish it? +
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.
Will the page show up on Google? +
Not by default. Every published page 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.
What does publishing cost? +
Your first 10 pages are free, no credit card. Pro is $15/mo ($150/yr) and adds custom domains (5) and custom slugs; Team is $19/seat/mo with 25 domains.
From dist/ to a live link before your next compile.
Drop the file, or let Claude Code publish it — private by default, free to start.