Track SEO leads and customers in Close CRM
Organic search can look healthy in a traffic dashboard while the sales picture stays unclear. This guide shows how to pass organic-search context into Close CRM so each new lead carries its channel, drilldown, and landing-page details. You can then compare SEO with other channels and report on leads, customers, and revenue.
Four setup steps
The workflow has four linked stages. Each stage must work before the next one can produce trustworthy data. Confirm the current signup terms, trial length, and billing details before you begin, since these are set by the provider and can change over time. Then follow the steps in order and verify each one before moving on, because a gap at any stage will leave the later reports incomplete or misleading. Start by installing the tracking script and adding hidden fields to your lead-capture forms. The script snippet goes on the website, and the hidden fields go into the forms themselves. The field names are listed in the field map below. Form builders usually let you drag a hidden field type into the form or hide a regular field through its settings. Next, let the script classify the visit. When a visitor arrives, the script identifies the source in a way similar to analytics software. It groups the visit into a channel such as Organic Search, Paid Search, or Paid Social and stores that classification in the visitor's browser. Then capture the data with the form submission. On submission, the form tool records the hidden-field values alongside the visitor's typed details, such as name and email. Finally, send the record to Close CRM. Use a built-in connection or a connector such as Zapier or Make to move the form data into Close CRM. Once records are there, build reports on organic-search leads and customers.
Field map: what gets captured and what it feeds
The hidden fields fall into two groups. Channel fields describe how the visitor found the site; landing-page fields describe which content received them.
A useful distinction: Channel answers "how did they arrive?" while Landing Page answers "what content did they see first?" Keeping both lets you separate channel performance from content performance.
Worked example: a fencing manufacturer
Suppose a manufacturing marketer sees a visitor arrive from an organic Google search. The captured values could look like this:
- Channel: Organic Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: google.com.au
- Channel Drilldown 3: fencing manufacturers in Sydney (when available)
- Landing Page: sydneyfencing.com/blog/best-fencing-companies
- Landing Page Group: /blog
Read together, these values show both the discovery route and the content that earned the visit. If the visitor later submits a quote request, the same values travel with the lead into Close CRM. That makes it possible to ask which blog content produces leads, not merely which pages receive traffic.
Three reports worth building
Leads by Channel. Tally monthly lead counts and break them out by acquisition channel. Tracking the trend reveals whether organic search is gaining or losing ground, and it places SEO alongside paid search and paid social on one axis. A durable lead-volume edge for organic search is a cue to reconsider channel spend.
Customers from Organic Search by Landing Page Group. Tally monthly new customers, limited to organic search and grouped by site section such as Home, Blog, or Services. This distinguishes sections that turn visitors into buyers from sections that mostly produce pageviews.
Revenue from Organic Search by Landing Page. Attribute customer revenue to the entry page. This reveals which articles or pages generate the most money and informs what to publish next.
Troubleshooting: where the chain usually breaks
When SEO data is missing from Close CRM, identify which link failed rather than changing everything at once.
- No values in the form submission: the hidden fields are absent, misnamed, or not mapped in the form builder.
- Values present in the form tool but absent in Close CRM: the form-to-CRM connection is incomplete or the field mapping in the connector is wrong.
- Values present in Close CRM but no useful reports: the report grouping or filters have not been set up around Channel and Landing Page Group.
Checking in this order prevents a reporting problem from being mistaken for a tracking problem.
Customer outcome
Customer example worksheet
Record a customer example you can verify. Leave unknown fields blank until you have supporting evidence.
| Field | Your details |
|---|---|
| Customer and permission to use the example | ________ |
| Problem and starting point | ________ |
| Configuration or actions | ________ |
| Measurement period | ________ |
| Outcome and supporting evidence | ________ |
| Approval to publish | ________ |
Getting started
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
| Captured field | What it records | Report it supports |
|---|---|---|
| Channel | Broad source group, e.g. Organic Search, Paid Search, Paid Social | Leads by Channel |
| Channel Drilldown 1 | Search engine or platform, e.g. Google | Channel comparison |
| Channel Drilldown 2 | Source domain, e.g. google.com, google.com.au, google.co.uk | Source-domain review |
| Channel Drilldown 3 | Search keyword when available | Keyword-level review |
| Landing Page | Full URL of the entry page | Revenue by Landing Page |
| Landing Page Group | Section of the site, e.g. /blog | Customers by Landing Page Group |
Frequently asked questions
Why is the searched keyword sometimes blank?
The keyword drilldown is populated only when the search engine exposes it. When it is unavailable, the channel and landing-page fields still identify the visit and the content that received it.
How is organic search separated from direct traffic?
The script classifies each visit into a channel group. Organic Search is its own group, so it can be filtered and compared against Paid Search, Paid Social, and other channels in Close CRM reports.
Do I need a specific form builder?
No single form builder is required. The essential requirement is that the form supports hidden fields and can pass their values to Close CRM, either through a native connection or a connector such as Zapier or Make.