Organic Search Leads
An Organic Search Lead is a record in Salesforce where the Lead Source field is set to a value that represents unpaid search engine traffic, usually a custom picklist value named Organic Search.
Definition
An Organic Search Lead is a record in Salesforce where the Lead Source field is set to a value that represents unpaid search engine traffic, usually a custom picklist value named Organic Search. The record is typically created when a prospect finds your site through a regular search result, not a paid ad, and then submits a Web-to-Lead form.
Organic Search is not one of the standard Lead Source values that ship with Salesforce. Admins add it as a custom value so marketing and sales can separate SEO-driven prospects from paid, referral, and list-based ones. Once the value exists, every lead tagged with it becomes reportable, which is how teams measure what search-driven content is actually worth.
How Organic Search becomes a trackable Lead Source
Lead Source is a picklist, and Organic Search is a value you add
Lead Source is a standard field on the Lead object. Out of the box it ships with five picklist values: Web, Phone Inquiry, Partner Referral, Purchased List, and Other. There is no Organic Search value by default, so a Salesforce admin creates it as a custom picklist value. You add it in Setup under Object Manager, Lead, Fields and Relationships, Lead Source, then New under the value list. One detail trips people up. Lead Source shares its StandardValueSet with the Account object's Account Source field. The two fields pull from the same set of values. When you add Organic Search for leads, plan for how it should appear on accounts too, since both reference the same controlling value set. If your org uses record types, you also assign the new value to each active record type, or it will not show on those layouts. Once the value is live, you can map it onto a Web-to-Lead form or set it through automation so the right records get tagged without a rep typing it by hand.
Web-to-Lead is the usual capture point
Most Organic Search Leads land through Web-to-Lead. This feature generates an HTML form you embed on your website. When a visitor submits it, Salesforce creates a Lead record from the field values. You build the form in Setup by picking which lead fields to include, then Salesforce gives you the HTML to hand to your webmaster. Web-to-Lead caps daily volume at 500 leads per organization. Submissions beyond that are held, and the default lead creator is notified so records are not silently dropped. The form supports a default Lead Source, a Campaign association, and an optional return URL. To keep junk out, reCAPTCHA verification is on by default and blocks spambots from flooding your pipeline with fake records. There is also a hidden debug field you can uncomment while testing, so you can confirm the form posts correctly before going live. For Organic Search specifically, the form sets Lead Source to your custom value, or you maintain separate forms or hidden fields per channel.
Setting the value: form fields, hidden inputs, and automation
There are three common ways an Organic Search value gets onto the record. The simplest is a Lead Source field on the form itself, defaulted to Organic Search, so anything submitted from your organic landing pages is tagged. This works when a page only ever receives organic traffic. The second is a hidden input. You drop a hidden field into the generated Web-to-Lead HTML that carries Lead Source as Organic Search, so the visitor never sees or changes it. Marketing teams often pair this with separate landing pages per channel, each hardcoding its own source. The third is automation. A Flow on the Lead object can inspect referrer data, UTM parameters captured into custom fields, or the originating page, then set Lead Source after the record is created. Automation is the most accurate route because it does not rely on a static page assumption. It also lets you enrich the lead with finer detail, such as the exact campaign or keyword group, while still rolling everything up to the Organic Search bucket for high-level reporting.
Why teams separate organic from paid search
Organic and paid search look similar to a visitor but mean very different things to a marketing budget. Paid search costs money per click and stops the moment you stop spending. Organic search is earned through SEO and content, and it tends to compound over months. Lumping both into a single Web or Search value hides which one is actually producing pipeline. A dedicated Organic Search value answers a sharp business question: what is our SEO work worth in real opportunities and revenue, separate from ad spend? Without it, you cannot defend a content budget or prove that a blog series turned into closed deals. This is the foundation of closed-loop reporting, where you trace a lead from its first touch all the way to won revenue. Accurate source data at the point of capture is what makes that loop possible. If the value is wrong or missing at lead creation, no downstream report or dashboard can fix it, because the source of truth was never recorded correctly in the first place.
Reporting and dashboards on Lead Source
Once Organic Search Leads exist, the payoff is reporting. A simple Leads report grouped by Lead Source shows volume per channel at a glance. Add a date filter and you can watch organic lead flow rise or fall as your SEO efforts mature. Because Lead Source carries forward when a lead converts, the value also lands on the resulting contact and opportunity, so you can follow organic prospects deep into the sales funnel. For revenue attribution, many teams pair Lead Source with Salesforce Campaigns. Lead Source is a single first-touch label, while Campaigns and Campaign Members let you track multiple touches and tie spend to outcomes through campaign ROI reports. A practical setup uses Lead Source for the broad channel and a Campaign for the specific initiative. Build a dashboard that trends organic leads over time, shows conversion rate by source, and surfaces won revenue per source. That view is what turns Organic Search from a label into an argument for where the next marketing dollar should go.
Keeping the data clean over time
A Lead Source field is only as useful as it is consistent. The most common failure is value sprawl, where Organic Search, Organic, SEO, and Search all coexist because different forms and reps entered slightly different things. Pick one canonical value and lock it down. Make Lead Source a required field where it makes sense, and prefer automation or hidden inputs over free typing so the value cannot drift. Audit periodically. Run a report grouped by Lead Source and look for near-duplicates or a swollen Other bucket, which usually signals records that should have been tagged Organic Search but were not. If you rename or consolidate values, remember the shared value set with Account Source, and update reports and any automation that references the old text. Governance matters more than cleverness here. A boring, well-maintained picklist with one organic value beats an elaborate scheme that nobody keeps current. Clean source data is what every marketing decision downstream quietly depends on.
Set up Organic Search as a Lead Source
Organic Search is a custom Lead Source value plus a capture path. Add the picklist value first, then wire Web-to-Lead so organic submissions carry it automatically.
- Add the Organic Search picklist value
In Setup, open Object Manager, Lead, Fields and Relationships, then Lead Source. Click New under the value list, enter Organic Search, and save. If you use record types, assign the value to each active record type so it appears on those layouts.
- Decide how the value gets set
Choose one method per organic landing page: a Lead Source field on the form defaulted to Organic Search, a hidden input hardcoding the value, or a Flow that reads referrer or UTM data and sets it after creation. Hidden inputs and automation keep the value consistent.
- Generate the Web-to-Lead form
In Setup, go to Web-to-Lead and create a form. Include the fields you want, set a default Campaign if relevant, keep reCAPTCHA enabled, and copy the HTML. Add or confirm the Lead Source value in the markup before handing it to your webmaster.
- Test, then build the report
Uncomment the hidden debug field to confirm submissions post correctly, then submit a test lead. Verify Lead Source reads Organic Search on the record. Finally, create a Leads report grouped by Lead Source and a dashboard that trends organic volume over time.
The Organic Search picklist value you add to the Lead Source standard field; it also affects Account Source via the shared value set.
The Lead Source carried by a generated form or hidden input, so organic submissions are tagged without rep input.
On by default; blocks spambots from creating fake leads through the public form. Leave enabled for any organic landing page.
An optional Campaign linked at submission, used alongside Lead Source for ROI and multi-touch attribution reporting.
- Organic Search is not a standard value; if it is missing, an admin never added it to the Lead Source picklist.
- Lead Source shares its value set with Account Source, so changes to one field affect what the other offers.
- Web-to-Lead caps at 500 leads per day per org; overflow is held and the default lead creator is notified.
- Watch for value sprawl: Organic Search, Organic, SEO, and Search as separate entries break your reporting.
Prefer this walkthrough as its own page? How to Organic Search Leads in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Organic Search Leads.
- Guidelines for Setting Up Web-to-LeadSalesforce
- Lead Field ReferenceSalesforce
Hands-on resources to go deeper on Organic Search Leads.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. In Web-to-Lead, what are organic search leads?
Q2. What is organic search tracked as on these Web-to-Lead records?
Q3. Which Salesforce feature produces organic search leads from a website visitor?
Discussion
Loading discussion…