How to Add a Contact Form to Your Website (and Where the Messages Go)

What a good contact form needs (and what to leave out)

The best contact forms are short. Every extra field is another reason for someone to give up, so ask for the minimum you need to reply. For most businesses that is a name, an email, and a message. If the type of enquiry genuinely matters (a shoot date, a service, a preferred time), add one field for it, no more.

The goal is to start a conversation, not to collect a full brief. You can ask for the details once they have replied.

• Name, email, and a message field cover most businesses
• Add at most one context field (service, date, budget) only if you truly need it
• Label the button for what it does ("Send message," not "Submit")
• Show a confirmation after sending so people know it worked
• Put your email address in plain text nearby, some people prefer to email directly

Where do contact form submissions actually go?

This is the part that trips people up. A contact form is just a set of fields, on its own it does nothing. Something behind it has to catch each submission and deliver it to you. A form with nowhere to send to (a plain HTML form with no backend, for example) will look perfectly fine and silently go nowhere, which is why so many "broken" contact forms are really just unwired ones.

There are three common ways a submission reaches you:

Where to put your contact form

Do not bury your form on a single contact page and hope people find it. Make getting in touch easy from anywhere. A dedicated contact page is the anchor, but a short form or a clear "Contact" link should also live in your footer and at the end of your homepage.

Match the placement to intent. A service business might put a "Book" or "Enquire" button in the top navigation, while a portfolio might end each project with a quiet "Work with me" link.

• A dedicated contact page as the main destination
• A "Contact" link in both the top navigation and the footer
• A form or call-to-action at the bottom of your homepage
• Your email address in plain text as a fallback

Keep the spam out

Publish a contact form and you will eventually get spam. It is normal and manageable. The lightest-touch protection is a honeypot, an invisible field that bots fill in and humans never see, so their submissions get quietly rejected. Most good builders include this automatically.

Avoid clunky puzzle CAPTCHAs if you can, they cost you real enquiries by adding friction. A honeypot plus a bit of filtering catches the vast majority of junk without annoying your actual visitors.

• Use a honeypot field (invisible to people, tempting to bots)
• Avoid heavy CAPTCHA puzzles that frustrate real visitors
• Route submissions to a dedicated inbox or folder so spam does not bury real enquiries
• If spam spikes, add filtering rather than more friction

How to add a contact form without code

You should not have to wire up form handling, email delivery, and spam protection by hand. The old way meant a form plugin, a third-party form service, or writing backend code to catch submissions. The faster way is to describe what you want, "add a contact form with name, email, and message, and email me when someone submits," and have it built and connected in one step.

The key thing either way: after you add a form, send yourself a test submission. If it lands in your inbox, it is wired correctly. If nothing arrives, the form is not connected yet.

How Looops handles contact forms for you

Looops is an AI website builder you chat with. Ask it for a contact form and it adds one that actually works, the fields you want, connected so every submission is emailed straight to you, with spam protection built in. No third-party form service, no backend to set up.

You change it by talking: "add a phone number field," "send enquiries to a second email too," "make the button say Send enquiry." Submissions arrive in your inbox from the moment you publish.

• Contact forms that email you automatically, no wiring required
• Spam protection included, no CAPTCHA friction
• Add or change fields by describing them in plain English
• Optionally keep a record of submissions, not just email
• Works the moment you publish, test it and it lands in your inbox