Lovable prompts to build and iterate landing pages

Build the hero for [PRODUCT NAME]. Headline I approve: [HEADLINE]. Subheadline I approve: [SUBHEADLINE]. Primary button label and target: [PRIMARY CTA]. Visual notes: [VISUAL NOTES]. Use only that copy. If the subheadline is blank, write [VERIFY] in that slot and do not invent a promise. Do not invent a user count, a rating or a conversion rate. Layout: headline, subheadline, one button, optional image area labelled with [IMAGE BRIEF] or an empty frame if the brief is blank. No second button unless I set [SECONDARY CTA].

Give me three hero headline options for [AUDIENCE] about [PRODUCT NAME]. Each option must rephrase [APPROVED HEADLINE] without adding a claim. Under each, write a 20 word subheadline that only uses facts in [APPROVED FACTS]. If a fact needed for a subheadline is missing, write [VERIFY] in that option instead of stretching. Do not invent a result, a number or a famous customer. Output a table with columns Option, Headline, Subheadline. Then pick one and say why in 30 words, still inside the facts.

Set the primary and optional secondary calls to action for this landing page. Key action: [KEY ACTION]. Primary label I approve: [PRIMARY LABEL]. Secondary, if any: [SECONDARY LABEL]. Destinations: [DESTINATIONS]. Place primary on the hero and again above the footer. If secondary is blank, do not invent one. If a destination is missing, write [VERIFY] on that button and do not link to a made-up route. Do not invent a discount, a trial length or a conversion rate. Describe the two placements, then apply them.

Add a waitlist form to the hero for [PRODUCT NAME]. Fields I want: [FIELD LIST]. Submit label: [SUBMIT LABEL]. Success message I approve: [SUCCESS MESSAGE]. Store submissions with the built-in database. If [FIELD LIST] is blank, use email only and write [VERIFY] beside any other field you were tempted to add. Do not invent a company size field, a phone field or a conversion rate. Do not add a second form lower on the page unless I ask. Show empty, error and success states.

Replace the hero media for [PRODUCT NAME]. Brief: [IMAGE BRIEF]. Product shots I actually have: [ASSET NOTES]. If I have no asset, use an abstract background that matches [TOKEN SUMMARY] and a caption [VERIFY] so I remember to drop a real shot later. Do not generate a person, a celebrity likeness or a fake UI screenshot that shows invented metrics. Do not invent a conversion rate on a badge. Keep the heading copy unchanged: [HEADLINE]. Apply the media and describe what you used in three bullets.

Build a social proof bar under the hero. Names I may show: [LOGO OR CUSTOMER NAMES]. If the list is empty, do not build the bar; write [VERIFY] and stop. Use text names, not invented marks. Do not invent a company, a user count or a conversion rate. Caption I approve, or none: [CAPTION]. Layout: a single quiet row. If I listed more than eight names, use the first eight and list the overflow for me. Do not add stars or ratings.

Create a proof section with quote cards. Quotes I approve, word for word: [PASTE QUOTES WITH ATTRIBUTION]. One card per quote. If attribution is missing on a quote, put [VERIFY] where the name would go and still show the quote. Do not invent a role, a company, a photo or a conversion rate. Do not paraphrase. If I pasted no quotes, do not build this section; tell me and stop. Max four cards. Match [TOKEN SUMMARY].

Build a How it works section with exactly three steps for [PRODUCT NAME]. Steps I approve: [THREE STEPS]. Each step: title of at most five words, body of 20 to 30 words, no invented icons of people. Use only the step text I gave. If a step is missing, write [VERIFY] in that column and still keep three columns. Do not invent a result, a time saved or a conversion rate. Do not add a fourth step. Place this section where the brief says: [SECTION POSITION].

Build a two-column section: problem for [AUDIENCE] and outcome after [KEY ACTION]. Problem copy I approve: [PROBLEM COPY]. Outcome copy I approve: [OUTCOME COPY]. Do not invent a metric in the outcome. If the outcome copy lacks a concrete change I can defend, put [VERIFY] at the end of that column. Do not add photos of people. Do not add a conversion rate. Keep each column under 80 words. Place it after [PREVIOUS SECTION].

Add an FAQ accordion near the footer. Questions and answers I approve: [PASTE FAQ PAIRS]. Use my wording. If an answer is missing, show the question with [VERIFY] as the answer so I can fill it later. Do not invent a question, a price, a plan name or a conversion rate. Limit to eight pairs. If I pasted none, do not build the accordion; tell me which three questions I should answer from [PRODUCT NAME] without writing those answers.

Build an offer comparison table from tiers I already sell. Tiers: [TIER NAMES AND INCLUDED ITEMS]. Do not invent a tier, a limit or a conversion rate. If a cell lacks an item, write [VERIFY] rather than filling it with a guess. Highlight the tier I name as [FEATURED TIER], or none if that is blank. Buttons: [TIER DESTINATIONS]. If a destination is missing, the button label stays but the target is [VERIFY]. This is a comparison table, not a shop. Match [TOKEN SUMMARY].

I sell one offer. Build a single offer block, not a multi-column grid. Offer name: [OFFER NAME]. What it includes: [INCLUDED ITEMS]. Who it is for: [AUDIENCE]. Button: [PRIMARY CTA]. Do not invent a second tier, a discount or a conversion rate. If includes is thin, write [VERIFY] as a last bullet instead of padding. Do not show a comparison. Place the block where [SECTION POSITION] says. Keep the copy under 120 words plus the button.

