Skip to content
Lemnigent

Blog,

Ship a lead page for the price of a domain

Build, test and host a fast landing page on Cloudflare with Astro, React, Tailwind and shadcn/ui, using one Claude Code prompt. Then the part that brings the leads: getting found.

A lead page has one job: turn a visitor into a booked call or a filled form. It does not need a server, a database or a monthly hosting bill. This is how to build one with Claude Code, test it properly, and host it on Cloudflare, where serving a static page costs nothing.

This site is built the same way: Astro, React, Tailwind CSS and shadcn/ui, hosted on Cloudflare.

What you need

  • A domain, added to a free Cloudflare account.
  • Node.js on your machine.
  • Claude Code.

Why Cloudflare for a lead page

  • Static pages cost nothing to serve. On both the free and paid Workers plans, “requests to static assets are free and unlimited” (Cloudflare pricing).
  • The free plan is enough for most lead pages. It allows 20,000 files per version and 100,000 requests a day to Worker code (Cloudflare limits). A static page runs no Worker code at all.
  • One file configures it. A wrangler.jsonc points at your build folder and names your domain (static site setup).
  • You can test before you go live. Cloudflare can give each uploaded version its own preview address, and on workers.dev it marks previews as not for search engines (preview URLs).

Why this stack

  • Astro builds plain HTML pages. Search engines and AI answer engines read HTML, so a page that arrives complete is a page they can read.
  • React only where the page needs interaction, such as a pricing toggle or a multi-step form.
  • Tailwind CSS for styling without a separate stylesheet to maintain.
  • shadcn/ui for accessible components that are copied into your project, so you own and can change them.

The Claude Code prompt

Open an empty folder in Claude Code, fill in the brackets, and paste this:

Build a one-page lead site for [business name], which helps [customer] with [problem].

Stack: Astro with static output, React only for parts that need interaction, Tailwind CSS v4,
shadcn/ui. Use the official setup command for each, then read the generated config before
you change it.

The page, in this order:
1. An H1 that states the customer's problem in the words they search for.
2. Three short benefits, each with one concrete detail.
3. One proof point I can verify: [a number, a named client with permission, or a product link].
4. Five questions buyers ask, each answered in two or three sentences, with FAQPage data.
5. One action: a booking link to [URL]. No form unless I ask for one.

SEO: a title under 60 characters, a meta description under 155, a canonical URL, a sitemap,
robots.txt, an Open Graph image, and the site URL set in astro.config.

Hosting: add wrangler.jsonc for Cloudflare Workers static assets, with assets.directory
"./dist", not_found_handling "404-page" and a custom domain route for [domain]. No Worker
script. Add npm scripts: build, preview, and deploy ("wrangler deploy").

Before you finish: run the build, start the preview, check the page at 390px and 1280px wide
with no sideways scroll and no console errors, and list anything you could not verify.

The last paragraph matters most. It makes Claude Code check its own work in a browser before it calls the job done, and tell you what it could not check.

Test it before anyone sees it

  1. npm run build, then npm run preview. Open the page on a phone-sized window and a desktop one.
  2. npx wrangler dev runs the build the way Cloudflare will serve it, including the 404 page.
  3. npx wrangler versions upload puts a version on Cloudflare without making it live. With preview addresses turned on, you get a link to share with whoever signs off.
  4. npx wrangler deploy makes it live on your domain.

What it costs

On the Workers Free plan, a static lead page costs nothing to host. The domain is the only bill. If the page later needs server code beyond the free plan’s daily limit, the paid plan starts at $5 a month (Cloudflare pricing).

The part a page cannot do alone: getting found

A fast page that nobody finds books no calls. Search engines have to discover it, index it and rank it. AI answer engines such as ChatGPT, Perplexity and Gemini have to read it and choose to cite it. None of that happens because the page went live.

On channelos.tv, our own product, a set of scheduled jobs does this work:

  • Every day, changed pages go to Bing and to IndexNow, which passes them on to the search engines that take part.
  • Every day, a check reads which pages Google has indexed and which it has not.
  • Every week, the questions buyers ask go to ChatGPT, Perplexity and Gemini, and the answers are checked for whether they cite the site.
  • Every month, a report lists the searches the site already appears for but has no page for. Those become the next pages.

Each run feeds the next one: what gets cited and what people search for decides what is written next. That is the loop we set up and run for clients’ lead pages, so the page keeps working after launch day.

If you have a lead page, or need one, book a call. Thirty minutes, free, with the people who would do the work.

Tell us what you are building.

Thirty minutes, free, with the people who would do the work.

Book a call