How to Add a Contact Form to WordPress (Block Editor + Plugins)

Every serious WordPress site needs a clear way for visitors to reach you. A contact form beats publishing a raw email address: messages land in your inbox, you can require the fields you need, and you can add spam filters without turning the page into a free-for-all.

This guide replaces the old “2010 Edition” framing. WordPress has moved on. You still create a Contact page, but you build the form either with blocks (when a form block is available on your site) or with a dedicated form plugin. Both approaches are valid. Pick the lighter option that matches how complex your form needs to be.

What you need before you start

Confirm that WordPress can send email from your host. Many shared hosts throttle or block wp_mail() unless you route mail through SMTP. If test messages never arrive, fix deliverability first; a working form that cannot send mail looks broken to users. We covered common deliverability fixes in How To Fix The Email Deliverability Issue In WordPress?.

Also decide who receives the messages. Use a monitored inbox, not a personal address you barely check. For teams, route to a shared mailbox or a helpdesk address.

Create a Contact page

1. In wp-admin, go to Pages → Add New.
2. Title it something clear, such as “Contact” or “Contact us”.
3. Add a short intro: who should use the form, expected response time, and any topics that belong elsewhere (sales, support, press).
4. Publish the page, then add it to your primary menu under Appearance → Menus (or the Site Editor navigation for block themes).

If your theme needs a custom page layout, start from a template rather than fighting the default single-page design. See How To Create A Custom WordPress Page Template when the stock layout is not enough.

Option A: Build the form with blocks

Core WordPress does not ship a full-featured contact form block the way Contact Form 7 or WPForms do. In practice, block-based forms usually come from:

• Jetpack — Form / Contact Form blocks with fields, notifications, and basic spam tools when Jetpack is active.
• Your theme or a page builder — some block themes and builders include form blocks. Treat those as theme features and test after theme updates.
• A form plugin that registers blocks — many modern form plugins expose Gutenberg blocks so you build the form in the editor instead of pasting a shortcode.

Typical block workflow:

1. Edit the Contact page in the block editor.
2. Insert the form block your site provides (Jetpack Form, plugin form block, and so on).
3. Add Name, Email, Subject, and Message fields. Keep required fields to a minimum.
4. Set the notification email to your monitored address.
5. Preview on mobile. Forms fail more often on small screens when labels and buttons collide.
6. Submit a real test from a private/incognito window and confirm the message arrives.

Use blocks when you want a simple inquiry form, you already run Jetpack or a form plugin with blocks, and you do not need multi-page flows, conditional logic, or heavy CRM integrations.

Option B: Use a form plugin

Choose a plugin when you need multiple forms, file uploads, conditional fields, payments, CRM/email marketing hooks, or stronger spam tooling. For a side-by-side look at popular options, start with 10 Best WordPress Contact Form Plugins Compared. Deeper product notes live in our WPForms Review and weForms Review.

A practical setup path that still works in current WordPress:

1. Install and activate the plugin from Plugins → Add New.
2. Create one form with Name, Email, and Message. Save.
3. Copy the shortcode or insert the plugin’s form block on the Contact page.
4. Configure the “To” address and a clear subject line (include the site name so you can filter mail).
5. Turn on spam protection the plugin supports (Akismet integration, reCAPTCHA/hCaptcha, honeypot, or built-in filters).
6. Send a test. Check spam folders. Fix SMTP if mail never leaves the server.

Contact Form 7 remains a solid free choice for sites that need several forms and are comfortable with markup-style field tags. WPForms Lite suits owners who want a drag-and-drop builder and fewer template edits. Pick one primary form plugin. Running two form plugins doubles assets and support surface for no gain.

Spam and abuse: do not skip this

Open contact forms attract bots. At minimum:

• Require a valid email field.
• Enable a honeypot or CAPTCHA that does not wreck accessibility.
• Keep Akismet (or equivalent) active if comments and forms share the same spam pipeline.
• Rate-limit if your host or security plugin offers it.
• Never auto-reply with sensitive account details.

If your inbox fills with garbage overnight, tighten filters before redesigning the page. Spam is an ops problem, not a design problem.

After publish: a short QA checklist

• Form submits successfully on desktop and mobile.
• Confirmation message or thank-you page appears.
• Notification email arrives within a few minutes.
• Reply-To uses the visitor’s address when your plugin supports it.
• No duplicate forms from theme plus plugin.
• Contact page is in the footer or main nav so people can find it.

When the old advice no longer applies

Older WPArena notes pointed readers at Fast Secure Contact Form and Cforms II. Those product lines are not the right default in 2026. Prefer actively maintained plugins listed on WordPress.org, with recent updates and clear support channels. If a plugin has not shipped updates in a long time, do not install it on a production site just because an old tutorial ranked it highly.

Bottom line

Create a Contact page. Prefer a block-based form when your stack already provides one and the form is simple. Move to a dedicated plugin when you need more than a basic inquiry box. Prove that email delivery works, then lock down spam. That sequence still solves the same problem this post covered in 2010 — visitors need a trustworthy way to reach you — without clinging to discontinued tools or a year stamped in the title.