SITEWRENCH

How to Add a Form to a GoDaddy Website (Contact & Custom Fields)

Issued Jul 17, 2026Re-checked Aug 21, 2026

A website that can't take a message is just a brochure. The good news: to add a form to a GoDaddy website you don't need code or a plugin — the builder ships a Contact Form as part of its Contact Us section, and it handles the classic jobs: general enquiries, quote requests, simple sign-ups. This procedure sets one up, wires the notifications to the right inbox, and walks through the limits you should know before you depend on it.

Why a form instead of a published email address? Three reasons a technician will give you: a form keeps your address off the page where harvesters scrape it, it forces senders to include the details you actually need instead of a one-line mystery, and it feeds GoDaddy's Conversations inbox so there's a record that doesn't live in one person's mailbox.

One scope note before the steps: this page covers the native form inside the Websites + Marketing editor. If you already know you need file uploads, payments, or branching logic, skip ahead to the third-party section near the end — no sense wiring up a form you'll replace in a month.

Prerequisites

  • A Websites + Marketing site and access to its editor.
  • The email address that should receive submissions — one somebody actually checks. Notifications going to a dead inbox is the most common form failure there is.
  • A field list decided in advance. Write down the questions you genuinely need answered; every extra field costs you completed submissions.
  • Ten minutes after publishing to run a proper end-to-end test — the procedure for that is further down this page.

Procedure: add the contact form

The flow below is GoDaddy's documented route into the form settings.

  1. Sign in to your GoDaddy account and open My Products.
  2. Expand Websites + Marketing and select Manage next to your site.
  3. Select Edit Website.
  4. Open the page where the form belongs — for most sites, the Contact page.
  5. Add a Contact Us section there, or select the existing one if the page already has it.
  6. Inside the section, choose the Contact Form option.
  7. Set Send Message To to the email address that should be notified of submissions.
  8. Adjust the fields — the next section covers exactly what can change.
  9. Publish. The form doesn't exist for visitors until the site is republished.

Field options: what bends and what doesn't

  • Reorder by dragging fields into the sequence you want visitors to fill them.
  • Add a field with Add, then give it a Field Name and an Input Type.
  • Per field, you can toggle required on or off, rename, or remove entirely.

Two things are welded in place: the Email field and the Send button can't be deleted. That's the builder's floor — every form collects a reply address and has a submit control, whether you want them or not. Plan your field list around those two fixtures rather than fighting them.

CAUTION: removing a field is immediate, and its label and settings go with it. Deleting the whole Contact Us section removes the form outright. Messages you've already received stay in your notification inbox and in Conversations, but the form's configuration has no undo beyond the editor's Undo button and Site History.

Where submissions actually land

Every submission goes to two places. The first is the notification email you set in Send Message To — and this is per form, so a site with several forms can route each to a different address: quotes to sales, support requests to the helpdesk, press enquiries to the owner. The second is the GoDaddy Conversations web inbox, which collects submissions regardless of what the notification address is.

Treat them accordingly: the email is your alert, Conversations is your record. When someone claims they wrote weeks ago and got silence, Conversations is where you settle it.

Spam: set your expectations

Be realistic here. At the time of checking, the built-in form exposed no granular anti-spam controls — no visible CAPTCHA toggle, no keyword filters. What you get is the structural benefit: your address isn't printed on the page for bots to scrape, which alone cuts most of the junk a raw mailto link attracts.

If spam volume climbs anyway, marking more fields required raises the effort bar slightly. Past that, the honest fix is a third-party form with real CAPTCHA support, embedded via custom code — more on that below. And whatever you do, don't reply to obvious junk; a reply confirms the address is live.

Test the form before you trust it

  1. Publish the site so the live form matches what's in the editor.
  2. Open the page in a private browser window and submit a test message with a real reply address you control.
  3. Check the notification inbox — and its spam folder, which is where first-time form mail often lands.
  4. Open the Conversations inbox and confirm the same test arrived there.
  5. Reply to the test from your notification inbox to confirm the return path works too.

Variations worth knowing

  • Multiple forms: each form carries its own Send Message To, so different pages can notify different people without any forwarding rules.
  • Quote and intake forms: the Add field flow with input types is how you turn the generic contact form into a structured request form — budget, deadline, service needed, preferred date.
  • Changing the notification address later: edit the section, update Send Message To, republish. It takes a minute and gets forgotten constantly when staff change.

The built-in form vs a third-party embed

Know where the stock form stops. At the time of checking there was no documented support for conditional logic, multi-step flows, file uploads, or payment collection — it takes messages, and that's the job. For an application form, an order form, or anything with branching, embed a dedicated form tool instead using an HTML section; the full procedure is in our guide to adding HTML to a GoDaddy site. Note that custom code requires a paid plan, so Free-tier sites are limited to the built-in form.

If forms are the center of your operation — bookings, intake, orders — that's worth weighing before you commit to the platform at all. Our GoDaddy Website Builder review covers where the builder's simplicity helps and where it boxes you in. The rest of this manual's procedures live in the GoDaddy tutorials index.

Troubleshooting

The form submits fine but no email arrives. Where did it go?
Check three things in order: that Send Message To has the right address with no typo, that the notification isn't sitting in spam, and finally the Conversations inbox — submissions land there even when the email leg fails, so the message itself is almost never lost.
Can different forms send to different email addresses?
Yes. The notification address is set per form, not per site. Build a form on each page that needs one and give each its own Send Message To — no forwarding rules required.
Can I delete the email field to make an anonymous form?
No. The Email field and the Send button are fixed parts of the builder's form and can't be removed. If you need genuinely anonymous submissions, that's a job for an embedded third-party form tool.
Where do I find old submissions?
The Conversations web inbox keeps received messages in one place, independent of your email. Your notification inbox has its own copy of each alert, but Conversations is the ledger to search first.

Zoom out from this procedure: read the full GoDaddy Website Builder review or browse the tutorial index.