Trip Pages for Every Water You Run

A trip page is usually written to persuade, and that is the wrong job for it. By the time somebody reaches a specific trip they have already decided they are interested; what they are doing now is checking whether this particular day is for them. The most valuable function of the page is therefore letting the wrong person rule themselves out, quickly and without embarrassment, because a mismatched client costs you a day you cannot get back, a refund conversation, and sometimes a review written by somebody who had a perfectly accurate experience of the wrong trip. Write each page to disqualify honestly and it converts better, which is the counterintuitive part.

Why should a page try to lose people?

Because the alternative is losing them later at much greater cost. Somebody who books the wrong trip discovers it at the ramp, and by then you have committed a day, taken a deposit and created a problem that no amount of goodwill fully solves.

The economics are stark for a one-boat operation. You do not have the volume to absorb mismatches, and a day spent with somebody having a bad time is a day you could have sold to somebody having a good one.

There is a second effect that guides notice and rarely name. Pages that state limits honestly read as confident, because only somebody who knows their water well enough to say who it does not suit would write them.

Whoever remains is a better client too. A person who saw the wade described as hard and booked regardless has already accepted the difficult half, and the day runs differently as a result. The bio piece applies the same candour to describing yourself.

Feelin Fishy, WI

How many trip pages should you actually have?

One per genuinely different day, which is fewer than the number of things you could list and more than one. The test is whether somebody choosing between two options would need different information, not whether the trips have different names.

A half day and a full day on the same water are usually one page with two options, because everything except duration and price is identical. Two different rivers are two pages, because the access, the species, the season and the difficulty all differ.

Getting this wrong in the direction of too many pages is the more common error. Eight thin pages that each say a little dilute the one or two that matter, and each of them has to be maintained forever.

Err the opposite way and you get a single sprawling page in which nobody locates their own trip. The page list covers how these fit together.

What is the hardest thing to write honestly?

What you will catch. Every instinct pushes toward the best day, and every client compares their actual day against whatever the page implied.

Advertising rules touch this, though they were written with no fishery in mind. The federal position runs roughly like this: put an unusually successful customer in your advertising, hold no evidence that their outcome is the normal one, and you owe the reader a plain statement of what people usually get instead.

Be careful about how far that stretches, and I would rather understate it. The guidance addresses endorsements, so a client's testimonial about a spectacular day sits far closer to the line than your own description of the trip. Rules here get revised and I am not a lawyer, so treat it as a reason to think rather than as an obligation you can self-assess.

The practical version is simple and costs nothing. Describe the ordinary day, mention the exceptional one as exceptional, and let somebody decide against that rather than against a highlight reel.

What does the photograph on a trip page have to do?

Show that specific trip, on that water, and it should be a different image from every other page on your site. This is also the tag that decides what appears when somebody shares the page.

The published advice on nominating a preview image comes as a short list of instructions. It should genuinely depict what the page covers. Skip anything generic, a masthead or badge included. Skip anything with lettering across it. Skip unusually tall or unusually wide crops. Go as sharp as the file allows.

Guide sites break the first of those constantly, because most templates ship with one image applied across everything. Send three different trips to somebody and all three arrive looking the same, squandering the only picture that determines whether the message gets opened.

Assigning a separate picture to each trip runs to roughly five minutes apiece, and the effect persists in every message thread your pages ever appear in. Who owns those pictures is a separate question, handled in the photos piece.

What does the physical demand section need to say?

The specifics somebody can measure themselves against. Not "moderately active" but how far the wade is, how deep, how slippery, how long people are standing, and whether there is anywhere to sit.

Vague descriptions fail in both directions. Somebody fit reads "moderate" and assumes it is easy; somebody less mobile reads the same word and rules themselves out of a trip they could have done comfortably.

Boat access is the version guides forget entirely. Getting into and out of a boat from a dock, a trailer or a beach is a completely different proposition for different people, and it never appears on a trip page.

Say what accommodations are possible, too. A trip that can be run from a seated position, or with the wading section skipped, is a trip somebody can book who currently assumes they cannot.

How do you state a skill floor without putting people off?

By stating it precisely, which is almost always more welcoming than leaving it vague. "No experience needed, I will teach you to cast" is a clear invitation. Silence is an ambiguity people resolve pessimistically.

Where there genuinely is a floor, name it and name why. A trip requiring an accurate sixty-foot cast in wind is a real requirement, and somebody who cannot do that will have a miserable day pretending otherwise.

The middle case is the awkward one and it deserves a sentence rather than a category. Somebody who has fished twice wants to know whether that counts, and only you can tell them.

Consider offering the honest downgrade explicitly. Pointing a beginner from your technical trip to your easier one, on the page, keeps a booking you would otherwise lose entirely and produces a better day.

What should each page say about weather?

What happens if it turns, who decides, and what happens to the money. Weather is the single largest uncertainty in the purchase and most trip pages leave it to a link somewhere else.

Separate the two things people conflate. Ordinary cancellation, where a client changes their mind, and weather cancellation, where the trip cannot safely run, have different terms and different fairness.

Three things need answering outright. Whose judgement ends the trip. What notice you give. And whether money paid gets rolled forward or refunded. Three sentences per trip page, since the answer may not be identical across them.

