Troubleshooting

Fix localbot existing-form forwarding, floating form installs, SMS delivery, domains, CSP, and test lead verification.

Common localbot setup issues and how to fix them.

Existing form forwarding

Use this section if your current form should send notification emails to localbot.

Confirm the localbot address is added as a recipient in the form notification settings.
Submit the actual website form once.
Check Dashboard > Lead source > Existing form for the latest received email.
If no email arrives, send a normal test email from your inbox to the localbot address.
If the inbox test arrives but the form test does not, the form notification settings are not sending to localbot.

localbot floating form

Use this section if the localbot form should appear on the website.

localbot form doesn't appear

Check the script tag placement. It should be before </body>, not inside <head>.
Verify the ID in the script URL. Log in to the dashboard and confirm the ID in your embed code matches.
Check the browser console. Open Developer Tools (F12) and look for errors. If you see localbot: form not found, the ID in the script URL is incorrect.
Check the Network tab for the script request. If the request to www.localbot.io/api/widget/... is blocked, missing, or shows a CSP violation, see "Content Security Policy" below.
Check if the page is published. On platforms like Wix, Webflow, and Framer, custom code only runs on the published site, not in the editor preview.
Clear your browser cache. Or open the page in an incognito window.

Content Security Policy (CSP)

If your site sends a Content-Security-Policy header, the browser will silently block the localbot form unless you allow the localbot.io origin.

Signs of a CSP block:

The form never renders, but the script tag is present in the HTML source.
Browser console shows: Refused to load the script 'https://www.localbot.io/...' because it violates the following Content Security Policy directive: "script-src ..."
The localbot form submits but nothing happens (connect-src is blocking the POST).

Add https://www.localbot.io to both script-src and connect-src in your CSP. Example:

Content-Security-Policy:
  script-src 'self' https://www.localbot.io;
  connect-src 'self' https://www.localbot.io;

In Next.js this is typically set in next.config.ts under headers(). In Vercel, you can set it via vercel.json or a headers() config. In WordPress/other CMS, CSP is usually set at the hosting/CDN level (Cloudflare, nginx) rather than in the CMS itself.

localbot form submits but no SMS

Check your phone number. Go to dashboard setup and verify your phone number is saved correctly, including the country code (e.g., +358).
Check billing and usage. Go to dashboard billing and confirm the account is active and inside the included lead conversation limit.
Check localbot setup. Go to dashboard localbot and confirm lead follow-up is enabled.

localbot form appears but looks wrong

CSS conflicts. If your site has aggressive global CSS resets, they may affect the form. The localbot form uses scoped styles, but some !important rules can override them.
Container too narrow. The localbot form has a max-width of 480px. If the container is narrower, the form will adapt, but it may look cramped below 300px.

Platform-specific issues

WordPress

localbot form disappears after theme update: Use the localbot plugin instead of manual code insertion. Manual changes to footer.php are overwritten by theme updates.

Squarespace

Code Injection not available: Requires a Business or Commerce plan.

Wix

localbot form doesn't appear in Wix editor: This is normal. Custom Code only runs on the published version of your site.

Shopify

localbot form doesn't appear after adding to theme.liquid: Clear Shopify's cache by re-saving the theme, or wait a few minutes.

Still stuck?

Last updated: 2026-05-23. Maintained by Benjam Indrenius.

On this page