Trip Photos That Book Clients

Three things decide whether the photos on your site help you, and only one of them is about photography. There is what the photos show, which is where every article on this subject stops. There is who owns them, which almost nobody raises and which has a clear answer in copyright law: the person who pressed the button owns the picture, and that person is frequently your client. And there is what a wall of trophy shots implicitly promises a stranger about their own day, which is a question the Federal Trade Commission has published guidance on. Take those in order. The composition advice is the least valuable part.

Who actually owns the photo?

The person who took it. The US Copyright Office puts it plainly: everyone is a copyright owner, and once you create an original work and fix it, like taking a photograph, you are the author and the owner. Copyright attaches the moment the shutter closes.

Which means the photo your client took of their own fish, on their own phone, and texted to you afterwards, belongs to them. Not to you, and not to your website, however friendly the exchange was.

There are two routes to owning something you did not shoot. Work made for hire covers works created by an employee within the scope of employment, and applies to certain independent contractor relationships for certain commissioned works. And ownership can come from contracts, including assignments.

Neither of those happens by accident. If you hire a photographer for a day, they own what they shot unless your agreement says otherwise, and a verbal understanding is worth exactly what it sounds like when a relationship goes bad. This is legal territory rather than website advice, so treat this section as a prompt to sort your paperwork rather than as counsel, and talk to a lawyer about anything load-bearing.

Angler, TX

How do you actually get usable photos then?

Ask, in writing, at a moment when the answer is easy. The end of a good day is the easiest moment there will ever be, and a one-line text asking permission to use a photo on your site takes ten seconds and creates a record.

Build it into the follow-up you already send. If you are sending a thank-you message anyway, adding a sentence asking whether you can use the day's photos costs nothing and gets you a yes almost every time from somebody who just had a good time.

The stronger version is to make the ask before the trip, in the confirmation. That way nobody is surprised, and the person who would rather not appear online can say so quietly instead of having to object afterwards.

Keep the replies. A folder of screenshots costs nothing and settles a question you will otherwise be reconstructing from memory in three years. That folder belongs alongside the rest of the operating paperwork described in the ownership piece.

What does a wall of trophy shots promise?

More than you mean it to. A stranger scrolling twenty photographs of exceptional fish forms a view of what a day with you produces, and that view becomes the standard they measure their own trip against.

There is a formal version of this problem worth knowing about. The FTC's endorsement guidance addresses advertising that features people who achieved exceptional or above-average results, and it is blunt about the usual workaround: endorsements claiming specific results are usually interpreted to mean the endorser's experience reflects what others can also expect, and statements like "results not typical" or "individual results may vary" will not change that interpretation.

The guidance gives advertisers two choices instead: have adequate proof the results shown are typical, or clearly and conspicuously disclose the generally expected performance in the circumstances shown.

Be careful about how far that stretches. The guides address endorsements, meaning advertising messages consumers are likely to believe reflect somebody's opinions other than the advertiser's, so a client's testimonial with their photograph sits much closer to the line than a photo you took yourself. The FTC itself notes its staff guidance cannot be definitive because context matters. Read this as a reason to think about what your gallery implies, and ask a lawyer if you are relying on it.

So what should the gallery actually contain?

A day, not a highlight reel. Five categories: people's faces, the water in ordinary light, the boat, the in-between moments, and you doing your job.

Faces first, because a stranger deciding whether to book is trying to work out whether they will enjoy themselves, and a fish cannot answer that. A photograph of somebody grinning with a modest fish sells better than a bigger fish held by a torso, and it does the same job as the plain-spoken bio described in the bio piece: it makes you a person rather than a service.

The water in ordinary light matters because it sets an honest expectation about where they are going. Every gallery has the golden-hour frame. Very few have the flat grey morning that is what most days actually look like, and including one is the difference between a brochure and a description.

The in-between moments are the ones guides delete. Coffee at the ramp, somebody tying on, the dog, lunch, the drive out. Those are the photos that make a day feel like a day rather than a transaction, and they are the ones that do the most work on a homepage. What goes at the top of that page is covered in the homepage piece.

