Form Redirect After Submit: 5 Simple Ways in WordPress

A form redirect after submit decides what visitors see in the moment after they send your form. It is a small setting with a big effect: a thoughtful next page can book a call, recommend a resource or simply reassure, while a dead-end “Thank you” wastes the moment when the visitor is most engaged.

This guide explains when a redirect beats an on-page message, five simple ways to set up a form redirect after submit in WordPress, how to build a thank-you page that works, and the tracking mistakes to avoid.

How a form redirect after submit works

Behind the scenes, the sequence is simple. The visitor presses Send. The form checks the answers, the server saves the entry and runs spam checks, and the notifications and auto-reply are queued. Only then does the form either show your message or move the browser to the page you chose. Because the redirect comes last, nothing the visitor typed depends on the next page loading. If they close the tab during the redirect, the entry is already safe in your inbox.

Message or redirect?

Both are valid. A short message is perfect for a simple contact form or a popup. A form redirect after submit is better when you have something useful to show next.

5 simple ways to redirect after submit in WordPress

1. Show a message instead

The simplest option is no redirect at all: the form is replaced by your thank-you message. In FillKite, choose Show a message under After someone submits in the form’s Settings tab. Messages can include merge tags such as the person’s name, so “Thanks, Sam, we will reply by email today” feels personal.

2. Redirect to a thank-you page

Choose Go to another page and pick a page on your site. After the form is sent and the entry is saved, the visitor lands there. This is the classic form redirect after submit, and it gives you a full page for next steps.

3. Redirect by answer

Different visitors often need different next steps. Press Add a confirmation by answer and set a rule, such as “Department is Sales → /sales-thanks/”. The first matching rule from the top wins; everyone else gets the default confirmation. You can mix messages and pages: sales enquiries go to a page with a booking link, support questions see a message pointing to the help centre.

4. Return after payment

On a paid form, the visitor goes to the payment provider’s checkout first, then comes back to your site. The thank-you page should confirm both the details and the payment. With FillKite Pro’s Payment field, visitors return after paying, and the notification is sent only once the payment succeeds. Our guide to the Stripe payment form covers the flow.

5. A developer filter for special cases

Sometimes a redirect depends on something the settings cannot express, such as a value from another system. FillKite has a fillkite_submission_redirect filter so developers can decide the destination in code. Most sites never need it, but it is there when a project does.

Why the moment after Send matters

Right after sending a form, a visitor is at their most engaged. They have just decided to contact you, typed their details and pressed the button. Their attention is fully on your business for a few seconds. A generic “Thank you” lets that attention drift away. A well-planned form redirect after submit, or a well-written message, uses it: to reassure, to set expectations, and to offer something that moves the relationship forward.

It is also the moment where doubt can creep in. Did it work? Will anyone read it? Should I also email them, or fill in a competitor’s form just in case? A clear confirmation answers all three before they are asked.

Form redirect after submit examples

Each form redirect after submit in the table leads to a page with one job. The visitor already did what you asked; the thank-you page makes the next step obvious and easy.

Example: by service

A web studio’s enquiry form asks “What do you need?”. With confirmations by answer, “New website” redirects to a page with portfolio highlights and a booking link, “Support” shows a message pointing to the help desk, and everything else gets the default thank-you page. One form, three well-matched next steps.

Build a thank-you page that works

Every form redirect after submit is only as good as the page it leads to. A useful thank-you page:

• confirms it worked: “Thanks, your request is in”;
• says what happens next and when: “We will send a quote by 3 pm today”;
• offers one clear next step: book a call, read a case study, download a guide;
• stays out of search results, since it only makes sense after a form. Set it to noindex.

Avoid clutter. One next step works better than five links, and the visitor has just done you a favour; do not ask for too much more.

What to put on a thank-you page

If you are not sure what to offer after a form redirect after submit, choose one of these, based on the form:

• A booking link for enquiries where a call is the natural next step.
• Two or three case studies close to what the visitor asked about, to build confidence while they wait.
• A short video introducing the person who will reply.
• Answers to the questions people ask next, such as how pricing works or how long projects take.
• A way to share, for event registrations and downloads, so visitors can tell a colleague.

Whichever you choose, pick one and make it the obvious action on the page. Several competing offers dilute the effect.

Why redirects stay on your own site

FillKite’s Go to another page setting sends visitors to a page on your own site. That also avoids a real risk: a form that can redirect anywhere can be abused to send people to a malicious site that looks like yours, a known security problem called an open redirect. Keeping every form redirect after submit on your own domain avoids it, and keeps visitors on your site at the moment they are most engaged. If you need to hand people to an outside tool, such as a booking calendar, embed it on your thank-you page or link to it from there.

In Elementor and other page builders

