'Confirm Form Resubmission' and duplicate enquiries: the fix
Short answer: The "Confirm Form Resubmission" warning, and the duplicate enquiries or orders that follow when customers click through it, happen because your form page answers a POST request by showing the result page directly. When the customer refreshes or presses Back, the browser offers to send the POST again. The standard fix is called Post/Redirect/Get: process the form, then respond with a 303 redirect to a normal "thank you" or confirmation URL, so a refresh only reloads that page. Add a server-side duplicate check as a safety net.
What's going on
Forms that change something, like sending an enquiry, placing an order or booking a slot, normally submit with the HTTP POST method. The HTTP specification, RFC 9110, defines GET, HEAD, OPTIONS and TRACE as "safe" methods; POST isn't, because it's expected to have side effects.
If your server handles the POST and then returns the confirmation page as the response to that same request, the browser's current page is the result of a POST. When the customer:
- refreshes the page,
- presses Back and then Forward,
- or reopens the tab later,
the browser has to repeat the POST to redisplay it. Because that could create a second order or enquiry, browsers show a warning such as "Confirm Form Resubmission" or "Resend data?". Many customers click "Continue" without reading it, and you get duplicates.
The fix: Post/Redirect/Get
The pattern has three steps:
- POST. The browser submits the form.
- Redirect. The server processes it, saves the result, and responds with a redirect to a separate URL, such as
/enquiry/thanksor/orders/1234/confirmation. - GET. The browser follows the redirect with a normal GET request and shows that page.
Now the browser's current page is the result of a GET. Refreshing just reloads the confirmation page; nothing is resubmitted.
Which redirect code? MDN's documentation on 303 See Other explains that it's typically sent after PUT or POST so the client can retrieve a confirmation, and that the redirected resource is always fetched with GET. MDN's 302 page notes that browsers do change POST to GET after a 302, as the specification permits, but recommends 303 when you want the method changed to GET, and 307 when you want it preserved. For form submissions, 303 states your intention exactly.
What the confirmation page should show
Because the confirmation page is now a separate URL, it needs to know what to display:
- For orders and bookings: include an ID in the URL, such as
/orders/8F3K2/confirmation, and check that the visitor is allowed to see it (signed in as that customer, or holding an unguessable token). - For enquiries: a generic thank-you page is often enough, perhaps with a one-time message stored in the session ("We've received your message about kitchen fitting").
- Never put personal details in the URL query string, where they end up in logs and analytics.
Validation errors are different
If the form has errors, such as a missing phone number, it's common to re-render the form directly from the POST with error messages and the customer's entries kept. That's fine, because nothing was saved. Refreshing that page re-submits invalid data that will fail again. Only successful submissions need the redirect.
Add a safety net for double-clicks
Post/Redirect/Get stops refresh duplicates. It doesn't stop a customer double-clicking the submit button or a slow connection sending the form twice. Add:
- Disable the button after the first click and show "Sending…".
- A one-time form token: include a unique hidden value when the form is shown, and on the server reject a second submission with the same value.
- Natural duplicate checks where they make sense, such as the same email, same message and same minute.
JavaScript-submitted forms
If your form submits with JavaScript (fetch or XHR) and updates the page without navigating, the browser history doesn't contain a POST, so refresh warnings don't appear. You still need the double-click protection, and you should update the URL or show a clear confirmation so a refresh doesn't make the customer think it failed and submit again.
How to check your forms
- Submit a test enquiry or order.
- Press refresh on the confirmation page. If you see a resubmission warning, the form isn't using a redirect.
- Look at the network panel in your browser's developer tools: after the POST, you want a 303 (or 302) and then a GET.
- Double-click the submit button quickly and check that only one record is created.
Emails and notifications
Duplicate submissions usually cause duplicate notifications too: two emails to your sales inbox, two confirmations to the customer, two entries pushed into your CRM. After fixing the form, check each automation it triggers. If an integration receives the submission through a webhook, make it ignore an entry it has already processed, using the submission's ID, so a retry or a resend from the form tool doesn't create a second lead or a second order in another system.
Keep the confirmation page useful
A redirect gives you a page you control, so use it: confirm what was received, say what happens next and when, and offer one useful next step, such as a link to opening hours or a guide.
An illustrative example
A hypothetical Leeds driving school received the same lesson enquiry two or three times a day. Its form plugin displayed "Thanks, we'll call you" as the direct response to the POST, and students refreshed the page to check it had worked. The developer changed the handler to redirect with a 303 to a thank-you page, disabled the button after the first click and added a hidden one-time token. Duplicate enquiries stopped.
FAQ
Is this an SEO issue?
Not directly. Confirmation pages are usually excluded from indexing anyway. It's about data quality and customer experience.
Do form plugins handle this?
Many do, often via a "redirect to a thank-you page" setting. Check yours.
Can I just hide the warning?
No. The warning is the browser protecting customers. Fix the flow instead.
Will a thank-you page help analytics too?
Yes. A dedicated confirmation URL makes it easy to count successful submissions.
If your forms create duplicate enquiries or orders and you'd like them fixed, tell us which form tool or platform you use.