# Which fields belong in your landing-page form?

> Choose form fields by the next business action. Compare signup, consultation, and quote requests, review a worked example, and verify field delivery.

- Canonical: https://pageree.com/guides/landing-page-form-fields/
- Published: 2026-09-15. Updated: 2026-09-15.
- Collection: Guides (https://pageree.com/guides.md)
- Site index for agents: https://pageree.com/llms.txt

**The short answer.** Every form field should support a decision or the promised next step. Keep a reliable contact route, distinguish required from optional information, and verify that changes to field names reach the configured delivery destination correctly.

## Give every field a job

A useful landing-page form collects what is needed for the promised next step. Removing every question can create enquiries that are impossible to assess. Asking for a full discovery brief can make an initial conversation unnecessarily difficult. Choose fields from the business process rather than from a universal rule about form length.

Start with two questions: what did the visitor agree to request, and what information does the person receiving it need to act? A newsletter, a consultation, and a quote request should not share an identical form just because an assistant generated one convenient component.

For each field, name the decision it supports. If nobody uses the answer, remove it or defer it to follow-up.

## Compare three common goals

| Goal | Sensible starting fields | Details to add only when needed |
| --- | --- | --- |
| Newsletter signup | Email and the actual subscription choice | Name or topic preference if used |
| Consultation request | Name, email, and the question to discuss | Time zone or format for practical fit |
| Project quote | Name, reply contact, scope, and relevant location | Timing, budget range, or property type |

These are starting designs, not measured optimal field counts. A local cleaning business may need property size and service area to prepare a meaningful estimate. A software demo may need team size or a workflow description. The field earns its place when it changes the next response.

For examples of those different conversations, compare the [SaaS demo template](https://pageree.com/templates/saas-demo-landing-page/) and the [quote-request template](https://pageree.com/templates/request-a-quote-landing-page/).

## Distinguish required from useful

Mark a field required only when the requested action cannot proceed without it. A contact route is necessary for a reply. A preferred appointment time may be optional if the owner will discuss scheduling anyway. Include an “I don't know yet” option when uncertainty is a valid answer.

Use labels that remain visible as the visitor types. W3C's [form-labelling tutorial](https://www.w3.org/WAI/tutorials/forms/labels/) explains the relationship between a control and its label. Placeholder text can show an example, but it should not be the only explanation of what belongs in the field.

Give format instructions where they help. “Town or postcode” is clearer than “Location” if the business does not need a street address. “Approximate total event budget” is clearer than “Budget” when it might otherwise be confused with your fee.

## Work through a cleaning enquiry

Consider a **fictional design example**. A cleaning business initially asks for name, email, phone, full address, company name, budget, and a long message. The owner actually needs to know whether the property is in the service area, its approximate size, and whether the visitor wants a one-off or recurring clean.

A more relevant first form could ask for name, email, town/postcode, property-size range, and cleaning frequency. Phone can remain optional if email follow-up works. The exact address can be requested when a visit is being arranged.

This redesign improves the relationship between questions and decisions. It is not evidence that fewer fields caused a higher conversion rate. The owner should still test whether the answers are sufficient to respond and whether any missing detail creates repeated follow-up.

## Build the field and delivery contract together

In Pageree, the generated page must follow the form contract described in the [connection documentation](https://pageree.com/docs/). Each submitted input needs a name, and the form needs the configured endpoint, validation, honeypot, and consent behavior required by that workflow. Visual fields alone do not prove that the server will accept or deliver them.

When a field changes, inspect both the published form and the delivery destination. A spreadsheet or CRM mapping may still expect the old field name. Do not silently rename `project_type` in the page and assume every downstream automation will infer the change.

## Use this review prompt

```text
Review the fields on this landing-page form.
Visitor action: [what they are requesting].
Owner's next step: [actual follow-up]. Current fields: [list].
For each field, state its decision purpose, whether it must be required,
and whether it can move to later follow-up. Keep a reliable reply route.
Suggest precise labels, examples, and valid unknown/other choices.
Do not collect sensitive detail that the first enquiry does not need.

Then inspect the Pageree form contract and configured delivery mapping.
Show the proposed field names and any destination changes required.
Save a private draft for review. After approved publication, provide
test cases for normal, incomplete, long, and repeated submissions.
```

## Verify the owner receives usable answers

Submit a realistic enquiry and inspect the destination. Test an optional blank, a long description, and an “other” choice. Confirm required-field errors are understandable and that a failed request does not show a success message.

Use the [email delivery guide](https://pageree.com/guides/landing-page-form-to-email/) for receipt checks. If the page attracts too many irrelevant enquiries, inspect the offer and traffic as well as the form; another mandatory field cannot fix every targeting problem.

## Related
- [Landing-page CTA examples for enquiries and signups](https://pageree.com/guides/landing-page-cta-examples.md): Choose honest CTA labels for quotes, consultations, demos, and resources. See annotated examples, useful nearby copy, and a complete action-review prompt.
- [Reduce spam in your landing-page contact form](https://pageree.com/guides/landing-page-form-spam.md): Inspect honeypots, field validation, rate limits, and delivery behavior in a Pageree form. Reduce unwanted submissions without promising zero spam.
- [Request-a-quote landing page template](https://pageree.com/templates/request-a-quote-landing-page.md): Ask the right questions for a useful estimate. Explore an original quote page, field checklist, confirmation copy, and AI prompt for your service business.

## Build it with your agent

Pageree is an MCP server. Add https://mcp.pageree.com/ to an MCP client that supports Streamable HTTP and OAuth, sign in, and the agent can build, publish and measure the page. Setup for every supported client: https://pageree.com/docs.md. Sign up: https://console.pageree.com/signup.