How to Embed a Systeme.io Form in WordPress in 2026
Keep WordPress as the public site and use Systeme.io for capture by embedding an Inline form or Popup form through the Script method. Test the resulting contact, follow-up and bot protection as one complete journey.
Keep WordPress for publishing while Systeme.io handles the lead database
You do not need to rebuild an established WordPress site simply to capture leads in Systeme.io. The platform can generate an external inline form or popup whose submissions enter the Systeme.io contact system.
This hybrid setup is useful when WordPress already handles SEO and editorial publishing while Systeme.io manages campaigns, tags and sales funnels. The key is testing the handoff between the external page and the Systeme.io follow-up.
Create an Inline form or Popup form step inside a Systeme.io funnel
Systeme.io's current external-form guide starts by adding an opt-in step using either Inline form or Popup form. Choose a template, edit the fields and configure the action the visitor should experience after submitting.
Keep the form short enough for its purpose. A newsletter or lead magnet usually needs fewer fields than a qualification form, and every unnecessary field adds friction before the contact reaches your database.
Use the Script integration and place it in the appropriate WordPress code area
After configuring the form, use the Script option to copy the code generated for an external site. An inline form can be placed inside an HTML-capable block or widget on the WordPress page where it should appear.
For a popup, Systeme.io instructs you to place the script in a header or footer code area so the popup code can load on the external page. Use the method supported by your theme, code-injection plugin or hosting setup.
Connect the signup to the right campaign, tag and destination inside Systeme.io
The embed is only the visible capture layer. Verify what happens after submission: whether the contact receives the intended tag, enters the correct campaign and reaches the expected confirmation or thank-you experience.
Use a fresh test email and inspect the resulting contact record. This proves that WordPress, the embed code and the Systeme.io automation are all connected rather than only confirming that the form renders visually.
Use the Script method when reCAPTCHA protection is required on an external form
Systeme.io's list-bombing guidance warns that reCAPTCHA does not work with its stripped Embedded form HTML method. For externally embedded forms that need CAPTCHA protection, the platform recommends using the Script integration instead.
If an old embedded form has been attacked by bots, remove obsolete code from the page source as well as from the visible layout. Hidden leftover form code can still expose the old endpoint even when visitors no longer see the form.
Test the WordPress page on mobile and complete a real opt-in before publishing
Open the live WordPress page on a phone and desktop browser, submit the form and confirm the redirect, contact creation and email follow-up. Check that the embed does not overflow its container or slow the page enough to disrupt the signup experience.
Repeat the test after major theme, caching or optimization changes. External scripts depend on the surrounding website environment, so a WordPress update can affect a form even when nothing changed inside Systeme.io itself.
Check these four signals.
✓The correct Inline form or Popup form step is configured
✓The Script integration is placed in an appropriate WordPress code area
✓A test signup creates the expected tags and campaign state
✓External forms that need reCAPTCHA use the Script method
Need the bigger picture before choosing a plan?
Open the current offer and check Systeme.io pricing, limits and features before deciding on a subscription.
Official sources for this guide
Software pricing and features can change. Review the official documentation below before choosing a product or plan.
