A visitor who wants to book a service should not have to read a menu first.
On a lot of the sites I look at, it does anyway. A menu, a services page, a second services page for the same service split out by location, a contact page, then a form that asks for information the visitor already gave on the fit-call page.
Three clicks is the number worth aiming for. Not because of a study. Because every click past that is a chance to lose the visitor to a second tab, a phone call they never make, or a change of mind.
That number should embarrass more of the industry than it does.
Click Depth Is Just Friction
Click depth is the number of clicks between where a visitor lands and the thing they came to do: book, call, or buy. It sounds like a technical term. It is really just a count of chances to quit.
People quit for reasons that have nothing to do with price or trust. A slow page. A confusing label. A form that resets when the back button gets hit by accident. Google and AI tools like ChatGPT read the same path differently, but they read it. A page three clicks deep gets read and understood less often than a page one click from the homepage.
Where the Extra Clicks Hide
Extra clicks hide in a few usual places. A mega menu with every service listed twice, once under the department and once under the location. A team page, an about page, and a company page that all cover the same three facts. A quote form behind a second form that only asks to confirm interest in getting a quote.
- Duplicate navigation: the same service linked from the header, the footer, and a sidebar, none of them leading anywhere different.
- Buried contact information: a phone number that only shows up on the contact page, not the page the visitor is already reading.
- Confirmation before commitment: a form that asks a visitor to agree to be contacted before it lets them say what they actually need.
None of that looks like friction from the inside. It looks like being thorough. It is still friction.
What a Crawler Reads the Same Way
A crawler does not get tired of clicking, but it does weigh pages by how many links point to them and how many clicks separate them from the homepage. A page nine clicks deep rarely gets treated as important, no matter how good the page is. An earlier post here on internal linking covers how that weighting works in more detail.
That math is strange to a shopper and reasonable to a program weighing thousands of pages at once. A business that wants people to find it and choose it does not get to build one structure for a visitor and another for a crawler. The flattest version, the one with the fewest clicks between the homepage and the thing a visitor came to do, tends to win on both sides.
Fewer Clicks, Not More Pages
The fix is almost never more pages. It is fewer, each one doing more work. A service that used to need three pages, one general, one for a sub-service, one for a location, can usually live on one page written to answer all three questions a visitor was clicking around to find.
Combining pages is not the same as cutting content. The words that were spread across three thin pages move onto one page built to carry them. A visitor gets the same information in one stop instead of three, and a crawler gets one strong page instead of three competing weak ones.
Cutting a click sounds small. It rarely is. Try it anyway.
What I Check First
When I audit a site, the first thing I do is click through it the way a new visitor would, from an ad or a search result, not from the homepage. I count every click to the point where the visitor can actually ask for the thing they came for.
If that number comes back at four or more, I look at which pages are doing the same job twice before I touch a single pixel of design. A rebuild that adds motion and a better color palette on top of the same buried form fixes the wrong problem.
The good news is that this part of the fix is cheap relative to a full rebuild.
A cinematic website still has to pass this test. Motion and a custom look earn their keep only if the path underneath them is short. That is the part of a Web Experiences build that happens before any animation gets decided.
If your site is asking a visitor to click more than it has to, that is worth fixing before anything else gets touched.