Why Your Website Isn't Booking: A Diagnostic

Nobody can tell you why your website is not booking trips, including me, until four numbers exist. How many people arrive. How many of them reach the page where they could act. How many act. And how fast you answer the ones who do. Without those you are guessing, and guessing has a predictable failure mode: guides rebuild the thing that bothers them personally, which is usually the design, and the actual leak is somewhere else entirely. All four numbers are free to collect and most of the collecting is already done and sitting in tools you have not opened. This article is the order to do it in, and what each answer means.

Why start with measurement rather than a redesign?

Because the four possible diagnoses need completely different responses and cost wildly different amounts. Nobody is arriving is a visibility problem. Everybody arrives and nobody acts is a conversion problem. They act and you answer in three days is not a website problem at all.

Rebuilding a site fixes exactly one of those. If your problem is that 40 people a month find you and none of them should be expected to fill a season, a beautiful new site is 40 people looking at something nicer.

The reason guides skip this step is that measurement feels like delay and rebuilding feels like progress. It is the opposite. An afternoon with four numbers routinely saves a five-figure decision.

You also need the baseline for a second reason: without it you cannot tell afterwards whether anything you did worked. Whoever you hire, and whatever you change, the before number is the only thing that makes the after number mean anything.

Salmon Chaser, WI

How do you find out how many people arrive?

Google Search Console, which is free, and whatever analytics your site already has. Search Console tells you what queries you appear for, how often, and how often anybody clicks.

Search Console is where the first two of those live. Look at three things in it. Total clicks over the last twelve months. The queries producing them. And the pages receiving them. Those three answer whether you have a visibility problem and, if so, what kind.

The pattern to look for is whether people find you by name or by need. Traffic dominated by your business name means you are being found by people who already know you, which is a referral machine rather than an acquisition one. Traffic from queries about your water and your species means strangers are finding you.

Both are fine and they mean different things. A site living entirely on name searches is not failing at conversion, it is not being seen, and no amount of copywriting changes that. Where local visibility actually comes from is a separate subject covered across the guide websites collection.

What number counts as too little traffic?

There is no published benchmark for this industry and I am not going to invent one. What you can do instead is work backwards from your own capacity, which gives a real answer specific to you.

Take the days you need to sell. Assume, pessimistically, that a small percentage of visitors ever contact you and a portion of those book. Multiply out and you get the traffic you need for the website alone to fill those days.

The number is usually larger than guides expect, and that realization is itself the diagnosis. If filling 30 days requires several hundred qualified visitors a month and you get 60, the site is not underperforming. It is under-supplied.

Do not treat that as defeat. It reframes the work from fixing the site to being findable, which is a different project with a different timeline, and it stops you spending money on the wrong one.

How do you tell whether people reach the booking path?

Compare the page views on your homepage against the page views on your booking or contact page. The ratio between them is the single most diagnostic number on the whole site.

If a large majority of visitors never reach the booking page, the problem lives in the pages between. Usually that is one of three things: they cannot find rates, they cannot tell which trip applies to them, or the path to booking is not obvious from where they landed.

Check the third one first because it is the cheapest to fix. Load your own site on a phone and count the taps from landing to booking. More than two and you have found something.

The rates problem is the most common and the most avoidable. Somebody who cannot establish what a day costs will often leave to check a competitor and not come back, and whether to publish rates at all is argued out in the pricing piece.

What if they reach it and do not act?

Then the booking page itself is the suspect, and there are only a few things it can be. Too many fields, a required account, a missing price, a missing phone number, or a form that fails silently on a phone.

Test the silent failure first, because it is invisible and it is more common than anybody admits. Submit your own form from your own phone, on cellular, and confirm the message actually arrives. Do it once a season.

If the form works, the next suspect is length. A booking form asking for information you could get on the phone afterwards is trading completions for convenience, and the specifics are in the booking page piece.

The last suspect is trust rather than mechanics. Somebody about to send a deposit to a stranger wants a face, a phone number, a cancellation policy and evidence that other people have done this. If those are missing, the page is asking for commitment without having earned it.

How fast do you answer?

Open your sent folder and measure it, because this is the one leak that has nothing to do with your website and is frequently the largest. Take the last twenty inquiries and calculate the gap between arrival and your reply.

The classic study on this is a Harvard Business Review piece from March 2011 whose stated finding is that most companies are not responding nearly fast enough to online queries. I should be straight about its limits: the full article is behind a paywall, so I am citing the abstract rather than the underlying figures, and it is fifteen years old and not about fishing.

What makes it worth mentioning anyway is that the direction is uncontroversial and the mechanism is obvious in this industry specifically. Somebody planning a trip contacts three guides in one sitting. The one who replies first is talking to a person who is still deciding. The one who replies Thursday is talking to somebody who has booked.

Measure yours before you conclude anything. If your median reply is under an hour during the season, this is not your leak and you can stop looking here. If it is two days, no website change will outperform fixing it.

What about speed and stability?

Run your own URL through PageSpeed Insights, which is free, and read the field data rather than the score. Google publishes three specific targets. Loading, measured as largest contentful paint, should land inside 2.5 seconds. Responsiveness, measured as interaction to next paint, should sit at or under 200 milliseconds. Visual stability, measured as cumulative layout shift, should stay at or below 0.1.

Those three are the Core Web Vitals and Google's own documentation states the assessment method: a page passes if it meets all three targets at the 75th percentile of page loads, measured separately for mobile and desktop.

