Websites and Funnels

Funnel structure overview

When to use a funnel vs a website.

Intermediate20 min

Purpose

This SOP explains the difference between a website and a funnel, and helps you pick the right structure for a given goal. A website is for browsing; a funnel is for one specific action. Using the wrong one dilutes the goal. A website may still include forms and booking links, but it usually supports more than one visitor path. A funnel should reduce distraction. It should not send the visitor in five different directions.

When to Use This SOP

Building a new landing page
Deciding between a website page and a funnel
Creating a campaign-specific page
Creating a lead magnet path
Creating a booking path
Creating a paid offer path
Connecting forms, calendars, or documents to a front-end page
Reviewing pages that are getting traffic but not creating usable CRM records

Before You Start

Do not build the page before defining the path.

You should know:

Who the page is for
What the visitor should do next
Whether the page is educational or conversion-focused
What form, calendar, document, or payment step is needed
What source tag should apply
What workflow should start
What confirmation or thank-you action should happen
How the page will be tested before traffic is sent to it
A page with no CRM path is just a brochure.

Step-by-Step Procedure

1
Decide the page purpose
Write one sentence that explains what the page is supposed to do.
Examples:
- This page explains the business and routes visitors to contact or book.
- This page captures leads for a downloadable guide.
- This page drives consultation bookings from a campaign.
- This page collects event registrations.
- This page explains one offer and routes interested visitors into a form.
If the purpose is unclear, the structure will be unclear.
2
Choose website when navigation and education matter
Use a website page when the visitor may need to explore.
A website is better when the goal is:
- Brand trust
- General business information
- SEO and search visibility
- Multiple service explanations
- About page context
- Contact information
- Resources or articles
- Legal pages
- Broader navigation
A website can still include forms and booking links, but it usually supports more than one visitor path.
3
Choose funnel when one conversion path matters
Use a funnel when the visitor should follow one clear path.
A funnel is better when the goal is:
- Download a resource
- Book a consultation
- Register for an event
- Request a quote
- Apply for a program
- Buy one offer
- Complete one form
- Move from ad click to one next step
A funnel should reduce distraction. It should not send the visitor in five different directions.
4
Define the CTA path
Every page needs a clear call to action.
Examples:
- Book a call
- Complete the form
- Download the guide
- Request a quote
- Register for the event
- Start the application
- Sign the document
- Call the business
Do not use vague CTAs like "learn more" unless the destination is specific and useful.
The CTA should match the visitor intent and the page promise.
5
Connect the page to a CRM asset
Decide what the page connects to.
Common CRM paths:
- Form
- Survey
- Calendar
- Document
- Payment
- Chat
- Phone number
- QR code destination
- Email capture
- Lead magnet delivery
Do not publish a page until the connected CRM asset is tested.
6
Define source tracking
Every meaningful page or funnel should identify where the lead came from.
Tracking may use:
- Source tag
- Source field
- UTM values
- Hidden form field
- Unique link
- Campaign-specific form
- QR-specific link
Examples:
- source-facebook-ad
- source-google-search
- source-qr-event
- source-linkedin-post
- source-landing-page-guide
Source tracking helps reporting later. Without it, the business may know a lead arrived but not what produced it.
7
Build the thank-you path
A submission, booking, purchase, or document request should not end with silence.
Choose the right thank-you action:
- Inline confirmation
- Thank-you page
- Calendar redirect
- Download delivery
- Confirmation email
- SMS confirmation, if consent exists
- Next-step instructions
- Internal team notification
The thank-you action should match the promise on the page.
If the page says "get the guide," the guide should be delivered.
If the page says "book a call," booking should be obvious.
8
Check message consistency
The page, form, confirmation, and follow-up should all sound like the same path.
Review:
- Page headline
- CTA text
- Form title
- Thank-you message
- Confirmation email
- Reminder message
- Internal notification
- Follow-up campaign
Do not let the visitor click from a specific promise into generic messaging.
9
Test mobile experience
Most visitors will likely see the page on a phone.
Test:
- Page loads quickly
- Text is readable
- CTA is visible
- Form is easy to complete
- Calendar is easy to book
- Buttons are easy to tap
- Thank-you action works
- No content is cut off
- Links open correctly
A funnel that works on desktop but fails on mobile is not ready.
10
Send a test lead through the full path
Test from the page, not only from the CRM builder.
Confirm:
- Page opens
- CTA works
- Form submits or calendar books
- Contact record is created or updated
- Source tag applies
- Pipeline stage updates
- Workflow starts
- Confirmation sends
- Internal notification sends
- Thank-you page or redirect works
- Reporting source is visible
Do not publish or send traffic until the full path works.
11
Document the page or funnel
Create a page documentation note.
Include:
- Page or funnel name
- URL
- Purpose
- Audience
- CTA
- Connected form, calendar, document, or payment
- Source tag or tracking method
- Workflow connection
- Pipeline connection
- Thank-you action
- Owner
- Date tested
- Where traffic will come from
This makes future edits safer.

Checks Before You Finish

✓Page purpose is clear
✓Website vs funnel choice is intentional
✓CTA is specific
✓CRM destination is defined
✓Form, calendar, document, or payment path is connected
✓Source tracking is planned
✓Thank-you action is configured
✓Page message matches follow-up message
✓Mobile experience is tested
✓Full test lead was submitted
✓Contact record was reviewed
✓Workflow and pipeline behavior are correct
✓Page or funnel documentation exists

Common Mistakes

Watch for these

Building a funnel when the visitor needs a website page
Building a website page when the visitor needs one focused CTA
Sending every CTA to the homepage
Using vague CTAs with no clear next step
Connecting a page to an untested form
Forgetting source tracking
Forgetting a thank-you action
Sending traffic before mobile testing
Matching an ad to one promise and the page to another
Not checking the CRM record after a test submission
Leaving old funnel pages live after the offer changes

Related SOPs

← Back to SOP Library