Funnel web design means one page doing one job properly

1 day ago
3 min read

Updated: 18 hours ago

Introduction

Funnel web design is the practice of building pages around a single intended action rather than around everything a business would like to say. It is less a visual discipline than an editorial one — most of the work is deciding what to leave out.

The usual failure is a page that tries to introduce the company, list every service, display testimonials, carry a newsletter signup and request an enquiry. Each element is defensible on its own. Together they leave the visitor with no clear next move, and the page converts worse than a plainer one would.

None of this requires a designer. It requires deciding what each page is for.

1. Funnel web design gives every page one job

The organising rule.

Write the job at the top of the page in your notes before designing anything. If you cannot state it in one sentence, the page is not ready to build. Two jobs means two pages.

2. Match the page to the stage

The mapping.

Someone arriving from a search for a problem needs something different from someone who came to compare prices. The stage decides the content. This is the whole reason to think in funnel terms at all.

3. Put the action where the decision happens

The placement principle.

Not only at the bottom — beside the point in the page where the reader is likely to be convinced. Repetition of one action is fine; competing actions are not.

4. Remove before adding

The main technique.

Most pages improve more from taking three elements off than from adding a new section. Navigation, sidebars, unrelated offers. Start with subtraction every time.

5. Load speed is a design decision

The technical half.

Large images, embedded video and tracking scripts cost you visitors before any of the design matters. Weight is part of the design. Test on a phone on mobile data rather than on your desk.

6. Write the first line for the person who just arrived

The opening.

It should confirm they are in the right place and say what this page will do for them. Most first lines describe the company instead. That is the commonest single fault.

7. Keep the form as short as the stage allows

The friction point.

Every field costs you submissions, and most fields exist because somebody once wanted the data. Ask for what you need to take the next step and no more. The rest can be collected in conversation.

8. Design for the phone first

The realistic constraint.

Most first visits arrive on a small screen, where a layout that works on a monitor becomes a long scroll. Build the narrow version first. The wide one is easier to derive than the reverse.

9. Judge changes by what the page is for

The measurement.

If the page exists to produce enquiries, count enquiries — not time on page, not scroll depth. One page, one job, one number. Anything else invites arguing about interpretation.

Be careful about stripping a page so far that it stops being credible. Removing every proof point and every explanation in the name of focus produces a page nobody trusts, and the objective is clarity rather than minimalism for its own sake.

Conclusion

Decide what each page is for, in one sentence, before anything else.

Match the content to the stage the visitor is at, put the action beside the point where they are likely to be convinced, take elements off before putting new ones on, treat page weight as part of the design and test it on mobile data, write the first line for the person who has just arrived rather than about your company, keep forms to the fields the next step actually needs, build the narrow layout first, and judge every change against the one number that page exists to move.