How do I put a lead form, a pop-up or a call button on my website?

Make a form

Open the project → Toolbox → Leads & clients → Lead capture and pick one of the tiles under Make a new one:

• Form in the page: a contact or quote form where you put it.
• Pop-up: appears in the middle of the screen after a delay or scroll depth; on phones it is a small card at the edge (or a slim bar, or not shown) and never shows on the first page someone opens.
• Slide-in: a card at the corner that does not cover the page.
• Sticky bar: a slim bar along the top or bottom with a button that opens the form.
• Call and WhatsApp button: round buttons that call your number or open WhatsApp.

The builder is one page with these sections:

1. Basics: the name (only you see it), the kind, optional start and end dates, and More websites it may work on (your project's own sites always count, with and without www).
2. Questions: name, e-mail, phone, postcode or area, the service you need (a choice), a message, the best time to call, your own questions (short or long answer, a choice, a tick box, a number or a date) and, when it is switched on for your workspace, a photo. Mark each as required or not. Add steps to split a long form ("About you", "The job").
3. Wording and consent: the title, text and button, the thank-you message (or a thank-you page to send people to), a link to your privacy notice and the consent line visitors must tick. Tick Also ask if they want news and offers for a separate, unticked marketing box: people who tick it get one e-mail to confirm it before they count as agreeing. Someone who ticks it without giving an e-mail address stays "not confirmed", so make the e-mail field required to collect confirmed consent. A phone number typed into a form never counts as agreeing to text messages: give that on the lead once you have confirmed the number. Tick Wait for the visitor's consent before showing if the form should stay hidden until your cookie banner says yes (see below).
4. Look: the button, background and text colours, the corner rounding, the font and your logo. A new form starts from your site's own look where SEOmise has it (from Landing pages, or your workspace brand); press Use my site's look again to go back to it.
5. When and where it shows (pop-ups, slide-ins, bars and call buttons): wait a number of seconds, or until they scrolled part of the page, spent time on the site, were idle, or are about to leave (computers only); only or never on some pages (/services/*); computers, phones or both; first-time or returning visitors; campaigns by their utm_source; and how often someone sees it again after closing it.
6. A/B test: other titles, texts or buttons for part of your visitors. Each visitor keeps seeing the same version.

Beside it, the Preview shows the form at computer and phone width (and each step and version), and Checks before publishing lists what to change: Google's guidance on pop-ups that cover the page, accessibility (titles, button wording, colour contrast) and privacy.

Put it on your site

Press Save, then Publish. Under Put it on your site, choose your platform (SEOmise shows the one it detected) and follow the steps:

• Any website: copy the code. Pop-ups, slide-ins, bars and call buttons go once on every page (in the page head or footer: the steps name your platform's own place for it). A form in the page goes where the form should appear, for example in a Custom HTML block in WordPress, a Custom Liquid section in Shopify, Embed HTML in Wix, a Code block in Squarespace or a Code Embed element in Webflow.
• WordPress with the SEOmise plugin: the [seomise_form key="…"] shortcode or the SEOmise form block.
• Laravel with the SEOmise package: @seomiseLeadForm('…') in a Blade view.
• PHP with the SEOmise PHP connector: seomise_lead_form('…').

If the form waits for consent, your cookie banner must give the signal once the visitor agrees: add the attribute data-consent-granted to the page's <html> element, or call seomiseConsent() from the banner's "accepted" step. Until then the form shows nothing and stores nothing in the visitor's browser. Without this option the form shows straight away; it sets no cookies.

When the form loads on a page of your site, the screen says Seen on your site with the page. Check my site reads a page you name and looks for the form's code. The form only works on your project's own websites.

Leads and results

With the Lead inbox in your plan, each enquiry arrives there (source Lead capture form) with the page it was sent from, the form and its version, and the campaign tags of the visit. It is stored encrypted, given to the right person, announced to your team, and marked when the same person asked before. The consent line the visitor ticked is kept with the lead. Photos are kept privately and deleted with their lead; open one from the link in the lead's answers.

Without the full Lead inbox, Lead capture comes with a basic Lead inbox: press See your leads on the Lead capture screen. It lists the leads from your forms; open one to call or e-mail them, mark it as e-mailed, log a call, move it to another step, or delete it when the person asks to be forgotten. Your owners and admins get an e-mail for each new lead. Leads from your ads and other forms, meetings, quotes and reports come with the full Lead inbox, shown locked with the way to add it.

Results shows views, starts, leads and the conversion rate of each form and version, leads per page, and, with Search Console or Google Analytics connected, the pages with visits but no leads: open one to add it to your To do. A figure that could not be measured says why instead of showing 0.

Your plan sets the submissions (and photos) a month; your owners and admins get one e-mail when most of them are used (80% unless our team set another share), and when they are used up your forms ask visitors to contact you directly until the 1st. Spam is kept out by a hidden trap, a minimum time to fill in the form, limits per connection (a whole home or office network counts as one) and per form an hour and a day, refusing disposable e-mail addresses, and the bot check when it is set up.

Building and changing forms needs a role that manages the project; anyone who can open the project can see the forms and results.