Build and publish a landing page with Claude Code

Use a small project for a small campaign

Claude Code can work with the actual files behind a landing page, which makes it useful when you want a reviewable HTML source and a clear record of later edits. For a single offer, start with a small project containing the brief, approved assets, and one HTML file. A framework is optional; it should solve a real requirement before it adds a build process.

The workflow below uses Claude Code’s terminal client and Pageree’s remote MCP server. Connection instructions follow official documentation, reviewed on September 15, 2026. They are not a claim that every operating system, organization policy, or Claude account has been tested with Pageree.

Add Pageree to Claude Code

From the project terminal, configure the remote HTTP server:

claude mcp add --transport http pageree https://mcp.pageree.com/

Open Claude Code, use /mcp, and complete browser authentication for Pageree. Anthropic documents HTTP server setup and OAuth in its Claude Code MCP guide. Keep any existing MCP configuration when adding this entry; the command is an addition, not an instruction to replace your other tools.

Ask Claude to read the account and list pages. If authentication succeeds but the tools are absent, inspect /mcp before working on the HTML. A browser sign-in and a usable tool connection are separate checkpoints. The Pageree docs provide the current server details.

Give the project a concrete business job

For an illustrative example, consider a founder offering onboarding reviews to small software teams. The page needs to explain the review, show genuine work samples, and collect an enquiry. It does not need account creation or an application database.

Build a landing page in this project for my onboarding-review service.
Audience: founders of small software teams improving their first-user experience.
Offer: review one onboarding flow and deliver a prioritized written action list.
Goal: receive a project enquiry, not book an appointment automatically.
Read brief.md and the approved assets. Ask about missing scope, pricing, and proof.
Write a single index.html with inline CSS and JavaScript for Pageree.
Use hosted images through its asset tools; no local paths in published markup.
Follow the current Pageree page, form, privacy, and publishing skills.
Ask for the destination email and chosen slug, then save a private preview.
Persist the returned page ID and URL in a .pageree file. Do not publish yet.

The prompt generator can help turn your own offer into a starting brief. Remove any assertion you cannot substantiate before asking Claude to use it in the page.

Review both the source and the preview

Use the project diff to see whether Claude changed only the intended file. Check for an accidental dependency on a development server, a relative image URL, or an API credential embedded in JavaScript. Pageree saves a complete HTML document; separate CSS and JavaScript files must be inlined for this route.

Then open the private preview. Source inspection cannot tell you whether a long service name wraps badly on mobile. Check the offer, focus states, labels, link destinations, privacy controls, and the complete form response. Ask for specific fixes and keep the same page ID during each save.

When the preview is approved, publish and open the returned public URL. Submit a clearly marked test with an inbox you control and verify delivery. A form that reports success without reaching the chosen destination is still an unresolved business problem; use the form troubleshooting guide.

Make the second edit on the same page

The project file is helpful, but it can become stale if someone edits the page from another assistant. Start a later change by asking Claude to retrieve the page information and stored HTML. If an open draft exists, decide which work to continue before replacing it.

Use the page identity in .pageree. Read its current information and stored source.
If there is an open draft, show me what it contains before replacing it.
Change the primary offer from a full onboarding review to a first-session review.
Preserve the URL, delivery configuration, unrelated sections, and working form.
Save the complete revised document as a draft on the same page ID.
Show the preview and a short description of the change. Wait for publication approval.

This separates source changes from live changes. The current public version keeps serving while you review the new draft. The live-editing guide explains version history and recovery when a later change needs to be reversed.