How many photos is enough?

Fewer than you think, chosen harder. Twelve photographs that each show something different beat sixty that show the same thing sixty times, and the sixty cost you real page weight.

The test for whether a photo earns its place is whether removing it would take information away. Two photographs of different people holding similar fish in similar light are one photograph twice, and the second one is costing you load time in exchange for nothing.

Guides accumulate galleries the way garages accumulate rods, one season at a time and nothing ever leaves. Once a year, go through and delete anything that is not carrying its own weight.

The exception is a trip page, where more is genuinely better because somebody reading that page has already decided they are interested and wants to see specifically that trip. Structuring those pages separately is covered in the trip pages piece.

What does photo weight cost you?

Speed, and speed costs bookings. Google's own image guidance says outright that images are often the largest contributor to overall page size, which can make pages slow and expensive to load.

That word expensive is doing real work. Somebody loading your gallery at a ramp on cellular is spending their data on your photographs, and a page that takes fifteen seconds gets abandoned before it finishes.

Google's image documentation is where all of that is set out, and it is worth checking the current version before you rebuild a gallery, because the format list and the guidance around it get revised. The fix is not fewer photos alone; it is correctly sized ones. A phone camera produces files far bigger than any web page needs, and uploading them untouched is the single most common cause of a slow guide site.

Google's guidance also asks for both things at once: high-quality photos appeal to users more than blurry ones, sharp images are more appealing in a result thumbnail and can increase the likelihood of getting traffic, and yet images are the main contributor to page size. Sharp and small is the target, and modern formats get you both. The full speed argument is in the speed piece.

Which file formats should you use?

Any of the ones Google supports, which for images referenced in an image element are BMP, GIF, JPEG, PNG, WebP, SVG and AVIF. In practice you want JPEG for photographs, or WebP and AVIF if your site can serve them.

The modern formats exist precisely to solve the tension in the previous section: they hold detail at much smaller file sizes than a JPEG of the same visual quality. Most site builders can produce them automatically now, which means this is usually a setting rather than a project.

One small detail from the same guidance that costs nothing to follow: make the file extension match the actual file type. A file named as a JPEG that is really something else is an avoidable problem.

Whether that setting exists at all depends on what your site is built on, which is one more thing to weigh in the platform comparison. Whatever format you land on, serve different sizes to different screens rather than sending a desktop-sized image to a phone. That is what responsive image markup is for, and it is the difference between a gallery that works on cellular and one that does not.

Are your photos even findable?

Only if they are real images in the markup. Google's guidance is explicit that it does not index CSS images, so a photograph placed as a background rather than as an image element may as well not exist as far as image search is concerned.

This catches people out because CSS backgrounds look identical on screen. The gallery renders, the photos appear, and the entire set is invisible to the one search surface where fishing photographs actually get browsed.

Check yours the lazy way: right-click a photo on your own site and see whether the menu offers to open or save the image. If it does not, you are probably looking at a background.

The same guidance suggests an image sitemap for photos that might not otherwise be discovered, and notes that image sitemaps may include URLs on other domains, which matters if your photos live on a separate host. That is a technical job, and the point of raising it here is that it is worth asking whoever built your site whether it is done. More site mechanics sit in the guide websites collection.

Boca on the Fly, FL

What controls the photo that shows up when somebody shares your page?

A tag you can set, and if you do not set it the choice is made for you. Google describes its image preview selection as completely automated, and says you can influence it by specifying a preferred image through schema markup or the og:image meta tag.

Its advice on which image to nominate is specific and worth following exactly. Choose an image that is relevant and representative of the page. Avoid a generic image such as your site logo, or an image with text on it. Avoid extreme aspect ratios, meaning anything unusually narrow or wide. Use high resolution where you can.

The logo instruction is the one guides most often violate, because a logo is the default in a lot of website templates. It means every page you share looks the same, which wastes the one image that decides whether somebody clicks.

