One-question choice pages
Best for radio-button or dropdown questions where the next page should load as soon as a visitor chooses an answer.
Documentation
Multi Page Auto Advance docs
Setup guidance, recommended Gravity Forms patterns, plan differences, and troubleshooting for building faster multi-page forms.
01
Quick start
Use this path when you are setting up the plugin for the first time or rebuilding an existing long form.
- Install and activate Gravity Forms.
- Install Multi Page Auto Advance from WordPress.org or upload the paid version from your account.
- Create a Gravity Forms multi-page form and add page breaks between each step.
- Use one primary question on pages where you want the form to move immediately after an answer.
- Enable auto-advance behavior for the field types supported by your plan.
- For typed fields or checkboxes in Plus, set the number of characters or selections required before auto-advance.
- Test the full flow on desktop and mobile before sending traffic to the form.
Best first test:
Create a short three-page form with one radio-button question per page. Confirm each answer advances to the next page before applying the same pattern to a production form.
02
Field and plan guidance
Start with the narrowest plan that fits your form. Upgrade to Pro for one business site, or Plus when the plugin belongs in your agency stack across client sites.
Plan
Use it for
Best fit
Free
Radio buttons and dropdown/select fields on simple multi-page forms.
Testing the core auto-advance behavior.
Pro
Product, poll, quiz, and survey workflows, hidden navigation buttons, conditional logic handling, transition animations, and step colors.
One serious business site with lead forms, quote requests, quizzes, polls, and higher-value multi-step forms.
Plus
Unlimited client-site licensing, checkbox/text/number triggers, upgraded conversational form functionality, and the full paid workflow for multi-site Gravity Forms operators.
Client sites, intake systems, conversational funnels, and advanced form workflows.
03
Recommended form patterns
Auto-advance works best when the page has one obvious answer and the next step is not surprising.
Lead qualification
Use auto-advance on budget, timeline, service, location, or fit questions so prospects move through the form quickly.
Quizzes and assessments
Keep each question focused, use progress indicators, and reserve manual navigation for review or open-ended responses.
Client intake
Split long intake forms into short steps, auto-advance simple choices, and keep complex detail pages manual.
Quote requests
Pair conditional logic with auto-advance so visitors skip irrelevant pages and reach the right quote path faster.
Conversational forms
Use the Plus workflow when the form is designed to feel like a guided conversation rather than a traditional form.
04
Configuration checklist
Use these checks before pushing a form live, especially when paid traffic or high-value leads depend on it.
Page design
Use page breaks, keep auto-advance pages short, and place explanation text before the field so the selection can immediately move the visitor forward.
Field selection
Use auto-advance on supported fields where one answer is enough. Keep manual navigation on pages with uploads, signatures, or review steps.
Navigation buttons
Hide buttons when a page is intentionally one-answer-at-a-time. Leave Back available when visitors may need to correct a previous choice.
Progress bar
Turn on a Gravity Forms progress indicator for longer flows so visitors understand how much work remains.
Conditional logic
Build and test the Gravity Forms logic first. Auto-advance should wait when the answer reveals another required field on the same page, then continue when the path is clear.
Mobile testing
Run the full form on a phone, check scroll position after each advance, and confirm the next question is visible without confusion.
05
Troubleshooting
Use the symptom first, then work backward through plan fit, field setup, conditional logic, and scripts. Most issues become obvious once the failing step is isolated.
Fast isolation test
Duplicate the form, remove custom styling and conditional logic, then test one radio-button field per page. Add features back one at a time until the behavior breaks.
Auto-advance does not fire
Symptom: A visitor chooses an answer, but the form stays on the same page.
Check
- Confirm the form is a Gravity Forms multi-page form with Page fields between steps.
- Confirm the trigger field type is included in the plan active on the site.
- Test with a radio button or dropdown first, because those are the simplest supported triggers.
- Disable cache/script optimization on the form page while testing.
Fix: Rebuild the first failing step as a one-question page, save the form, clear cache, and test the path in a private browser window.
Checkboxes advance too early or not at all
Symptom: The form moves before the visitor is done selecting options, or it never moves after checkbox selections.
Check
- Checkbox auto-advance is a Plus workflow.
- Set the required selection count so the plugin knows when the visitor is finished.
- Avoid mixing required and optional checkbox groups on the same auto-advance page.
Fix: Use one checkbox field per auto-advance page and configure the minimum selections required before the page can move.
Text or number fields do not advance
Symptom: Typed fields keep waiting even after a visitor enters a value.
Check
- Text and number triggers are Plus features.
- Set the character count or numeric condition expected before advancing.
- Avoid using typed auto-advance on pages where the visitor may need to review formatting, calculations, or long answers.
Fix: Use typed auto-advance for short, predictable answers only. Keep manual Next buttons for long comments, addresses, uploads, and review pages.
Conditional logic behaves unexpectedly
Symptom: The form advances, but the wrong next page appears or a required field is skipped.
Check
- Turn auto-advance off temporarily and test the Gravity Forms conditional path by itself.
- Make sure the answer does not reveal another required field on the same page.
- Check whether the conditional rule belongs on the field, page, section, or confirmation.
Fix: Fix the Gravity Forms logic first, then re-enable auto-advance after every branch reaches the right next page manually.
Image choice or styled choice fields fail
Symptom: A visually styled choice appears selected, but the page does not move.
Check
- Confirm the styled field still stores a standard Gravity Forms radio/select value.
- Test the same question with the default Gravity Forms field markup.
- Check for theme or add-on JavaScript that intercepts clicks before Gravity Forms receives the selection.
Fix: If the default field advances but the styled version does not, keep the default markup or exclude the styling script on that form page.
The page jumps or feels rough on mobile
Symptom: Auto-advance works, but the visitor lands in an awkward scroll position or the transition feels too fast.
Check
- Use one primary field per mobile auto-advance page.
- Keep help text above the field short so the next question is visible after advancing.
- Test with animations disabled before tuning transition effects.
Fix: Shorten the page, keep the next question high on the screen, and use simpler transitions on traffic-heavy mobile forms.
Common questions
Should every page auto-advance?
No. Auto-advance is strongest when a page has one primary answer and the next step is obvious. Keep manual buttons on review pages, upload pages, signature pages, long text answers, and pages with several fields.
Do I still need a Next button?
Sometimes. If the page contains multiple checkboxes, open-ended text, or several fields, visitors need a deliberate way to confirm they are done. Hide the Next button only when the page is intentionally one-answer-at-a-time.
What should I test first when debugging?
Start with a three-page test form using one radio-button question per page. If that works, add your real field type, then conditional logic, then styling, then cache/script optimization.
Why does the free version work in one form but not another?
The free version is intentionally limited to simple radio and dropdown/select auto-advance. Forms that rely on checkboxes, typed fields, hidden navigation, product fields, quizzes, polls, or conditional logic usually need a paid plan.
Can cache plugins break auto-advance?
They can. If JavaScript is delayed, combined, or moved, the trigger script may run at the wrong time. Exclude the form page or Gravity Forms scripts from optimization, clear cache, and retest.
Does auto-advance change entries, notifications, or integrations?
No. Auto-advance changes movement between pages. Gravity Forms still handles entries, notifications, confirmations, feeds, and integrations.
What details should I send support?
Send the form URL, Gravity Forms version, Multi Page Auto Advance version, license plan, field type, expected behavior, actual behavior, and the exact answer path that fails.
06
Support prep
When you need help, send enough context to make the issue reproducible.
- Gravity Forms version and Multi Page Auto Advance version.
- Your license plan: Free, Pro, or Plus.
- The field type that should trigger auto-advance.
- Whether the form uses conditional logic, hidden buttons, animations, cache, or script optimization.
- A link to the form page, plus the exact answer path that fails.
Next step
Compare features, confirm the plan fit, or send the support details when a live form is behaving unexpectedly.
Get support