Launch mistakes
A contact form still posting to staging
A form's action attribute is the URL the browser sends the submission to. When a site moves from staging to production and that URL still points at a staging host or localhost, visitors fill in the live form but their enquiries go to an environment nobody watches, or fail outright. Check the action of every form on the live site and send one real test submission before handoff.
Last reviewed
The action attribute is the URL that processes the form submission, and a formaction attribute on the submit button can override it. (Source: MDN: The form element)
How it happens
Developers often hard-code an absolute endpoint while building: a staging API, a webhook on a preview deploy or a handler on their own machine. A search-and-replace of the domain during migration catches text in the database but can miss values in theme files, environment configuration or a page builder's form settings.
Forms that submit through JavaScript have the same problem, with the URL kept in a script instead of the markup.
How to spot it yourself
- On each live page with a form, right-click the form, choose Inspect and read the action attribute on the <form> element. Check any formaction on the submit button too.
- Search the page source for the staging hostname, “localhost” and “127.0.0.1”.
- Open the developer tools' Network tab, submit a test entry and see which host the request goes to.
- Confirm the test entry arrives where the client expects it: the inbox, the CRM or the form service.
How to fix it
- Point the action at the production handler, preferably as a relative path, so it follows the site to any domain.
- Keep endpoints in environment configuration rather than in templates, and check the production values before go-live.
- After the fix, submit a real test entry and confirm it arrives.
What Launch Ready checks
Each finding below shows the title, “Why it matters” and “How to fix” text the report uses. Severities are the defaults; a project rule override can change or silence a rule.
Rule form_action_localhost
What the scan looks at: Reads the action attribute of every <form> on the crawled pages, from the HTML and, where a page was rendered in a browser, from the rendered page. It reports an action that contains localhost, 127.0.0.1, 0.0.0.0 or ::1. It runs whatever the project's environment.
Default severity: Block Launch.
Form submits to localhost
Why it matters: The form action points at a local machine. Real visitors cannot submit it. This is a static markup check — Launch Ready did not send a test submission.
How to fix: Point the action at your production form handler or a live form service.
Rule form_action_staging
What the scan looks at: Runs only when the project is set to Production and the scanned address does not itself look like staging. It resolves the action to a full URL and reports it when the host looks like staging: a subdomain word such as staging, stg or uat; on the site's own domain also dev, develop, development, stage, preview, test, testing, qa or sandbox; the default preview domain of a hosting platform, such as a vercel.app or netlify.app address; or a private network address.
Default severity: Important.
Form submits to a staging URL
Why it matters: Submissions will go to a non-production endpoint. This is a static check; we did not submit the form.
How to fix: Update the form action to the live endpoint.
What Launch Ready does not check here
- Submitting the form. The check reads markup only; it does not send a test entry or confirm that a message arrives.
- A formaction attribute on the submit button. The check reads the action on the <form> element.
- Endpoints called from JavaScript instead of the action attribute, and embedded forms whose markup sits inside an iframe.
- Staging hosts with ordinary names, such as a client's old domain.
- Spam protection, validation messages and thank-you pages.
- Launch Ready does not guarantee a bug-free website.
- It does not make the launch decision. People make it, with the report in hand.
How we scan describes what the crawler fetches, renders and stores.
Related checklist items
- Form actions do not point to localhost or staging (Scan check)
- Critical journeys complete end-to-end in browser (Manual)
- Form submission delivery reaches intended inbox/CRM (Manual)
- Post-submit redirects and thank-you pages work (Manual)
From the free 72-item website launch checklist, with each item's coverage label: Scan check, Partly checked or Manual.
Related launch mistakes
- Staging and localhost links left in: Links, canonical tags or redirects still send visitors to staging, a preview build or a developer's machine.
- Analytics that never fired: The tracking tag is missing, waiting for consent that never comes, or installed twice.
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.