Blog

Landing Page Forms: 7 Placement and Design Tips

By
The Reform Team
Use AI to summarize text or ask questions

Place a landing page form where visitors have enough information to act - not automatically at the top. Keep the offer, fields, and button connected, and make the form easy to complete on any screen. For longer forms, multi-step layouts can further reduce friction.

These seven tips cover the path from reading to submission:

  1. Placement: Match the form’s position to visitor intent and how much explanation the offer needs.
  2. Visual order: Guide visitors from headline to value, fields, and button.
  3. Spacing: Keep labels close to their fields and separate field groups with consistent gaps.
  4. Contrast: Make text, field borders, errors, and keyboard focus easy to see.
  5. Sizing: Fit the screen, use readable text, and aim for touch targets of at least 44 × 44 CSS pixels.
  6. Labels: Keep labels visible and arrange questions in a logical order.
  7. Button alignment: Place the button below the fields and name the next step, such as “Get the Guide.”

Treat these as starting points, not fixed rules. Test on desktop and mobile, then compare completion rates, errors, and lead quality - not just submission counts.

Landing Page Form Design: 7 Visual Tips

Landing Page Form Design: 7 Visual Tips

Match the Form to Visitor Intent

Match form friction to visitor intent. For high-intent offers like demos, place the form near the promise and proof. Lower-intent offers, such as guides or newsletters, need more context: explain the benefit and how delivery works before asking for details. For a consultation or custom quote, offer reassurance first. Explain what the conversation covers, what happens next, and whether there’s any obligation.

Match the fields to the offer and audience, too.

An email address may be enough for a resource; a webinar or trial may justify a company name or role if it changes the experience. A sales inquiry may need a timeline or service type.

Save qualification questions that aren’t needed right away for follow-up. If you ask for sensitive details, such as a phone number, explain why you need them.

Adding fields can sometimes remove friction; one test found the longer form outperformed the shorter version by 13.56%.

Before designing the form, map the path visitors will follow: Promise, benefit, proof, fields, action. Use the headline to reinforce the outcome and the button to name the next step. Visitors should know what they’ll get before they start typing.

Place the form at the point where visitors have enough context to act.

1. Place the Form Where Visitors Have Enough Context

Once visitor intent is clear, put the form where people have enough information to act. Higher-commitment offers usually need more explanation before the fields appear.

Offer or visitor context Recommended position Reason Design implication
Short, low-commitment offer or high-intent visitor Near the opening offer, often above the fold Visitors need little explanation Keep key benefits and the form together
Complex or higher-commitment offer After key benefits and trust signals Visitors need reassurance before submitting Present the offer, then the proof, then the form
Simple offer with hero copy Beside the hero copy on desktop Visitors can understand the offer and act in one view Put copy first when stacking the form on mobile

Match the placement to how much explanation the offer needs. On mobile, stack the copy above the form so visitors see the offer’s claim and supporting proof before the fields.

Use scroll depth, heatmaps, and A/B tests to compare early placement against placement after key proof. Test on both desktop and mobile, and track abandonment alongside submissions.

With placement set, the next job is making the path to design the perfect landing page form obvious.

2. Create a Clear Visual Path From Copy to Form

Once the form is in place, guide the reader’s eye from the copy to the submit button. Follow a clear order: headline, value, fields, then submit button. Use size, color, and position to make the main action stand out.

Give the form breathing room with whitespace, but keep its heading, fields, and button grouped together. Stack fields in a single column so visitors can move from top to bottom without scanning across columns.

Keep secondary links and supporting details less prominent than the submit button. Space the fields so each one is easy to scan without interrupting that top-to-bottom flow.

Quick check: At a glance, can visitors see the offer, find the fields, and tell which button submits the form?

Once the form is in place, use spacing to guide visitors from copy → label → field → submit. Keep related elements close and unrelated elements apart. Place labels above fields, help text below them, and validation messages directly under the field that needs fixing.

Follow a consistent spacing scale rather than judging gaps by eye. Start with 4–8 pixels between labels and fields and 16–24 pixels between field groups. Add more space before each new group heading so section boundaries are clear.

Error messages should help visitors fix a field without disrupting their progress. Explain what to change, and keep their entered value whenever possible. Use aria-describedby to connect help and error text to the input so screen readers announce them together.

Leave 24–32 pixels above the submit button to separate it from the last field. With spacing in place, contrast can help the fields and button stand out.

Quick check: On mobile, do labels, help text, and errors stay with the right field? Does the button still look like the final action? Test with larger text enabled, and don’t shrink text or squeeze gaps just to shorten the page.

4. Use Contrast to Make Fields and Buttons Clear

Use contrast to guide visitors from the headline to the button. Labels, input text, error messages, and button text should be easy to read, with at least 4.5:1 text contrast against their backgrounds. Give every field a clear boundary.

Keep your brand colors without sacrificing readability, and make the submit button the clearest visual action.

Add a clear focus ring to the active field or button. Then tab through the form to check that focus remains visible and follows the visual order, so visitors don’t lose their place.

