Your subscribe form on a WordPress site

Both Issue Mint snippets go into a Custom HTML block. Paste the script embed into one, publish the page, and the subscribe form appears in your newsletter’s own colour and body font, with no theme work and no plugin.

Copy either snippet from Settings, then the Subscribers tab, which shows both with a copy button and a preview of the form beside them. The script embed is the one to reach for on a WordPress site you host yourself.

Where the HTML goes

A Custom HTML block, in the block editor. Add a block, search for Custom HTML, and paste both lines of the snippet into it. The block keeps the markup as typed, which a Paragraph block does not.

That difference is the usual reason a pasted snippet turns up on the published page as visible code: it went into a paragraph, where the editor escapes it rather than letting it run. In the classic editor, use the Text tab rather than Visual, because Visual rewrites what you paste.

Which of the two snippets to use

The script embed, on any WordPress you host yourself. It confirms the signup in place rather than sending the reader off your page, it weighs under 10 kB, and it loads asynchronously, so a slow reply from us never holds up your page.

The plain HTML form is for pages where nothing of ours should run at all. It posts like any other form and the reader lands on Issue Mint’s thank-you page afterwards. The redirect field in Settings only accepts your newsletter’s own addresses, so a plain form cannot send readers to a thank-you page on your WordPress site.

What WordPress.com filters out

WordPress.com and a WordPress you host yourself behave differently here. On plans that do not include custom code, WordPress.com strips script tags out of page markup, and a stripped script tag leaves the empty container behind: no form, no error, nothing in the page source to explain it.

One script tag, however many forms

Issue Mint’s script mounts a form into every data-issuemint container on the page, so a single script tag can serve a form in your header and another further down.

A second copy of the script tag is the thing worth avoiding. Two copies loading alongside each other can both claim the same container before either has finished, which puts two forms where you wanted one. Paste the div wherever a form belongs and keep the script tag to one.

Checking it worked

Load the published page in a browser rather than in the editor, and subscribe with a real address. The signup reaches your list in a second or two, marked as coming from the embed, and with double opt-in switched on the reader is asked to confirm before they count as active.

A mistyped domain is refused in the field, with “We can’t find a mail server for that address”, so a test with an invented address will not appear on your list. That is the check doing its job rather than the form failing.