WordPress email form not working: check the embed

Most email signup boxes in WordPress are not part of WordPress at all. The form is an embed, a short piece of code your email service gives you, which loads its own script from its own host. A consent plugin treats that script as a third-party tracker and waits for the visitor's choice before it lets the script run. Once a visitor declines, the box may never render, or it renders with a button that sends nothing. You accepted cookies on your own browser long ago, so you see the box every time. Nothing on your screen tells you a visitor was refused the form.

• Open the page in a private window and decline the cookie prompt. Is the signup box still there?
• Open it again and accept. Does the box appear, and does the button respond?
• Submit a new address. Does a message ask you to check your inbox?
• Look for that confirmation email in the visitor's inbox. Did it arrive, and does the link work?
• Note whether the box, the button or the confirmation is where it stops.

When you paste signup code into a WordPress page or widget, the box it draws comes from a host you do not run. The page holds a script that fetches the form, and sometimes a frame that shows it. Every part of that chain can be stopped by something on your site: a consent plugin that holds scripts back, a security setting that blocks frames from other hosts, or an ad blocker in the visitor's browser. Because the box depends on a second host, a failure looks like an empty space on your page, not an error.

An empty space means the embed never loaded, which points at the consent choice or a blocked script. A box that appears but whose button does nothing means the script ran and the submit was stopped, often by a blocked request to the other host. A message that asks you to check your inbox, with no email arriving, means the form worked and the confirmation step failed. Each one needs a different fix, so write down which of the three you saw.

Test them one at a time. First decline cookies in a private window and see whether the box renders. Then accept cookies in a new private window and submit a new address. Last, look for the confirmation email. Your own inbox proves little here, because you accepted cookies long ago and may already be on the list. Use an address that has never signed up, and keep a note of the time you submitted it, so the email you find is the one this test sent.

A simulated visitor makes the same first visit a stranger makes. It reports whether the box appeared, whether the button responded, and whether a confirmation email reached the inbox it was given. That last part matters, because a signup that looks finished on screen can still leave a subscriber with no way to confirm. The test follows the form to the email, but it does not show how your email service has set up its list.

Adding a consent tool, a security plugin or a new theme can block the embed without any error on your own screen. After each change, run the same visitors through the signup and compare where each one stopped. Include one visitor who declines cookies, since that is the path a change is most likely to break.