Track SEO Leads in Webflow
Organic search can send plenty of traffic to a Webflow site without telling you which of those visits became leads. This guide shows how to attach channel and landing-page attribution to each form submission, then turn that data into reports that show what SEO is actually producing.
Four setup steps
The workflow has four stages: install the attribution script, add hidden fields to your forms, let the script populate those fields, and confirm the data arrives with each submission. Each stage has a clear checkpoint, so you can verify progress before moving on.
1. Install the attribution script
The attribution tool provides a small code snippet to place on your site. On Webflow, paste it into the site's Custom Code area under Project Settings, or load it through Google Tag Manager if you prefer a tag-managed setup. Platform-specific installation walkthroughs are available in the help center for Webflow, WordPress, Squarespace, and Wix.
3. The script fills the fields
On arrival, the attribution tool reads the visitor's referrer and campaign signals and sorts them into a channel bucket — Organic Search, Paid Search, Paid Social, and similar — keeping that label in the browser for the rest of the session. If the visitor goes on to complete a form, the stored label and its supporting details are copied into the hidden inputs at that moment. The copy includes the channel, the referring search engine, and the query string when the engine exposes it.
4. Confirm the data is captured with each lead
On submission, the organic search values the attribution tool wrote are stored alongside the lead's name, email, and other form details. From there you can forward the data to a CRM, include it in notification emails, or keep it in a database or spreadsheet. That gives you a per-lead record of where the lead came from and how SEO is performing.
What each lead records
Two families of data are attached to every lead: the channel that brought the visitor, and the content that brought them. Channel answers 'where did this come from?'; landing page answers 'which page did the work?'.
Worked example: a fitness equipment company
Suppose a marketing team at a fitness equipment company sees a visitor arrive from an organic Google search. The captured values would look like this: Channel = Organic Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = www.google.com.au; Channel Drilldown 3 = home gym setup guide (the keyword used, when available). On the content side: Landing Page = fitforce.com.au/blog/best-home-gym-equipment-2024; Landing Page Group = /blog. Those values show both the discovery path and the specific page that converted the visitor, which is the basis for deciding what content to produce more of.
Field-to-report map
Use this map to decide which fields to prioritize for the reports you actually plan to build:
- Channel → Leads by Channel (monthly channel comparison)
- Channel Drilldown 1 and 2 → search engine breakdowns within Organic Search
- Channel Drilldown 3 → keyword-level insight when the search term is available
- Landing Page Group → content-category performance (blog, services, product, homepage)
- Landing Page → individual page performance
If you only need channel-level reporting, the drilldown fields can wait. If you need to know which content converts, the landing-page fields are essential.
Ways to use the captured data
Once the attribution tool's values are stored with each submission, there are several practical destinations:
- View them in Webflow submissions: Site settings > Forms > Form submission data shows attribution alongside each lead's form details.
- Add them to email alerts so each notification shows where the lead came from.
- Push them to a CRM through automation tools such as Zapier or Make — for example Salesforce, Pipedrive, or HubSpot — to report on lead counts, customer conversions, revenue, and average deal size.
- Export to a spreadsheet: send the data to Google Sheets via Zapier, or download a CSV from the Webflow dashboard, then chart leads by search engine or keyword.
Three reports worth building
These three reports cover the most common questions a marketing team asks about SEO performance. Start with the one that matches your current decision.
Report 1: Leads by Channel
A monthly count of leads grouped by marketing channel — Organic Search, Paid Search, Paid Social, and others. Read across the rows to see which channels are actually converting visitors into leads, and whether organic is pulling its weight next to paid. When Organic Search keeps beating Paid Search while the ad budget dominates, this report is the evidence for shifting spend toward content.
Report 2: Organic Search leads by Landing Page Group
A monthly count of organic leads organized by page category — homepage, blog, services, product, and so on. Because it counts leads rather than sessions, it separates the categories that actually convert from the ones that merely draw traffic, so you can steer content and SEO work toward the page types that yield the most valuable leads.
Report 3: Organic Search leads by Landing Page
A per-page count of organic leads for each individual blog post or landing page. At this granularity you can see which specific articles and pages are doing the converting, rather than averaging across a whole category.
Troubleshooting: two different failure modes
When attribution looks wrong, first decide which problem you have:
- Form submits, but attribution fields are empty. The form is working; the script or hidden fields are not. Check that the snippet is present on the page, that the hidden fields exist in the form markup, and that field names match exactly.
- Form does not submit at all. This is a form or embed problem, not an attribution problem. Check the HTML Embed markup and the form's action settings.
Separating these two cases saves time, because the fixes live in different parts of the setup.
Pre-launch checklist
- Script snippet installed in Custom Code or via Google Tag Manager
- All six hidden fields present on every lead form
- Field names match the expected names exactly
- A test submission shows populated attribution values
- At least one destination (CRM, email, or spreadsheet) receives the data
- One report built against the captured fields
Getting started
If you have been trying to measure how many leads SEO actually produces and how that number trends over time, attaching attribution to Webflow form submissions gives you a direct answer. Setup is quick, and the resulting reports make it possible to compare channels and content categories on lead outcomes rather than traffic alone.
Frequently asked questions
What does the attribution tool actually do?
The attribution tool classifies each visitor's source the way Google Analytics does — assigning a channel such as Organic Search, Paid Search, or Paid Social — and stores that classification in the browser. When the visitor submits a form, the values are written into hidden fields so the lead record carries its source.
Will I always see the search term a visitor used?
No. The search term is captured only when it is available. Channel and landing-page data are the reliable fields; keyword data is a bonus when the search engine passes it through.
Where does the script go in Webflow?
Paste the snippet into the site's Custom Code area under Project Settings, or load it through Google Tag Manager. Both approaches are supported.
How do I add hidden fields to a Webflow form?
Insert them manually using the HTML Embed element. The help center has step-by-step instructions for Webflow hidden fields.
Can the data go into my CRM?
Yes. Automation tools such as Zapier or Make can push the values the attribution tool captured into CRMs including Salesforce, Pipedrive, and HubSpot, which lets you report on lead counts, customer conversions, revenue, and average deal size.