Redirects
Send visitors to an approved thank-you page after native form submission.
Configure an exact destination
Use an HTTPS URL you control and keep it within the form's approved redirect policy. Do not accept an arbitrary visitor-provided URL.
Native HTML and JavaScript behave differently
A native accepted submission may return a 303 redirect. Fetch does not automatically navigate the page, so client code should validate the returned redirect before using it.
| Mode | Behavior |
|---|---|
| HTML POST with Accept: text/html | HTTP 303 redirect to the approved destination or service receipt |
| POST JSON | 202 response; data.redirect indicates any destination |
| Custom interface | Redirect only after an accepted response; keep errors in place |
Test the deployed destination
Verify the full path, query handling, mobile layout, analytics consent, and back-button behavior on the production domain.
Documentation reviewed on October 20, 2026Suggest an improvement →