HubSpot test form before you publish it

When you test your own form you fill every field, so you never see what a blank required field does. A visitor may leave the phone number empty or type a symbol in a name, and the error appears where they did not expect it. The thank-you message is also easy to skip, because you read it once and know what it says. A stranger reads it as the only sign the form worked. If it is a bare line of text under the button, they may submit again. A test that fills the form once shows none of this.

• Submit with every required field empty and read the message beside each one.
• Enter an email without the at sign and confirm the error names the email field.
• Complete the form once and read the thank-you text, then check whether a redirect address appears.
• Load the form at phone width and check the Submit button is reachable without zooming.
• Compare each field label with the word a stranger would use for the same thing.

A stranger may arrive on a phone, skim the title, and start typing without reading the labels. They fill the name, then the school or company, then reach the phone number, which some people type with spaces or a country code. They may leave an optional field empty and then find a required one they missed. Each of these is ordinary behavior, and none of it shows up when the owner fills the form in a steady order on a laptop.

An error message helps only if it sits beside the field it names. A message at the top of the form, far from a phone number, leaves the visitor guessing which box is wrong. Check that each message names the field and the rule in plain words, such as an email with an at sign, rather than a code. Then check the labels. A label such as Contact preference may mean nothing to a visitor who is not sure what they are being asked for.

The thank-you step is the last thing a stranger reads. A short line of text under the button can look as if the form did nothing, so the visitor may press again and send a duplicate. A thank-you page that sends them to a login or a generic home page leaves them unsure whether the request arrived. Read the words, then follow any redirect to see where the visitor lands.

The simulated run fills the form with bad data and with ordinary data, submits each time, and records the step where it stopped. The report gives that step, a screenshot of any error, and the thank-you screen it reached. It does not read your HubSpot account, so it cannot show whether the contact was created or landed on the right list. Check that yourself, under the name you typed, after one complete submit.

Forms grow after launch. A new required question, a changed field label or a new thank-you redirect can each stop the submit a stranger needs. Run the same bad and complete submits after each edit, at phone width, and compare the step where each run stopped with the run before. The run does not replace a check of the contact in your account.