Landing page prompts for AI app builders: v0, Lovable, Bolt, and Replit Agent

"Make it modern and clean" is the most common landing page prompt ever pasted into an AI app builder, and it produces the most common-looking landing pages on the internet. The tools are not the problem. v0, Lovable, Bolt, and Replit Agent will all follow real design direction — border weights, type scale, spacing rhythm, section order — the moment a prompt actually supplies it.

That is what every prompt below does. Each one specifies the section anatomy, the content skeleton, concrete spacing, responsive behavior, and an acceptance check the tool can verify its own output against. The parts that should vary — visual style, color direction, type pairing, motion level — are dropdowns in the customizer on each page, and each dropdown option substitutes a full specification block, not an adjective. Choosing "Neo-brutalist" injects border widths and shadow offsets; choosing "Scroll-driven parallax" injects layer ratios and a reduced-motion fallback.

A note on how to use these: paste the prompt as your first message in a fresh session, not as a correction halfway through. App builders commit to layout decisions early, and steering an existing generation toward a different visual system is much harder than starting from a complete spec.

v0 landing page prompts

v0 responds best to prompts that treat the page as a set of components. These prompts split the page per section so you can regenerate the hero without touching the footer.

v0 prompt for a hero section — This v0 prompt generates a drop-in hero component with a fixed anatomy: eyebrow, two-line headline, mechanism subhead, button pair, one proof element, and a screenshot slot.
v0 prompt for a testimonial section — A v0 prompt for a testimonial wall: a masonry grid of attributed quote cards with one featured pull-quote, where carousel behavior exists only as the mobile fallback.
v0 prompt for an FAQ section — This prompt gets v0 to build a FAQ accordion on shadcn's Radix primitive, so keyboard and ARIA behavior arrive correct instead of hand-rolled.
v0 prompt for a portfolio website — This v0 prompt turns a portfolio into six regenerable components, with the work grid's hover states specified down to the outcome-line reveal.
v0 prompt for a waitlist landing page — This v0 prompt builds a waitlist page as five small React components, so the form or hero can be regenerated without redoing the page.
v0 prompt for a SaaS landing page — This prompt makes v0 generate a nine-section SaaS landing page as separate React components, so you can regenerate the hero without losing the pricing section.
v0 prompt for an agency landing page — A v0 prompt for a portfolio-forward agency landing page, built as seven regenerable React components from nav to contact footer.
v0 prompt for an ecommerce landing page — A v0 prompt for a single-product landing page built from seven independent components, from gallery and buy box to a scroll-aware sticky purchase bar.
v0 prompt for a 404 page — A 404 page prompt for v0 that outputs one drop-in not-found component: oversized numeral, wry one-liner, and three recovery paths — button, home link, and search.
v0 prompt for a pricing section — This prompt makes v0 generate a three-tier pricing section that slots into an existing landing page, with a billing toggle and one clearly recommended plan.
v0 prompt for a bento grid section — This prompt has v0 generate a six-cell bento grid as a drop-in section: a 2x2 flagship capability, two stats with different units, a workflow strip, a quote, and a quiet see-it-live card.
v0 prompt for a footer section — A footer is the last thing a visitor sees, and this prompt makes v0 treat it that way: a newsletter band, link columns derived from the product, a legal row, and an optional oversized wordmark.
v0 prompt for an animated hero background — This v0 prompt builds only the background layer — a drop-in client component that slots behind an existing hero and picks gradient mesh, particles, or geometric drift to match the chosen style.
v0 prompt for a feature grid section — This prompt gets v0 to build a disciplined feature grid: same-span, equal-height cards driven by a features array prop, a benefit-first copy formula, and strict icon rules.

Lovable landing page prompts

Lovable builds the page as part of a working app, which makes it the right tool when the landing page has a live job to do — a waitlist form that actually stores signups, an ecommerce page with a real cart.

Lovable prompt for a hero section — A Lovable-specific hero brief that builds a left-aligned stack — pill, verb-first headline, wired CTA, trust line, and a short media band — sized to fit a 768px-tall screen.
Lovable prompt for a testimonial section — This brief has Lovable build a three-layer proof section — logo strip, featured quote, then a nine-card testimonial wall — backed by structured data.
Lovable prompt for an FAQ section — A brief that turns Lovable's FAQ section into objection handling: seven questions derived from what stops visitors signing up, each answered with a concrete fact.
Lovable prompt for a portfolio website — A Lovable portfolio prompt that treats the contact form as the product: submissions land in a messages table with budget and project type, ready to triage.
Lovable prompt for a waitlist landing page — A Lovable prompt for a pre-launch page that stores signups in a real database table, not a dummy form.
Lovable prompt for a SaaS landing page — A single message that has Lovable build a full SaaS marketing page with a working email-capture form wired to its built-in database.
Lovable prompt for an agency landing page — This Lovable prompt produces an agency landing page with a contact pipeline that actually works: validated form, database-stored submissions, email notification, then deploy.
Lovable prompt for an ecommerce landing page — This Lovable prompt builds a one-product landing page with measurable conversion wiring: buy clicks logged to the database, an email capture that stores addresses, and a deploy at the end.
Lovable prompt for a 404 page — This prompt turns Lovable's 404 into a diagnostic tool: every dead-end hit gets logged to a broken_links table, and a one-field report form flags the worst offenders.
Lovable prompt for a pricing section — A section-scoped brief that has Lovable insert three pricing tiers into a page it already built, wired to a working signup action.
Lovable prompt for a bento grid section — A Lovable brief for a five-cell bento section that slots under an existing hero: a 2x2 anchor capability, a tall metric card, two one-sentence features, and a wired action card.
Lovable prompt for a footer section — Lovable prompt for a footer section you can copy in one click. Customize it in your browser and paste it into Lovable. Free, no signup.
Lovable prompt for an animated hero background — A Lovable prompt that layers an animated background behind a hero you already built, without touching its copy, buttons, or forms.
Lovable prompt for a feature grid section — Lovable prompt for a feature grid you can copy in one click. Customize it in your browser and paste it into Lovable. Free, no signup.