Don’t rely on color alone to show state changes. Error color should be one cue, not the only cue. Mark disabled controls with the native disabled attribute, or use aria-disabled="true" for custom components.

Quick check: Test all four states before launch: default, focus, error, and disabled.

Next, size the form to fit the screen.

5. Size the Form for Desktop and Mobile

With the visual path in place, size the form to fit the screen and keep it easy to use.

On desktop, set a maximum width of about 600 CSS pixels. The form should feel like the next step, not a separate panel. Match field widths to the expected content: narrow for ZIP codes, full-width for street addresses, and more room for longer entries like email addresses. Keep those entries readable on smaller screens, too.

On screens below 768 CSS pixels, stack fields in a single column. Use fluid widths that fit the screen without horizontal scrolling, making the form easy to scan and complete on a phone.

Set input text to at least 16 CSS pixels for readability and to reduce automatic zoom in iOS Safari. Choose input types such as type="email" and type="tel" so phones display keyboards suited to each field.

Make fields and buttons at least 44 × 44 CSS pixels. Once sizing is set, label placement helps users complete each field.

Quick check: Fill out the form on a phone using realistic entries, including a long name and street address. Check that the layout stays readable, the keyboard matches each field, and the submit action stays visible.

6. Keep Labels Visible and Fields in a Logical Order

Once the form fits the screen, make each field easy to understand. Keep labels visible after people start typing. Placeholder-only text disappears, forcing people to remember what the field asks for. Link each label to its input with matching for and id attributes so screen readers can identify the field’s purpose.

Use plain language and a familiar question order. Ask only for information the offer needs, and mark any optional fields. Arrange questions to follow the visitor’s decision path toward submission. If the form gets long, split it up into multi-step forms rather than crowding one screen.

For forms with 7+ fields, use steps with 3–5 related questions each. Add a numbered progress indicator so people know where they are. Show conditional questions only when a previous answer calls for them.

Reform supports multi-step forms and conditional routing, but check label associations, contrast, and keyboard order before launch.

Quick check: Every field should have a label that stays visible, a clear purpose, and a place in the keyboard order that matches its position on screen.

7. Align the Submit Button With the Fields

Once the fields are clear and readable, make the button the form’s natural endpoint. Place the submit button directly below the last field, within the same form block. In a single-column, left-to-right layout, line up its left edge with the inputs. Don’t move it to a separate column or distant footer. This keeps the button in reading order and gives users a clear path from the last input to submission.

On mobile, use a full-width button to match the stacked fields.

Replace “Submit” with an action label that matches the offer, such as “Get the Guide” or “Request a Demo.”

The label should tell users what action they’re taking, keeping the path from the copy to submission clear.

Quick check: Can visitors easily find the button on desktop and mobile - and tell what happens next from its label alone?

Conclusion: Review the Path to Submission

Treat the page and form as one path. Context, hierarchy, spacing, contrast, size, labels, and button alignment all guide visitors toward submission.

Check each element on its own, then follow the experience from the headline through field entry to the submit button. Look for scroll jumps and broken alignment on desktop and actual phones and tablets. Test both portrait and landscape views.

Measure, fix, retest. Use form completion data to guide your next change. Compare desktop and mobile results, and check which fields cause errors or abandonment. Track scroll depth, CTA tap rate, and time to first field interaction to find where visitors get stuck. Fix issues supported by both data and observation first, then retest after each change to check that the path remains clear.

FAQs

Should my form placement change by traffic source?

Yes. Form placement should reflect visitors’ intent and how well they know your brand. High-intent visitors, such as people arriving through branded search or retargeting, often convert better when the form sits above the fold.

Cold traffic from social media or display ads may need more context before reaching a form below the fold.

If intent differs by channel, consider separate landing pages for each traffic source. Test form placement based on qualified leads, not just the number of submissions.

How can I match brand colors without losing contrast?

Keep a minimum contrast ratio of 4.5:1 between text and its background. For primary call-to-action buttons, use bold colors that fit your brand and high-contrast pairings that stand out against the background.

Test color combinations in different lighting conditions, including bright sunlight, to check readability. Save secondary or tertiary brand colors for less important elements so the path to submission remains the most visually prominent.

How do I balance fewer fields with lead quality?

Collect only the information that directly affects your sales process, such as company size, budget, or role.

Use multi-step forms to split complex requests into smaller steps. Add conditional logic so people see only the questions that apply to their earlier answers. Lead enrichment can gather extra context automatically, while real-time validation helps check that the information people enter is accurate.

Related Blog Posts

Use AI to summarize text or ask questions

Discover proven form optimizations that drive real results for B2B, Lead/Demand Generation, and SaaS companies.

Lead Conversion Playbook

Get new content delivered straight to your inbox

By clicking Sign Up you're confirming that you agree with our Terms and Conditions.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
The Playbook

Drive real results with form optimizations

Tested across hundreds of experiments, our strategies deliver a 215% lift in qualified leads for B2B and SaaS companies.