The Pages Every Guide Website Needs

A page earns its place by answering one question a stranger has, and the useful way to build a guide site is to write the questions down first and let the page list fall out of them. Seven cover almost every operation. There is also an external cross-check available, which is unusual for this kind of advice: Google publishes the fact set a local business page is expected to carry, and it requires a name and a physical address, then recommends a phone number, a working URL, opening hours and a price range. That is a neutral third party effectively listing the minimum, and it lines up closely with what the two guide sites I read closely actually do. Building the pages is a different job from writing them; what the most important one has to say is in the homepage copy piece.

Why start from questions rather than from a page list?

Because a page that does not answer a question anybody actually has is decoration, and most guide sites carry two or three of them. Starting from the question also tells you what goes on the page, which a template never does.

The practical method takes an afternoon. Write down every question you have been asked on the phone in the last month, then group them. The groups are your pages, in rough order of how often they come up, and the answers are the content.

Doing it this way produces a smaller site than most guides expect and a more useful one. Seven pages that each answer something beat twenty that mostly restate the homepage in different words.

Western Mass, MA

The external cross-check: what Google expects a local business page to carry

Two required facts and five recommended ones. Google's LocalBusiness structured data documentation lists name and a physical address as required, then recommends telephone, url, opening hours, geographic coordinates and a price range.

That is a useful list precisely because it was not written for guides. It is a neutral statement of what a local business page is expected to contain, and a guide site missing several of those items is missing them for a search engine and for a human at the same time.

Two details are worth pulling out. Google specifies that the phone number should include country and area code and describes it as the primary contact method for customers, which is a reasonable prompt to stop hiding yours. And it names price range as a recommended property, described as a numerical range or currency signs, which is a quiet argument for the position taken in the piece on publishing rates.

The seasonal detail matters for this industry specifically. Opening hours can carry a start and end date for a seasonal closure, so a business that genuinely shuts for half the year can express that rather than appearing permanently open or permanently shut. How that interacts with a Google Business Profile for a half-year operation is worth checking directly with the current documentation rather than assuming.

Page one: home

Answers what you do, where, and for what fish, in the first screen. It is the only page most visitors will see, and its job is to get somebody either to a trip page or to the phone.

The failure mode is treating it as a summary of everything. A homepage that tries to be the whole site ends up being a worse version of each page it summarises. Its actual job is triage: say what you do, prove you exist, and route people onward.

Everything about the first screen, the headline, the button and what to cut is handled separately, because it is the page most worth getting right and the one guides most often fill with a paragraph about their passion for the sport.

Page two: trips and rates

Answers what can be booked and what it costs. Both guide operations I read put this in their main navigation, one calling it Rates and Terms and the other Rates and Info, which is a strong hint about where people look for it.

The page needs each trip named by shape rather than by internal category: full day, half day, walk-and-wade, float, whatever you actually run. Under each, the duration, the party size, what is included and what is not, and the number.

Keep it to the trips that represent most of your bookings, with a line saying unusual requests are quoted individually. A page listing fourteen permutations is a catalogue, and catalogues make people leave rather than choose.

Page three: a page per water

The page type most guides skip and the one with the longest payoff. Somebody planning a trip searches for a river, not for a guide service they have never heard of, so a page per named water is a page per search.

Montana Angler runs this at scale, with individual pages for nine named rivers plus spring creeks, private waters and a national park. Most guides do not need nine, they need the two or three they actually fish, each with its own address.

Fill it with the briefing you already give on the phone about that stretch: the hatches and runs by month, how you get on and off, what each season looks like, and the kind of angler it rewards or frustrates. That is knowledge you already have and almost never write down. The fuller version of this argument is in the trip pages piece.

Page four: about

Answers who exactly is getting in the boat. Name, face, credentials stated as facts, and how long you have fished that water. This is a trust page and it works on specifics, not on adjectives.

Blackcloud handles it in two lines: the captain is named, then his licence class and insurance status appear as plain statements. Nothing superlative, nothing that cannot be checked, and it settles more than a page of enthusiasm would.

The mistake is writing this page as autobiography. A stranger deciding whether to send you a deposit wants to know that you are real, qualified and experienced on that particular water. Where you grew up matters only if it explains one of those three.

Page five: photographs

Answers what a day actually looks like. Images you took, on the stretch you actually run, featuring clients who agreed to appear, each carrying alt text that says what is in the frame.

A gallery is also the page most likely to make a site slow, because it is the page nobody thinks to resize images for. Compress before uploading and let the platform lazy-load below the fold, or this page quietly undoes the work described in the piece on phone speed.

Choose for information rather than for beauty. A photograph showing the boat, the water and a client with a fish tells a prospective booker more than a perfectly composed landscape, and the criteria for that judgement are in the trip photos piece.

Page six: the FAQ

Answers everything that would otherwise be a phone call at nine at night. What to bring, what is included, what happens in bad weather, licences, physical demands, deposits and cancellations. It is the least glamorous page and often the hardest working.

Build it from your actual call log rather than from a template of generic questions. The questions you get asked repeatedly are the ones costing you time, and answering them on the page converts that time into something that works while you are asleep.

Wherever licensing comes up, add a sentence noting that fees and rules get revised and that the reader should verify the position with whichever agency issues them, ahead of the trip. That is not legal caution for its own sake; it is accurate, and it prevents somebody arriving unlicensed on your say-so. What belongs on this page in more detail is in the FAQ piece.

Page seven: contact

Answers how to reach a human. A tappable phone number, an email at your own domain, your operating hours, and the general area you fish. Google lists the phone number as the primary contact method for customers, and it belongs in your header as well as on this page.