Bolt landing page prompts

Bolt scaffolds a runnable project in the browser, so these prompts lean on file structure and the instant preview loop: generate, look, tighten one section, repeat.

Bolt prompt for a hero section — Built for Bolt's instant preview loop, this prompt scaffolds a centered hero as a single new file with an explicit 720px height budget broken down element by element.
Bolt prompt for a testimonial section — A Bolt prompt that scaffolds a testimonial wall from a twelve-entry data file, with a falsifiable headline claim and a no-autoplay mobile carousel.
Bolt prompt for an FAQ section — Paste this into Bolt to add a grouped FAQ accordion — "Before you start" and "Once you're in" — rendered from a single data file.
Bolt prompt for a portfolio website — This Bolt prompt builds the portfolio around a data file: six project objects render the work grid, so updating your work never touches markup.
Bolt prompt for a waitlist landing page — This Bolt prompt scaffolds a flat, runnable waitlist project with the form logic isolated in one file, so the localStorage stand-in can be swapped for a backend later.
Bolt prompt for a SaaS landing page — Paste this into Bolt and it scaffolds a Vite + React landing page with every string extracted into one content file, so copy edits never touch markup.
Bolt prompt for an agency landing page — A Bolt prompt that scaffolds an agency site as a runnable Vite project, manifesto-first instead of hero-first, with one file per section rendering live in the preview.
Bolt prompt for an ecommerce landing page — A Bolt prompt that scaffolds a product landing page where all copy lives in one data file — change the price once and both buy points update.
Bolt prompt for a 404 page — A single-viewport 404 for Bolt with a fake command line that types "searching for page...
Bolt prompt for a pricing section — Drop this into Bolt to add a data-driven pricing section to a landing page without creating a separate route.
Bolt prompt for a bento grid section — This Bolt prompt splits a bento section into a typed data file and a renderer, so cell copy stays editable without layout risk — a structure Bolt scaffolds cleanly and hot-reloads instantly.
Bolt prompt for a footer section — Bolt scaffolds this footer as its own file in the project tree, so it stays maintainable instead of rotting at the bottom of a page component.
Bolt prompt for an animated hero background — This Bolt prompt adds the background layer only — one new file mounted under an existing hero, with the technique chosen to match your selected style.
Bolt prompt for a feature grid section — This prompt makes Bolt scaffold the feature grid as two files — copy in a data file, layout in a component — so tuning benefit lines never risks the markup.

Replit Agent landing page prompts

Replit Agent plans before it builds. These prompts are written so the plan it proposes is already the page you want — section list, copy skeleton, and checks included — and hosting is one click after.

Replit Agent prompt for a portfolio website — A Replit Agent portfolio prompt built for the plan-first workflow: the section map and file layout get approved before any code is written.
Replit Agent prompt for a waitlist landing page — A Replit Agent prompt that forces a plan — route, storage, sections — before any waitlist code gets written.
Replit Agent prompt for a SaaS landing page — This prompt makes Replit Agent propose a section plan for your approval before building, then deploy the finished SaaS page to a live URL.
Replit Agent prompt for an agency landing page — This prompt has Replit Agent plan an agency landing page before building it, then host the result on a public URL.
Replit Agent prompt for an ecommerce landing page — This prompt makes Replit Agent plan a single-product landing page, build it, and host it — with an objection row answering buyer hesitations before the benefit sections.
Replit Agent prompt for a 404 page — This prompt makes Replit Agent pitch three 404 headline directions before building, so you choose the voice instead of accepting a first draft.

Pages versus sections

The full-page prompts above ship a complete landing page in one paste. The section prompts (hero, pricing, bento grid, testimonial wall, footer, and the rest) exist because the second week of a landing page's life is section-by-section: the page converts, but the pricing section is weak, or the hero needs a rebuild for a new positioning. Running a section prompt inside an existing project is faster and safer than regenerating the page — and every section prompt states how to slot into surrounding markup without breaking it.

If you use a different tool, the same prompts exist for Cursor and Claude Code as part of each tool's prompt directory, and every page above links to its equivalents across tools.