The redirect is a form setting, not a page setting, so it works wherever the form appears: the block editor, Elementor with the FillKite Form widget, or a shortcode in a template. Build your thank-you pages with your page builder like any other page, then pick them in the form’s settings. When the same form appears in several places, every copy uses the same form redirect after submit, which keeps behaviour consistent.

Save before any form redirect after submit

Whatever you choose, the entry must be saved before the visitor leaves. If a form redirects first and saves later, a slow connection or a closed tab can lose the lead. FillKite saves every entry before anything else happens, then shows the message or redirects. The visitor’s journey and your record are both safe.

Writing the message when you do not redirect

If you choose a message rather than a form redirect after submit, make those few lines count. A good confirmation message:

• uses the person’s name with a merge tag, such as {field:name};
• confirms what they asked for, in their words;
• says when and how you will reply;
• offers one link, if it helps, such as your pricing page.

Example: “Thanks, Sam. Your question about a new website is on its way. We will reply by email within two working hours. Meanwhile, here are three recent projects.” That is short enough for a popup and still feels personal.

Redirect and auto-reply together

A form redirect after submit and an auto-reply do different jobs, and they work well together. The thank-you page handles the moment: it confirms and suggests the next step while the visitor is still on your site. The auto-reply handles later: it lands in their inbox as proof the message arrived, with your reply time and contact details. Keep their promises the same, so the page and the email never disagree. Our auto reply email template examples show how.

Tracking without double counting

Many sites set up a form redirect after submit so that analytics can count thank-you page views as conversions. That works, but be careful when you also send a form event. Counting both means every lead is counted twice.

• Pick one method. A form event, such as GA4’s generate_lead, is more accurate because it only fires after a successful submission. See our guide to GA4 form submission tracking.
• If you use page views, make sure the thank-you page cannot be reached any other way, and exclude refreshes.
• With redirects, FillKite waits a moment for the GA4 event to be sent before moving to the next page, so the event is not lost.

On phones

A form redirect after submit on a phone should land on a page that loads quickly and puts the confirmation at the top, not below a large header image. Keep the next step visible without scrolling, and make its button easy to tap. Test the whole path on a real phone with mobile data, from the first field to the thank-you page.

Popups and redirects

When a form lives in a popup, a message usually works better than a redirect. The visitor stays on the page they were reading, sees the confirmation in the popup, and closes it. A form redirect after submit from a popup can feel like being pushed away. Use redirects from popups only when the next page is genuinely valuable, such as a download.

Test the full journey

Before you rely on a form redirect after submit, walk through it as a visitor. Fill in the form with each kind of answer that has its own confirmation, and check that each lands on the right page or message. Confirm the entry is in the inbox, the notification reached the right person and the auto-reply arrived. Finally, open the thank-you page directly in a private window: it should still make sense, but it should not be findable in search results.

Repeat the test whenever you rename or move a thank-you page. A redirect that points to a deleted page sends every new lead to a “not found” screen, which is the worst possible end to a form.

Measure what happens next

A thank-you page is a chance to measure the second step. Watch how many visitors click the next step you offer, such as booking a call or reading a case study. If few do, change the offer or make it more prominent. Over time, a good thank-you page turns a single enquiry into a deeper conversation. Our guide to form conversion rate explains the testing method.

Review your thank-you pages yearly

Thank-you pages behind a form redirect after submit are easy to forget, because only people who send forms see them. Once a year, open each one and check that promises, reply times, links and offers are still accurate. Remove anything out of date, and refresh case studies so they show your current work.

A form redirect after submit checklist

• Every entry is saved before the visitor moves on.
• Simple forms and popups show a message; richer journeys redirect.
• Thank-you pages confirm, explain the next step and offer one action.
• Thank-you pages are set to noindex.
• Different answers lead to matching pages where it helps.
• Only one tracking method counts each lead.
• The whole flow is tested on a phone.

Where a form redirect after submit goes wrong

Frequently asked questions

How do I redirect a WordPress form to a thank-you page?

In FillKite, open the form’s Settings tab, choose Go to another page under After someone submits, and pick the page. The entry is saved before the redirect.

Can I redirect to different pages based on answers?

Yes. Add a confirmation by answer with a rule, such as a department or service, and choose a page for it. The first matching rule wins.

Is a redirect better than a message?

Not always. Messages are faster and work well for simple forms and popups; redirects give room for next steps and suit quotes, bookings and downloads.

Can a form redirect after submit go to another website?

In FillKite, redirects go to pages on your own site, which protects visitors from open-redirect abuse. Link to outside tools from your thank-you page instead.

Does the redirect slow anything down?

Only by one page load. The entry is saved first, and if GA4 is on the page, FillKite gives the event a moment to send before moving on.

Should the thank-you page be in my sitemap?

No. Set it to noindex so people only reach it after sending the form.