Blackcloud states when it is reachable, an early start through to the evening, every day of the week. Small thing, real effect: a visitor reading it late knows whether a message tonight gets a reply before morning, and the window itself is a promise that somebody is minding the phone.

Using an address on a domain you control, instead of a free mailbox, matters for reasons beyond how it reads, set out in the business email piece.

What about the pages you can add later?

Fishing reports, a blog, testimonials and small local pages. All useful, none load-bearing. Add them when the seven are genuinely good rather than instead of finishing them.

Reports are the strongest of the optional four, because they demonstrate current knowledge of the water in a way nothing else does, and they give somebody a reason to come back before booking. They are also a commitment, and a reports page last updated eighteen months ago actively damages the impression it was meant to create.

The small local page is the most underrated of the four. One of the sites observed devotes a top-level menu slot to boat ramps, which sells nothing at all and is precisely why it lands. Most guides are sitting on three or four pages like that.

Oahu Fly Fishing, HI

Which pages do guides build that nobody needs?

A services page that restates the trips page. A separate gallery for every trip type. A blog with three posts from four years ago. And a testimonials page that no visitor believes and no search engine rewards.

The duplicate-services page is the most common and it does active harm, because two pages competing to answer the same question split whatever attention either would have got and confuse anybody trying to navigate.

The stale blog is the second. Three posts from 2022 says less than no blog at all, because it demonstrates something started and abandoned. If you are not going to keep it current, remove it and put the effort into a water page that stays true.

How many pages should a one-boat operation have?

Seven to ten. The seven core pages plus a page for each water you genuinely fish. That is enough to answer every question a booker has and small enough that you can keep all of it accurate.

Accuracy is the real constraint, and it is why bigger is not better. Every page is something that has to stay true as your rates, seasons and boat change, and a guide with twenty pages has twenty things to update and will update six.

Build in order of the questions people ask most. Home, trips and rates, and contact first, because those three answer the majority. Waters next, because they bring people in. Then about, photos and FAQ, which convert the people already there.

In what order should you build them?

Home, trips and rates, contact. Those three answer the majority of what anyone arrives wanting to know, and a site consisting of only those three is already useful. Waters next, because they are the only pages that reach people who have never heard of you. Then about, photos and the FAQ, which convert people already on the site.

The ordering follows a simple rule: build what serves the visitor you already have before building what fetches new ones. A guide who writes six water pages while their contact page still hides the phone number has spent effort attracting people to a site that then loses them.

It also front-loads the quick wins. The first three pages can be written in a weekend from things you already say every week, and they are the ones you can judge honestly by opening them on a phone and asking whether a stranger could act.

Resist building all seven half-finished in parallel. A finished page that answers its question beats three drafts, and a site of three good pages is genuinely better than a site of seven placeholder ones. The remaining four can arrive across an off season.

How do you know a page is actually finished?

When somebody who does not fish can read it and answer the question it exists to answer, without asking you anything. That is a harder test than it sounds and it is the only one that matters.

Run it literally. Hand your phone to a friend or a family member outside the sport, point them at one page, and ask them the question that page is supposed to answer. What does this business do. What would a day cost. How would you get hold of them. Their hesitation tells you exactly where the page fails.

The reason a non-angler is the right tester is that you cannot unsee your own context. You know what your water is called, what a half day involves and what is included, so every gap reads as obvious to you and invisible on the page. A stranger has none of that, which is the same position as your actual buyer.

Two failure patterns show up almost every time. The page answers a slightly different question from the one it was built for, usually a more flattering one. Or it answers correctly but so far down that nobody scrolling would find it.

Fix those before adding anything. A site of seven pages that each pass this test is doing more work than any number of pages that do not, and the test costs nothing but a slightly awkward five minutes.

What do experienced guides do differently?

They build from their own call log rather than from a page template, they finish seven pages properly before adding an eighth, and they review the whole set once a year for things that have quietly stopped being true.

The annual accuracy pass is the habit nobody has and everybody needs. Rates change, seasons shift, a boat gets sold, a phone number changes. A site is a set of claims about your business, and claims rot without anybody noticing.

They also resist the urge to add pages as a response to a quiet season. A quiet phone is rarely fixed by a new page; it is usually fixed by making an existing one answer its question properly, which is a smaller and less satisfying job. Working out what is actually capping the season is the subject of the plateau diagnosis.

What are the common mistakes?

Building pages before deciding what each answers. Duplicating the trips page as a services page. Skipping the water pages, which are the ones that bring strangers in. And leaving a contact page that offers only a form.

The form-only contact page deserves singling out. Bookings in this trade still overwhelmingly arrive by voice, and a contact page offering nothing but a form reads as a preference not to be rung. Google's own guidance treats the telephone number as the primary contact method for a local business, which is a reasonable prompt.

The skipped water pages are the biggest missed opportunity in this whole list, because they are the only pages on the site that reach people who have never heard of you.

What surprises people?

That Google effectively publishes a minimum fact set, and that name and address are the only required ones. That price range appears as a recommended property. And that a good guide site is smaller than most guides assume, usually under ten pages.

The small-site point runs against a lot of instinct. More pages feels like more presence, and it mostly means more surface area to keep accurate and more ways to answer the same question inconsistently.

The structured-data list is worth reading in full for a different reason: it is one of the few places you can see, from a neutral source, what facts a business page is expected to state. Specifications and guidance get revised, so read the current version rather than relying on this summary. Everything else about building the site sits under guide websites.