Landing Page Prompts for Lovable: 12 Free, One per Traffic Source
Prompt builder · four steps · no account
Step 1 of 4
Which one is closest?
Building something else? Describe it to the AI generator
A landing page prompt for Lovable has to say where the visitor comes from and where the email goes. These 11 prompts name both. One of them built a capture page in a single round for 1.8 credits, and this page shows what came back, what it cost and where the generic version fails.
By Marco Kohns · Prompts written and run by us
Short answers
Short answers
Where do I start?
Landing Page + Email Opt-In if you are collecting addresses, the SEO content page if the page has to earn its own traffic. Decide by what happens after the click.
Pick by traffic source →What does a run cost?
1.8 credits
Our measured run of the email opt-in prompt: one round, no follow-up, backend provisioning included. It fits inside one day of free credits.
See the credit math →Will Lovable ask questions first?
Not on this run: the July prompt had no Before Building line yet. Every prompt here now ends with one, and on later runs it produced 2 to 5 questions before any code.
What the closing line does →Will the page rank?
Only once it is published: Lovable's docs say preview URLs are never indexable. Two prompts here exist for the copy body and the sitemap a page needs first.
Fix lines for live pages →12
Landing Page prompts in this category
↳ Copy-paste, free
1.8credits
Measured run, landing page + email opt-in
↳ 10 → 10 after 1.8 daily credits
0
Questions Lovable asked first
↳ Before writing any code
50
Upvotes since Jan 2026
↳ One per visitor, self-reported
Data basis: one run of one prompt in a fresh Lovable project on the Free plan, credits read from the balance panel after the run. The other 10 prompts are not run yet and say so on their card. Plan and credit rules from Lovable's docs, checked 22 October 2026.
Find a prompt
What happens after the click?
Cards are sorted by build order. Each says whether we ran it in Lovable, and if not, shows a question mark instead of a guess.
Showing 12 prompts
- Step 1 · Capture▲ 21
Landing Page + Email Opt-In
A single-purpose pre-launch page with one offer and one form, where the signups table accepts inserts and forbids every browser read, and UTMs are stored per signup.
Run it when: you have one offer, one action and one known traffic source.
Measured: 1.8 credits · asked 0 questions firstFull page: builder, run and launch checklistPro version adds the growth-channel instructionsUnlock - Step 2 · Be found
Small Business Website
A local service business site with home, one page per service, about and contact, where one config feeds every page and the LocalBusiness structured data.
Run it when: a local or service business needs a site search engines can read, one page per service and a contact form only the owner reads.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 1 · Capture▲ 2
Waitlist Signup Page
A pre-launch waitlist page with one concrete promise, insert-only email storage with UTM attribution, and a server function that returns only the caller's own position.
Run it when: the product does not exist yet and the page has to give a reason to believe it will.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 1 · Capture▲ 2
Lead Magnet Download Page
A gated download page for one asset: preview of the contents, email-only capture with a disclosure line, instant download, and a signed-link email that works weeks later.
Run it when: the trade is an asset for an address, and the asset has to be delivered.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 2 · Measure▲ 1
Basic Analytics for Landing Pages
First-party landing page analytics posted to your own server function: pageviews, sources, device, one conversion and a four-step funnel, read on an admin dashboard.
Run it when: before you send traffic, so the first variant has a baseline.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Be found▲ 3
Simple Sitemap & SEO Generator
Sitemap, robots.txt, titles, canonicals and structured data generated from one route registry in code, with an admin page that fetches each route and flags mismatches.
Run it when: the page has a URL you will share and want indexed.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Be found
SEO Content Landing Page Generator
A long-form page built for one search query: the answer in the first 150 words, question-phrased H2s, a worked example, FAQPage schema and a calculator capture.
Run it when: the page has to earn its own traffic from search.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Be found▲ 2
Simple Press Kit Page
A public /press page served from tables: dated facts, quotes shown only when marked cleared, downloadable assets with dimensions, a ZIP of everything and a press contact.
Run it when: journalists or partners need assets and facts on one URL.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 4 · Convert
Pricing Page with Tier Comparison
A pricing page for two or three plans that reads prices and limits from the same plans table the product enforces, with a monthly and annual toggle and FAQ schema.
Run it when: the plans are decided and the page has to explain the difference.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 4 · Convert▲ 6
Landing Page A/B Variant Generator
Two-variant testing on a live landing page: one changed block, cookie-stable assignment, per-variant conversion events and a results view that waits for 300 visitors per variant.
Run it when: traffic and measurement both exist and the offer needs a test.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Standalone▲ 12
Event Countdown Landing Page
A dated event page whose countdown, calendar links and live and replay variants all run from one UTC timestamp, with an insert-only reminder signup table.
Run it when: a date is fixed and the page is the reminder.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock
Building the whole funnel? The bundle has all 12 as one kit in build order, with every Pro version unlocked, plus 140 more prompts.
See what is in the 152-prompt bundleDisclosure: if you create a Lovable account through links on this page, we may earn a commission. It costs you nothing and does not change what we recommend.
Measured run
We ran the email opt-in prompt in a fresh project. This is what happened.
▍Context
Build a single-purpose landing page: capture an email address before a product launches. The visitor arrives from one known traffic source, so the page carries one offer and one action, and nothing that competes with them.
▍Core Features
1. Hero: the offer in one sentence, the form visible without scrolling
2. Email capture writing to Supabase with UTM parameters stored per signup
3. Inline success state replacing the form, no redirect, no alert
4. Duplicate handling: resubmitting the same address confirms instead of erroring
▍Capture & Consent
- Client and server-side email validation; the server is the one that counts
- Store source, utm_source, utm_medium, utm_campaign and referrer on every row
- One-line consent text under the form stating what will be sent and how to leave
▍Safe-Guard Instructions
- The signups table accepts inserts and forbids reads from the client, with no exceptions for debugging
- No second call to action anywhere on the page
▍Distribution hooks · Pro
Locked. The Pro version adds the growth-channel instructions for this screen.
- 01
Pasted unedited into a fresh project
Free plan, no template, no knowledge file. The prompt at the time had no Before Building line, so Lovable asked nothing.
- 02
Lovable enabled the backend on its own
Its completion card reads Enabled backend and built page: a signups table arrived with the page, write-only from trusted server code.
- 03
One round, no follow-up message
Every one of the 5 priority features was present on the first build, including the consent line under the form.
- 04
The placeholder rule held
Proof elements came back marked as placeholders. No invented names, no invented numbers, which is the failure the prompt was written to prevent.
- 05
Test submission, then the success state
The form was replaced inline by a confirmation, with no redirect and no alert dialog.
- 06
Balance read: daily credits 3.20 of 5 left
1.8 credits for the whole run, backend provisioning included. The 10 bonus credits on the account were not touched.