That percentile clause carries more weight than the three targets do. What is being asked is not whether the site feels quick on your own handset on home wifi. It is whether three quarters of everybody loading it got an acceptable experience, and that population includes every person standing outside on cellular.

Layout shift is the one guides never think about and the one that costs bookings most directly, because a button that moves as somebody reaches for it produces a mis-tap rather than a booking. The full argument, including what to do about it, is in the speed piece.

Which measurement should you trust when they disagree?

Field data over lab data, always. Google draws that distinction explicitly and its own guidance is that lab measurement, while essential during development, is not a substitute for field measurement.

Performance moves with the handset, the signal, whatever else is running, and what the visitor does once the page arrives. None of that exists inside a simulated load, which is why a tool running one cannot see it.

Practically, this means the score at the top of a speed report is the least useful thing in it. Scroll past it to the real-user data, which is collected from actual Chrome users and is the thing Google itself uses.

The same principle applies to every other number here. Your own impression of your site is lab data. Your sent folder, your analytics and your booking count are field data, and where they disagree the field wins.

Healing Waters, MT

What order should you fix things in?

Reply time, then the booking page, then speed, then visibility. That order is by cost and speed of payoff rather than by importance, and it is deliberately backwards from what most people do.

Reply time is first because it is free, takes effect immediately, and is frequently the biggest single leak. Setting up an automatic acknowledgement and a habit of answering from your phone costs one evening. The arithmetic on why that beats almost anything else you could do is in the response time piece.

The booking page is second because it is a small surface with a large effect, and most of the fixes are deletions rather than additions. Removing three fields is an afternoon.

Visibility is last, not because it is unimportant but because it is the slowest and most expensive, and because it multiplies everything above it. Sending more people to a site that loses them is the most expensive mistake available in this whole sequence, and the sequencing argument is made in full in the solo operator piece.

What does a healthy set of numbers look like?

Traffic that grows year over year, a booking page reached by a meaningful share of visitors, inquiries that convert at a rate you can state, and a reply time under an hour in season. Those are shapes rather than benchmarks, and the shape is the point.

Growth year over year matters more than any absolute figure, because it is the only comparison that controls for your season, your water and your weather. Twelve months against the same twelve months is the only fair test.

The conversion figure you want is not visitors to bookings, it is inquiries to bookings, because that one is entirely about you. If ten people ask and two book, the question is what happened in those eight conversations, and that is answerable by reading them.

Go and read them. The last twenty inquiries that did not convert will tell you more than any tool, because you will see the actual reasons in plain language: the date was gone, the price was more than expected, they never replied after your answer.

What can you check in ten minutes right now?

Five things, all on your own phone, all free. Load the site on cellular and count the seconds. Count the taps to booking. Submit your own form. Find your rates. Call your own number.

Do it away from your desk and off wifi, because the desk version of your website is not the one your clients use. A site that loads instantly on a laptop can take fifteen seconds on a weak signal in a parking lot.

Calling your own number is the one everybody assumes is fine. Numbers get ported, forwarding gets broken by a phone upgrade, and a number that rings nowhere sits on a website for a year before anybody notices.

Write down what you find as you go rather than trusting yourself to remember. Five findings in a note is a work list, and it is usually enough to occupy a week of evenings that will do more than a rebuild.

What do experienced guides do differently?

They know their inquiry count without looking. And they change one thing at a time.

Knowing the count is the difference between running a business and reacting to one. A guide who can tell you they had 61 inquiries last season and booked 38 of them has a conversion rate, a baseline, and the ability to tell whether anything they try works.

The one-thing-at-a-time discipline is what makes measurement worth doing at all. Rebuild the site, change the rates and start running ads in the same month, and whatever happens next is uninterpretable.

Experienced operators also write down what they expect before they change something. Not as ceremony, but because a prediction written in advance is the only protection against remembering the result as whatever you already believed. Two lines in a notebook is enough.

What are the common mistakes?

Diagnosing from the design. Rebuilding before measuring. Buying traffic to cover a conversion leak. And judging any of it on one bad month.

Diagnosing from the design is the most human error here, because your website is the part of your business you look at most and dislike most. Personal dissatisfaction with how something looks is not evidence about why bookings are down.

The one-bad-month error is the statistical version of the same mistake. A guide business has enormous seasonal and weather variance, and a quiet June may be a quiet June rather than a signal. Compare against the same period last year, not against last month. And be honest about which days are actually the problem, because a season that looks half-empty in aggregate is usually a specific weekday pattern, which is the whole subject of the Tuesday problem piece.

The last one worth naming is fixing the thing you know how to fix. Guides who are comfortable with photographs replace the photographs; guides who like writing rewrite the copy. Neither is wrong, and neither is diagnosis. The catalogue of what actually goes wrong on these sites is in the mistakes piece.

What surprises people?

That the biggest leak is usually not on the website. That the thresholds are measured at the 75th percentile rather than on average. And that the whole diagnosis is an afternoon's work with free tools.

The reply-time finding is the one that changes behaviour most, because it costs nothing to fix and it is entirely within your control. Guides spend thousands on sites while losing inquiries to a two-day response habit that no amount of design will compensate for.

The percentile point deserves its own thought. Designing for the average visitor means accepting that a quarter of people get an experience you never tested, and that quarter disproportionately includes people standing outside on a phone, which is exactly who is deciding to book a trip.

The last surprise is how boring the answer usually is. Not a redesign, not a rebrand, not a new platform. Answer faster, delete three form fields, resize the images, and then go and get found.