How to Create a Landing Page in 60 Seconds
Here is how to create a landing page in 60 seconds: two ways in the browser, one from the terminal, each ending with a live URL.
The fastest path is not a template gallery. It is a .page file and Publish.
Option 1: Prompt it
Go to app.micropage.sh, create a project, open the AI tab, and describe the page. Example:
Waitlist for Harbor, a backup tool for Notion. Friendly, technical, one email field, three dummy price tiers.
You get markup you can edit. The AI tab writes into the same .page file you are already editing — review the result, then apply it to the source pane or discard it. The Free plan includes an AI credit that refills each calendar month, so this path is not locked behind a card. When the month’s credit runs out the AI tab asks you to upgrade; nothing else locks. You can keep typing markup and publishing.
Option 2: Paste this and publish
Same editor, source pane:
[site]
title: Harbor
description: Nightly backups for your Notion workspace
[Home -> /]
/// hero
h1: Launch the waitlist tonight
p: A page you can edit like Markdown and publish without a builder account.
button: Join the list -> /#waitlist
/// section
form: waitlist
input: Email*
submit: Get early access
Click Publish. The site is live on its *.micropage.sh URL, which sits in the editor’s top bar from the first publish onward.
Option 3: CLI (Pro)
npm install -g @micropage-sh/cli
micropage login
micropage projects create harbor
# edit the generated .page file
micropage publish
micropage preview
micropage push only saves a draft build. micropage publish is the one that deploys.
What you just used
[site]for metadata- a hero
- a form that stores submissions after publish
That is a real page. Not a preview of a page.
What you get after Publish
A live URL over HTTPS. A *.micropage.sh host, no DNS to configure and no certificate to manage. Save creates a draft build and leaves the live URL untouched; Publish is the verb that moves it.
Static HTML. The markup is parsed into JSON, generated as a static site, and served from Cloudflare’s network. Nothing renders at request time.
A form that works immediately. Submissions land in the Form Submissions tab from the first publish — no backend, no third-party form service. A hidden honeypot and server-side validation (only fields declared in your markup are accepted) filter the obvious junk, and there is a no-JavaScript fallback so the form still submits with scripts off. Free accepts 100 submissions a month.
SEO tags you didn’t write. Meta description, canonical, Open Graph and Twitter Card tags, theme-color, and a JSON-LD WebSite block, derived from your [site] title and description.
sitemap.xml and robots.txt. The sitemap carries one <url> entry per page, each with the deploy timestamp as <lastmod>. Pages marked noindex: true, and pages whose canonical points at a different host, are excluded — so the file above produces exactly one entry. robots.txt allows everything and links the sitemap.
A rollback. Each publish is a numbered build. Redeploy an older one from the Builds tab and that version goes live again.
On Free you get one project and the page carries a Micropage badge. Plans and what each one unlocks.
Then what
Point your own domain at it. Custom domains are a Pro feature. Enter the subdomain in Settings → Custom Domain, CNAME it to cname.micropage.sh — not to your project’s *.micropage.sh host — and the editor walks from Waiting for DNS through TLS issuance to Live. Apex domains can’t be attached; redirect example.com to www.example.com at your DNS provider. Full walkthrough: connect your own domain.
Add pages. A second route is another block in the same file:
[Pricing -> /pricing]
/// section
h2: Plans
Nav entries, a footer, per-page meta: overrides — same file, no restructuring. Nothing you did in the first 60 seconds has to be undone to get there.