Multi-page forms help users complete longer workflows without feeling overwhelmed. Use pages when you have:
- 10+ questions
- Multiple “sections” (Contact → Details → Review)
- Optional branches (e.g., business vs personal)
When to use multi-page
Add and reorder pages
- Add a new Page from the page controls.
- Give the page a short title (users will see it in navigation/progress UI).
- Reorder pages to keep the flow logical.
Add page / reorder pages (16:9) placeholder
Page titles and progress
Good page titles are:
- Short (1–3 words)
- Specific (what the user is doing)
- Consistent (same style across the form)
Examples
- Contact, Company, Details, Review
- Avoid: “Page 1”, “Next step”, “More info”
Block editor preview vs frontend
When you embed a multi-page form in the block editor, the preview shows a simplified flow:
- Only lightweight navigation is available in the editor preview.
- Validation, conditional logic, and payment review steps run only on the frontend.
- Always preview the page to test the real multi-page experience.
Best practices
Best practices that reduce drop-off:
- Ask easy questions first.
- Group “work” questions into one page (Company, Budget, Timeline).
- Save the longest textareas for later pages.
- Consider a final page for confirmation or review (especially for payments).
If you use the Payment Field, keep the payment review/pay step at the end so totals and gateway selection are clear.
Troubleshooting
- Users can’t proceed: check required fields and validation rules on the current page.
- Too many steps: combine small pages; aim for 2–5 pages for most workflows.
- Page feels “empty”: avoid pages with only one short field—merge it into a neighboring page.
Common searches
Common searches
- How do I build multi-step forms in WordPress?
- Can GriffinForms split questions into pages?
- What is the best way to organize long registration forms?