A visitor fills out your contact form, clicks submit, and lands on a generic thank-you page that says nothing about your brand and gives them no next step. That's the default behavior for a lot of form backends, and it costs you a warm lead who just told you they're interested. SimpleForm is a hosted form backend for static websites that lets you set a custom Redirect URL for every form, so a successful submission sends the visitor exactly where you want: a real thank-you page, a pricing page, or back to the section of your site they came from.
This matters more than it looks. A form is often the only moment a static site talks back to a visitor, and where that moment ends up shapes whether the visitor trusts the submission went through at all.
What Happens to a Visitor After They Submit a Form?
By default, a standard POST submission to a SimpleForm endpoint shows a plain thank-you page and stops there. That's fine for a quick test, but on a live site it's a dead end: no confirmation of what happens next, no path back to your content, and no way to send a visitor toward a specific page after they've shown interest.
Leaving the redirect on default also makes it harder to measure success. Most analytics tools track a thank-you page view as the conversion event for a goal, and a generic shared thank-you page can't tell you which form on which page produced the lead. A dedicated confirmation URL per form fixes that immediately, since each form's traffic lands on a URL you control and can track on its own.
How Do You Set a Custom Redirect URL in SimpleForm?
Every form in SimpleForm has its own Redirect URL setting, changed from your dashboard without touching your site's code or redeploying anything.
- Log in to your dashboard with your account email.
- Open the form you want to configure from your forms list.
- Paste the full destination URL, including https://, into the Redirect URL field.
- Save the form settings.
- Submit a live test entry through the form itself to confirm the redirect fires.
Before a hosted form backend, most static sites solved this with a small server-side script or a serverless function whose only job was to catch the POST and issue a redirect header, one more piece of infrastructure to write, deploy, and keep working. Setting the field in your SimpleForm dashboard replaces that script entirely, and the setting lives with the form itself rather than in a codebase someone has to remember to update.
Can You Redirect Differently for an AJAX Submission?
No, an AJAX submission never triggers the Redirect URL at all. Adding an Accept: application/json header to the request tells SimpleForm to return a JSON response instead of a redirect, and your own JavaScript decides what the visitor sees next.
| Submission Method | What SimpleForm Does | What You Handle |
|---|---|---|
| Standard POST, no special headers | Redirects the browser to your Redirect URL, or the default thank-you page if it's blank | Nothing, SimpleForm issues the redirect |
| AJAX with Accept: application/json | Returns a JSON body with a success field, no navigation | Your JavaScript reads the response and updates the page |
This split matters if your form uses fetch() to submit without a page reload. The Redirect URL field is simply ignored in that case, and you'll need a few lines of JavaScript to show a confirmation message, swap the form for a success state, or navigate the visitor yourself once the response comes back with success set to true.
Mixing the two approaches on the same form is a common mistake: setting a Redirect URL and also submitting with fetch() does nothing, because the JSON header takes priority and the redirect is never issued. Pick one submission style per form and build the confirmation experience to match it.
Does SimpleForm Redirect on a Failed Submission Too?
No, only a successful submission redirects. SimpleForm returns a distinct HTTP status for every outcome, and the browser redirect is tied to exactly one of them.
| Status Code | What It Means |
|---|---|
| 200 | Submission accepted, or a honeypot field caught a bot and the request is silently marked OK |
| 302 | Redirects the browser to your configured Redirect URL |
| 400 | The form data was missing a required field or was otherwise invalid |
| 402 | Your plan's monthly submission limit was exceeded |
| 403 | The request came from a domain not on your allowed-domains list |
| 404 | The endpoint token doesn't exist or has been deactivated |
| 429 | The IP rate limit of 10 submissions per hour was exceeded |
This distinction matters when you're debugging why a visitor says the form "didn't work." A 400, 402, 403, or 404 means the submission never landed in your dashboard, and no redirect happens because there's nothing successful to redirect from. If you're relying on the Redirect URL page as your only signal that a submission worked, add a webhook so a failed attempt doesn't disappear silently, since a visitor who hits one of these codes usually just sees a blank error and gives up rather than reporting it.
What Happens If You Leave the Redirect URL Blank?
SimpleForm shows its own default thank-you page. It confirms the submission went through, but it carries none of your branding and gives the visitor nowhere else to go, which is why most production forms should point the field at a real page on their own site.
A blank Redirect URL is a reasonable choice while you're still testing a form, since it confirms the endpoint works without requiring a destination page to exist yet. Fill it in before the form goes live in front of real visitors, and confirm it by submitting a genuine test entry rather than trusting the dashboard preview alone.
If a single dashboard field feels like too small a thing to build a workflow around, that's a fair reaction, and the point isn't the field itself, it's the plumbing you don't have to build to use it. Every plan, including Free, includes redirects, honeypot spam protection, and IP-based rate limiting of 10 submissions per IP per endpoint per hour, all without running a server. The Free plan covers 100 submissions per month across 3 forms with no credit card required, which is enough to test this end to end on a real project before deciding whether to pay for anything.
Create a free SimpleForm account, set your form's Redirect URL to a real thank-you page, and submit a test entry. The whole setup takes about five minutes and you'll see the redirect fire on your own site immediately. Start free and connect your first form.
Frequently asked questions
No. SimpleForm handles the redirect for you. Set a destination URL in the Redirect URL field on your form's dashboard settings, and every standard POST submission that succeeds sends the visitor there automatically, with no server, no JavaScript, and no extra HTML required beyond the form itself.
SimpleForm shows a default thank-you page instead. This is fine for testing or a low-traffic form, but it carries no branding and gives the visitor no path back to your site, so most production forms should point the Redirect URL field at a real page before launch.
No, and this is by design. Adding an Accept: application/json header to the request tells SimpleForm to return a JSON body instead of issuing a redirect, so your own JavaScript reads the response and decides what to show the visitor next, typically a success message on the same page.
Retention depends on your plan. The Free plan keeps submissions for 7 days, and paid plans extend that window up to 365 days. You can also delete individual submissions from your dashboard at any time, independent of the plan's retention period.
Yes. The Redirect URL field is set per form, not per account, so a contact form and a newsletter signup on the same site can each send visitors to a different confirmation page after they submit.