Set a different preferred image per page, matched to what that page is about. A trip page shares its own trip's photograph. It is a five-minute job per page and it changes how every link to your site looks in every message thread it ever appears in.

What about photos of children, and people who did not agree to be there?

Ask the parent, every time, and treat a no as final without making it awkward. This is the one area where the cost of getting it wrong is not measured in bookings.

A family trip produces the best photographs you will take all season and the ones you should be most careful with. Some parents are delighted to see their kid on a guide's website and some are firmly not, and you cannot tell which from the day itself.

The clean approach is to ask the parent directly, name where the photo would appear, and then let it drop. If the answer is yes, note it. If it is no or a hesitation, that is a no.

The same courtesy applies to adults who happen to be in frame. The client whose face is in the background of your best boat shot did not necessarily sign up to appear in your marketing, and the right of publicity, which governs the commercial use of somebody's likeness, varies from state to state. Rules here differ by jurisdiction and get revised, so check the current position for your own state, and ask an attorney rather than guessing if you are unsure.

Where should the photos actually go on the site?

Distributed through the pages that need them, not piled into one gallery page. A dedicated gallery is the page nobody visits and the page that is hardest to keep current.

The reason is what a visitor is doing at each point. Somebody on a trip page is deciding whether that specific day appeals, and one honest photograph on that page does more than forty on a separate one they will never open.

Put two or three on the homepage, a set on each trip page matched to that trip, one on the about page that shows your face clearly, and one on the booking page if it does not slow it down, which is a real constraint given how little should be on that page at all per the booking page piece. That distribution puts a photograph wherever somebody is making a decision.

If you keep a gallery page as well, treat it as an archive rather than a shop window, and accept that it will get less traffic than any of the pages above. Where each of those pages sits in the overall structure is set out in the page list.

What do experienced guides do differently?

They shoot with the website in mind rather than shooting and then hunting for something usable. And they take one photograph a day that has no fish in it.

Shooting with intent mostly means remembering to turn around. Guides take a thousand photographs pointed at a client holding a fish and none pointed at the boat, the river, the ramp at first light, or the client's face while they are casting. The second set is the one the website needs and the one that never gets taken.

The no-fish habit is the single most useful thing in this article. One frame a day, of anything that is not a fish, and by the end of a season you have a library nobody else has, because everybody else's camera roll is all fish.

Experienced operators also keep the photographs organized by trip and by water rather than by date, because that is how you will need them later. A folder per trip type takes no more effort than one big folder and saves an afternoon every time you update the site during the offseason, which is where this job naturally lives per the offseason piece.

What are the common mistakes?

Using photos you do not own. Uploading phone-sized files untouched. Showing only exceptional days. And letting the same twelve photos sit there for six years.

The ownership mistake is the one with teeth, and it usually happens innocently, with a photo pulled from a client's social post or a photographer's proof gallery. Copyright does not care that you were friendly about it.

The stale-gallery mistake is quieter but more common. Photographs date themselves through clothing, gear and boats, and a returning client can tell instantly that nothing has changed since they were last there. Worse, a gallery of a boat you sold in 2021 is describing a business that no longer exists.

The last one worth naming is stock photography. A stranger cannot always tell, but a fisherman can, immediately, and the day somebody recognizes a stock photo on your site is the day they stop believing anything else on it. The wider list of ways guide sites undermine themselves is in the mistakes piece.

What surprises people?

That the client owns the photo they sent you. That "results not typical" does not do what people think it does. And that a photo shown as a CSS background is invisible to image search.

The disclaimer point is the most useful correction here, because that phrase is treated as a magic word across small-business marketing. The FTC's own guidance says it does not change how a claim is interpreted, and offers two real options instead: proof that the results are typical, or a clear disclosure of what people generally achieve.

For a guide, the honest and much easier version of that is simply to show a range. A gallery that includes ordinary days alongside exceptional ones is more credible, sets a client up to be pleased rather than disappointed, and sidesteps the whole question. It is also just a truer description of your work, which is the point of having photographs at all.