Add a contact form whose only job is [FORM JOB]. Fields: [FIELD LIST]. Submit label: [SUBMIT LABEL]. Notify me at [NOTIFY EMAIL] if that is filled, otherwise write [VERIFY] in an on-page note and still save to the built-in database. Do not invent a budget field, a file upload or a conversion rate. Empty, error and success states required. Success copy: [SUCCESS MESSAGE]. Place the form in [SECTION NAME] only.

Audit the form in [SECTION NAME]. Current fields: [CURRENT FIELDS]. Fields we actually use after submit: [USED FIELDS]. Remove every current field not in the used list. Do not add new fields. If [USED FIELDS] is empty, do not remove anything; write [VERIFY] and list the current fields for me to tick. Do not invent a reason a field is required. Do not mention conversion rates. After the change, show the remaining fields and the three states still working.

Add one legal line under the primary form button. Text I approve: [LEGAL LINE]. Link targets I approve: [POLICY URLS]. If a URL is missing, keep the line and put [VERIFY] on that link rather than inventing a policy page. Do not invent a guarantee, a refund or a conversion rate. Do not add a second paragraph. Font size smaller than the button, still readable. If [LEGAL LINE] is blank, do not write one; stop and ask me for the sentence our counsel already uses.

Rewrite the copy in [SECTION NAME] for [AUDIENCE]. Current copy: [PASTE CURRENT COPY]. Facts you may keep: [APPROVED FACTS]. Produce a new heading, a new body under 80 words, and the same buttons. Do not invent a proof point, a number or a conversion rate. If the current copy contains a claim not in [APPROVED FACTS], drop it or mark it [VERIFY] in a note above the section, then omit it from the visible copy. Apply the rewrite only in that section.

Create a second landing page variant for [SECOND AUDIENCE] by duplicating this page's structure. Shared facts: [APPROVED FACTS]. What changes: [WHAT CHANGES]. Keep the same sections and tokens. Do not invent a case study, a logo or a conversion rate for the new audience. If a section has nothing true to say to them, leave the heading and put [VERIFY] in the body. Tell me the new route you created. Do not delete the original page.

The [SECTION NAME] section feels noisy. Current contents: [PASTE SECTION CONTENTS]. Keep at most [MAX ITEMS] items. Delete the rest, do not hide them with CSS. Do not replace deleted items with new invented ones. If I did not say which items to keep, pick the ones that support [KEY ACTION] using only [APPROVED FACTS], and list the deleted items for me. If that choice needs a fact I did not give, write [VERIFY] and do not delete yet. No conversion rates.

Fix heading hierarchy on this landing page. Current outline: [PASTE OUTLINE OR DESCRIBE]. The page title is [PAGE TITLE]. There must be one h1, then h2 per section, then h3 only inside a section that already has an h2. Do not change the words except to split a heading that is really two sentences. Do not invent a section to fill a gap. If a section has no heading, write [VERIFY] as a placeholder h2 I must supply. Then apply the outline.

List every button and link labelled as a button on this landing page. For each, write: current label, destination, and whether it matches [KEY ACTION]. Propose a new label only when the current one is vague, using words from [APPROVED CTA WORDS]. If a destination is unknown, write [VERIFY] and do not invent a route. Do not invent a conversion rate to justify a label. After the table, apply the label changes I would accept from that table, and list any you left because of [VERIFY].

Restack this landing page for a small screen. Breakpoint to care about: [MOBILE BREAKPOINT]. Rules: one column, buttons full width, type still from [TOKEN SUMMARY], no horizontal scroll. Do not remove sections. Do not invent a mobile-only offer, a conversion rate or a new image of a person. If a section needs a shorter heading and I did not give one, write [VERIFY] above that section instead of inventing a tighter line. Describe the five largest mobile changes, then apply them.

Set the page title and meta description from copy I already approved. Title pattern: [TITLE PATTERN] using [PRODUCT NAME]. Description: 140 to 160 characters, facts from [APPROVED FACTS] only. If a fact needed for the description is missing, write [VERIFY] in the description field rather than inventing a claim. Do not invent a conversion rate or a slogan. Do not change on-page headings. Show me the title and description, wait for yes, then apply.

Add empty, error and slow states for the form in [SECTION NAME]. Empty: [EMPTY HINT]. Error: [ERROR MESSAGE]. Slow: a disabled button and [SLOW MESSAGE]. Use my messages. If a message is blank, write [VERIFY] on that state and still implement a simple default that says try again, without inventing a cause. Do not invent a conversion rate, a ticket id or a phone number. Keep the three states visually quiet. Show me each state in notes, then apply.

Walk a launch checklist for this landing page. Items I require: [CHECKLIST ITEMS]. For each, mark done, not done or [VERIFY] from what you can see in the project, not from hope. Do not invent a DNS record, a domain or a conversion rate. If an item needs a fact outside the project, mark [VERIFY] and tell me what to paste next. Output a table, then the three not-done items in an order I should fix. Do not change the page until I pick an item.

Scan this landing page for leftover mock content. Mock means names, quotes, numbers, logos or cities that are not in [APPROVED FACTS] and not in [ASSET LIST]. List each leftover with the section it sits in. Replace visible leftovers with [VERIFY] placeholders I can fill, or delete the block if I set [DELETE MOCKS] to yes. Do not invent replacements. Do not add a conversion rate while cleaning. Show the list first, wait if more than five items, otherwise apply the replacements.