Three ways to add a form without code
| Option | How it works | Watch out for |
|---|---|---|
| Built-in form in your page builder | You add a form block; submissions are stored by the builder. | Where submissions go and who on your team can see them. |
| Embedded form from a form tool | You build the form in a separate tool and paste its embed code or link into the page. | The form may not match your page’s fonts and colours, and can load slowly. |
| Link to a hosted form | A button on the page opens a form on another site. | Visitors leave your page, and some will not come back. |
A built-in form is usually the simplest: one tool, one place to look for submissions, and a form that looks like the rest of the page.
Which fields to ask for
Every extra field asks the visitor for more effort and more trust. Start from what you will do next with a lead, and ask only for what that step needs.
- Sending a guide or a discount code: an email address is enough.
- Booking a call or a demo: name, email and perhaps a preferred time.
- Qualifying a sales lead: add one or two questions you will genuinely use to route or prioritise it, such as company size or what they need.
Mark which fields are optional, and use clear labels above the fields rather than placeholder text that disappears when the visitor starts typing.
Where to put the form on the page
Put the form where a visitor has enough reason to fill it in. On a short page with a simple offer, that can be the first screen. On a longer page that has to explain something first, put it after the explanation, and add a button near the top that scrolls down to it.
On mobile, keep the form short enough to see the submit button without scrolling past the keyboard, and make sure each field opens the right keyboard (email, number, phone).
Telling visitors what happens to their details
A form collects personal information, so treat it with care. The rules depend on where you and your visitors are; the principles below apply almost everywhere:
- Say next to the form what you will use the details for, in one plain sentence.
- Link to your privacy policy.
- Collect only the fields you need for that purpose.
- Ask separately before adding someone to a marketing list, if that is not the reason they are filling in the form.
- Limit who on your team can read the submissions.
How to test the form before you publish
- Fill in the form yourself with test details and submit it.
- Check that the submission arrived where you expect it, with every field filled in correctly.
- Submit it again with a required field left empty and check the error message makes sense.
- Check what the visitor sees after submitting: a confirmation message, or a thank-you page that says what happens next.
- Repeat the test on a phone.
- After publishing, send one more test from the live page, then mark or delete the test entries.