Also describe the exposure honestly. Whether there is shade, whether it gets cold on the water, and how likely seasickness is on that particular trip are things somebody wants before booking rather than at the dock.

Where does the price go?

On the trip page itself, next to the description, along with what changes it. A rate on a separate page is a rate somebody has to go and find, and some of them will not come back.

Name the variables rather than hiding them. Party size, duration, which water, and whether gear is included are the usual four, and stating them prevents both the surprise and the inquiry that exists only to establish the number.

Give the deposit a line of its own as well. State the sum, state when the remainder falls due, and state where a cancellation leaves it. That trio is precisely what somebody wants to know at this point on the page.

Whether to publish rates at all is a real argument with a real other side, and it is worked through properly in the pricing piece. What is not defensible is using the price as bait for an inquiry.

What can a real booking form tell you about the page?

Quite a lot, because the fields somebody asks for are the things they need to know, and each has a mirror-image question the client wants answered first.

A charter I looked at collects six pieces of information before it will take a booking: who you are, two ways to reach you, how many rods, when you want to go, and space to explain anything unusual. Their form is effectively a list of everything a guide has to settle before agreeing to a date.

Invert it and you have your page checklist. Where the form wants a party size, the page owes a capacity. Where it wants a date, the page owes a season.

Any question on the form the page left hanging is friction of your own making. The booking page piece covers the form itself.

Art of Fishing, MI

How long should a trip page be?

Long enough to answer the seven questions in the table and no longer. That is usually four hundred to seven hundred words, which is shorter than most guides expect and longer than most guides write.

The failure at the short end is a page that is really a paragraph and a price, leaving every disqualifying question unanswered so they all arrive as messages instead.

The failure at the long end is atmosphere. Three hundred words about the river at dawn is lovely writing that answers nothing, and it pushes the practical information below where anybody reads.

Lead with the answers; keep the atmosphere below for whoever wants it. Nowhere else on the site does the ordering carry this much weight. The anatomy piece sets out the wider sequence.

What should the page say about who else can come?

Whether a non-fishing companion is welcome, what it costs, and what their day looks like. This is asked constantly and answered almost nowhere.

The question comes from a specific person: somebody who wants to book but is travelling with a partner, a parent or a friend who has no interest in fishing and no intention of pretending. Right now they cannot tell whether that is possible.

Answer all three parts. Whether there is room, whether the price changes, and honestly what the day is like for somebody sitting in a boat for six hours not fishing, which for some trips is lovely and for others is a long day.

If the answer is no, say no. A trip that genuinely does not work with a passenger is better stated than discovered, and it points that booking toward whichever of your trips does.

How do you handle a trip that only runs part of the year?

Name the months on the page, in text, and say what happens outside them. A seasonal trip with no stated season generates inquiries in February that you have to decline.

Be specific rather than approximate. "Late May through September, best in June" tells somebody whether to plan; "summer" does not, and the difference is a booking made now versus an intention to check back.

Where a season shifts with conditions, say that too. Water levels, runs and temperature move dates around, and a sentence explaining that the window depends on the year is more useful than a fixed range you will be held to.

Then point at the alternative. Somebody arriving in the wrong month for this trip is somebody who might book a different one, and the page should say which, rather than leaving them at a dead end.

What do experienced guides do differently?

They update trip pages the week the season ends, and they add whatever the season taught them about who each trip suits.

Timing is the whole trick. In October you can still remember which description misled somebody, which question everybody asked, and which client turned up expecting a different day. By April all of that has smoothed over.

The who-it-suits addition is what makes a trip page improve rather than merely stay accurate. Every season teaches you something specific about the people who enjoy each trip, and writing that down is how a page starts doing the sorting for you.

Experienced operators also delete trips they no longer run rather than leaving the page up. A live page for a discontinued trip generates inquiries you have to decline, which is worse than no page, and it is one of the traces examined in the staleness piece.

What are the common mistakes?

Writing to persuade rather than to sort. Describing the best day as though it were the usual one. Hiding the price. And using the same photograph and the same description across every trip.

The same-everything mistake is the most revealing to a reader. If three trip pages differ only in the title and the price, a visitor correctly concludes that the trips do not really differ, and picks on price.

The best-day mistake is the one with consequences beyond conversion, because it sets an expectation you then have to meet on an ordinary Tuesday in a wind. Describing the ordinary day protects the day itself.

Underneath all of them sits the persuasion habit. Aim a page at everyone and it excludes no one, so the sorting gets deferred to the water, where it costs you a day. The mistakes piece catalogues the rest.

What surprises people?

That stating limits increases bookings. That the photograph is also a shareable-link decision. And that the most useful sentence on most trip pages is the one saying who the trip is not for.

The bookings effect is real and worth understanding rather than merely believing. A page that answers the disqualifying questions removes the reason to send a cautious message first, and a lot of bookings are lost in that gap between wondering and asking.

Guides resist writing the not-for sentence more than any other, and clients bring it up more than any other. It signals somebody who understands their own water and declines to sell a day to a person who would not enjoy it. The guide websites hub indexes the rest.