WordPress

Formcrest works on any WordPress site — self-hosted or WordPress.com — through a Custom HTML block. No plugin to install, nothing to keep updated.

Add the form with a Custom HTML block

  1. Edit the page or post where the form should live.
  2. Add a block and pick Custom HTML (type /html in the block inserter).
  3. Paste your form markup, with the action pointed at your Formcrest endpoint:
<form action="https://api.formcrest.com/v1/submit/abc123" method="POST">
  <p><label>Name<br /><input type="text" name="name" required /></label></p>
  <p><label>Email<br /><input type="email" name="email" required /></label></p>
  <p><label>Message<br /><textarea name="message" rows="5" required></textarea></label></p>
  <input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off" />
  <p><button type="submit">Send</button></p>
</form>

Use the block's Preview tab to check the rendering, then publish. The hidden _honey field is our spam honeypot — keep it in.

Where visitors land after submitting

By default we redirect to your form's success URL (set it in the form's settings in the dashboard) or to our hosted thank-you page. To send visitors back to a page on your own site — say a /thank-you page you made in WordPress — either set that URL in the dashboard or add it as a hidden field:

<input type="hidden" name="redirect" value="https://your-site.com/thank-you/" />

Styling

The markup above inherits your theme's styles, since it's ordinary HTML inside your content. If your theme ships button classes (e.g. wp-element-button in block themes), add them to the submit button to match the rest of the site.

Page builders and classic editor

The same snippet works anywhere raw HTML is accepted: the Classic editor's Text tab, Elementor's HTML widget, Divi's Code module, or a Custom HTML widget in a sidebar or footer. WordPress.com requires the Premium plan or higher for custom HTML on some sites — check your plan if the block is unavailable.

Notes

  • There is no Formcrest WordPress plugin today — and you don't need one. Your form posts directly to our API; there's no PHP to run on your server.
  • Don't use WordPress's built-in comment/contact plugins alongside this form for the same purpose — double spam filtering can swallow legitimate messages.
  • If you restricted your form with a domain whitelist, remember to add your WordPress site's domain.

Next steps