Credit math
What 1.8 credits means on your plan
Lovable prices Build mode by the work done and says many requests cost less than one credit. A capture page with a backend is a small build; treat our figure as one data point.
| Plan | Daily build credits | One capture page run (1.8) | Unused credits |
|---|---|---|---|
| Free | 5 a day, max 30 a month | Fits in one day with 3.2 daily credits left, which is what happened. Two pages this size fit in a day. | Daily credits do not roll over |
| Pro | 5 a day, plus 100 monthly plan credits from $25 | All 1.8 from the day's credits; plan credits untouched | Plan credits roll over, expire after 2 months |
| Business | 5 a day, plus 100 monthly plan credits from $50 | Same as Pro | Same as Pro |
Lovable's own examples, for scale
- “Make the button gray”
- 0.50
- “Remove the footer”
- 0.90
- “Add authentication”
- 1.20
- Build a landing page with images
- 2.00
Source: Lovable docs, Credits and usage, marked illustrative there. Checked 22 October 2026.
Three ways to spend less
- Name the capture path in the prompt. A form with nowhere to write is a second message. Our run got the table, the validation and the duplicate rule in one because they were listed under their own heading.
- Give it placeholders for proof. Lovable will otherwise invent testimonials you then have to remove. The prompt's placeholder rule saved that round.
- Publish before you judge indexability. Checking a preview URL in Google tells you nothing; the docs say previews never index. Run the in-editor SEO review after publishing instead of re-prompting.
Start here
Which landing page prompt should you run first?
Pick by what happens immediately after the click.
Capture first, then measure
- 01Landing Page + Email Opt-In · one offer, one action, UTMs per row
- 02Waitlist Signup Page · the reason to believe it will ship
- 03Basic Analytics for Landing Pages · a baseline before the first variant
Build order
Four steps. Capture before you measure, measure before you test.
01
Capture
Opt-in · Waitlist · Lead magnet
The page and the form together. Building the form after the layout is what produces a hero with nowhere for the address to go.
02
Measure
Basic landing analytics
Instrument before you drive traffic, so the first variant has a baseline to beat.
03
Be found
Sitemap · SEO content page
Canonicals, titles and a sitemap. Cheap now, expensive once URLs are shared. Then publish.
04
Convert
Pricing · Proof · A/B variants
What the visitor decides. Only worth a prompt once traffic and measurement exist.
Anatomy
What each section of a landing page prompt does
| Section | What it tells Lovable | What you get without it |
|---|---|---|
| Context | One offer, one action, and the traffic source the visitor arrives from | A generic hero, three feature cards and a footer |
| Core features | Hero and form first, copy body last, numbered | Sections in whatever order the model prefers |
| Capture & consent | Where the address goes, server-side validation, UTM columns, the consent line | A form that submits to nothing, or a table the browser can read |
| Copy & conversion | One accent colour, placeholder rule for proof, line length | Invented testimonials and logo strips |
| Build order | Static copy first, so something exists to index | Analytics and SEO retrofitted onto markup that cannot carry them |
| Safe-guards | Insert-only table, no second CTA, keep typed input on error | A second button competing with the first |
| Before building | Ask questions first, save answers to project knowledge | Guesses about the offer and the audience |
A one-line prompt gets you
- A hero, three cards and a footer that convert nothing
- A form with nowhere to write
- Testimonials that never happened
- A preview URL that will never index
A prompt from this page gets you
- One offer, one action, shaped by the traffic source
- An insert-only table with UTMs and a consent line
- Placeholders where proof belongs
- A copy body that can rank once published
Fixes
Where landing page prompts go wrong, and the line that fixes it
Already built a page that looks finished and converts nothing? Paste the fix line into your existing project.
Symptom
The form submits and nothing is stored
Cause: the prompt described a form and never said where the address goes, so Lovable built the input and not the path.
Fix line
Create a signups table with email, source, campaign and created_at. Insert from server code only, validate the address server-side, treat a duplicate as a silent success. The browser never reads this table.
Symptom
Testimonials from people who do not exist
Cause: social proof was requested without a placeholder rule, so the model wrote plausible names.
Fix line
Replace every testimonial, logo and number on this page with a clearly marked placeholder. Do not invent names, companies or figures anywhere.
Symptom
Google cannot find the page
Cause: the page was checked at its preview URL, and Lovable's docs say preview URLs are never indexable.
Fix line
Add a title, meta description, canonical URL and a sitemap entry for this page. Then I will publish and run the SEO and AI search review in the editor.
Symptom
The hero could belong to any product
Cause: the prompt named neither the traffic source nor the single action, so the page serves everyone and nobody.
Fix line
This page receives visitors from [source]. Rewrite the hero for that visitor: one headline that states the offer, one action, and remove every other call to action.
Upvotes
Which Landing Page prompts do builders upvote?
Upvotes since January 2026, one per visitor. The email opt-in prompt is the second most upvoted in the whole library, which is why it was the one we ran.
- Landing Page + Email Opt-In21
- Event Countdown Landing Page12
- Landing Page A/B Variant Generator6
- Simple Sitemap & SEO Generator3
- Simple Press Kit Page2
- Waitlist Signup Page2
The Complete Lovable Bundle
All 11 landing page prompts in build order, plus every other prompt
Every prompt and kit, every Pro version unlocked. One payment, no subscription.
One payment. No subscription, no renewal, ever.
FAQ
Questions about Landing Page prompts
Are these Lovable landing page templates or prompts?+×
Prompts. Each one is the instruction you paste into Lovable, which generates the page inside your own project with your stack and styling. The free build kits on the templates page are the download option, and the landing page kit there ships the insert-only schema with its verification queries.
How many credits does a landing page cost in Lovable?+×
Lovable publishes no per-prompt figure and bills Build mode on the work done; its own illustrative example for a landing page with images is 2 credits. Our two measurements: the email opt-in prompt cost 1.8 credits in one round on 31 July 2026, and the six-section SaaS landing page prompt cost 4.5 credits on 26 September 2026 after 5 pre-build questions. Both fit inside the Free plan's 5 daily credits.
Should I prompt the whole page at once or section by section?+×
Lovable's own prompting guide says a full-page prompt gets you noise and a section-based prompt gets you signal. The prompts here are one message each, but every one carries a build order inside it, which is what makes a single paste behave like a sequence: static copy first, then the form, then analytics.
Can the page send the confirmation or download email itself?+×
Only on a paid plan with a verified email domain, per Lovable's prompt library page. The waitlist and lead magnet prompts confirm on the page first and treat the email as a second copy, so the first build works before email is set up.
Can I take payments on a landing page built this way?+×
Yes, two ways per Lovable's docs read on 22 October 2026. Built-in payments through Paddle or Stripe need a Pro plan or higher; connecting your own Stripe account needs no paid plan and stores the key as a secret. The pricing page prompt here inherits whichever path you pick the moment a plan button does more than open a form.
Will a landing page built in Lovable rank in Google?+×
Once published, and only then: Lovable's SEO documentation says only publicly published apps are indexable and workspace previews never are. The SEO content page and sitemap prompts produce the on-page half; the editor's SEO and AI search review is the check that counts, because on projects created before 13 May 2026 a plain fetch of the page does not show what crawlers receive.
How much should I change before pasting?+×
The audience, the offer and the traffic source, always. Those three lines change which sections Lovable prioritises more than anything else in the prompt. The structural sections can stay as written, and the closing Before Building line makes Lovable ask about anything it still needs.
What we have not tested yet
- The other 10 prompts in this category. Their cards show a question mark until we run them.
- Conversion rates of the generated pages. The run built a page; nobody sent traffic to it.
- The same capture prompt with and without the Before Building line, side by side.
- Runs on Bolt, v0 or Base44. Only Lovable runs are ours.
Next run: Waitlist Signup Page, the second capture prompt in the build order. How we test prompts
Who wrote this
Marco Kohns wrote and ran these prompts. Lovable Prompts is independent and not affiliated with Lovable.
“Try in Lovable” links are affiliate links: we may earn a commission when you create an account through them. The Pro versions and the bundle are our own paid products. Neither decides which prompt we tell you to start with.
Related reading
- the email opt-in prompt, run and measured · 1.8 credits, one round, screenshots.
- Lovable pricing and credits · Plans read today and what one prompt costs in credits.
- the landing page build kit · Prompt, insert-only schema and verification queries.
- getting the first 100 users · One channel, the matching playbook.
- SaaS prompts for what comes after the capture · Auth and roles once the list exists.
- UI prompts for the states a page needs · Empty, loading, error, named per screen.
- the mistakes that cost rebuild rounds · Invented proof is number five.
- Lovable vs Bolt · What each meter counts.
- Lovable SEO, measured on our own site · Pre-rendering, SSR and a before-and-after from Search Console.
- vibe coding prompts · The waitlist and paid-landing prompts in short form.
- Lovable and Stripe, in the SaaS guide · What a $29 sale costs on Stripe and on Paddle via Lovable.
- Lovable vs v0 · Where a Next.js landing page from v0 differs from Lovable's.
- app ideas · Fifty ideas from the library, grouped by channel.
- SaaS landing page prompt · The SaaS landing page as a six-section prompt, run and checked.
- MVP examples, measured · The July run as an MVP example, with the famous three sourced.
- CRM app prompts · The public lead form that writes into a CRM, insert-only.
- Lovable prompt generator · Writes a structured prompt for an idea that matches no library entry.
- the email opt-in prompt, with its builder and run · Fill 3 fields, copy, paste; 1.8 credits unedited.
- the bundle · All 11 landing page prompts with their Pro channel versions, plus every other prompt and kit.
Other prompt categories
Sources
- Lovable docs: Prompting best practices
- Lovable docs: Landing page use case
- Lovable docs: Prompt library (plan requirements for app emails)
- Lovable docs: Optimize your app for SEO and AI search
- Lovable docs: Add payments to your app
- Lovable docs: Stripe connector
- Lovable docs: Credits and usage
All read on 22 Oct 2026.