The Guide Site FAQ Page

If somebody built you an FAQ page in the last few years, there is a good chance they sold it to you on search results. That reason is now gone. Google spent three years dismantling the FAQ rich result: it narrowed the feature to government and health sites in 2023, logged the deprecation in May 2026, and removed the documentation entirely in June. I went to fetch the official page for FAQ markup while writing this and got redirected to the notice announcing its removal. So the question is no longer whether an FAQ page helps you rank. It does not. The question is whether it earns its place for the only reason left, which is that it answers questions so you do not have to answer them on the phone in July.

Is the markup worth keeping?

If it is already there, leave it. Google's own instruction when it first cut the feature was that you can drop the structured data but there is no need to proactively remove it, because unused structured data does not cause problems for search while also having no visible effect.

That is a rare piece of clarity from a platform and worth taking literally. Removing it is work with no upside. Leaving it is no work with no upside. Do not let anybody sell you either as a project.

What you should not do is add it now expecting something. The 2023 announcement was explicit that going forward FAQ rich results would only be shown for well-known, authoritative government and health websites, and that for all other sites the result would no longer be shown regularly. Three years later the documentation itself is gone.

Whether the AI answer tools that have replaced some of that search behaviour read this markup is a genuinely open question, and I could not find a primary source that answers it in either direction. Anybody telling you confidently that they do, or do not, is guessing.

Beyond The Limit, TX

So why build one at all?

Because the same eleven questions arrive by phone and message every season, and answering them once in writing is the cheapest hour you will spend all winter.

Count them for a week and the pattern is obvious. What do I bring. Do you have gear. Is my kid old enough. What if it rains. Where do we meet. Do you clean fish. Is there a bathroom. What is the deposit. Do I need a licence. What happens if I cancel. How many people fit in the boat.

That list is the page. Not questions you wish people asked, and not marketing dressed as a question, which is the failure mode of every bad FAQ page ever made.

The benefit is not only your time. Somebody who has to ask before booking is somebody who might not ask at all, and an unanswered question at eleven at night is a booking that goes to whoever answered it on their site. This is the same logic that governs what belongs on the page where they commit, covered in the booking page piece.

How should the answers be written?

Answer first, then the detail. The oldest usable research on web reading found that 79 percent of test users always scanned a new page and only 16 percent read word by word, which means the first sentence of every answer carries the whole load.

That study is from 1997 and I am citing the date deliberately, because it is very old and it is still the canonical reference on the subject. Its prescriptions have aged unusually well: meaningful sub-headings rather than clever ones, one idea per paragraph, bulleted lists, and the inverted pyramid style that starts with the conclusion.

The one-idea rule has a specific consequence for FAQ writing. Nielsen's write-up notes that users skip additional ideas if they are not caught by the first few words of a paragraph. So an answer that opens with context and reaches the answer in sentence three has, for most readers, no answer in it at all.

Write "Yes, all gear is included" and then explain. Not "We pride ourselves on a fully outfitted experience" and then, eventually, yes.

Does shorter actually measure better?

It did, by a lot, in the one study that bothered to measure it. Five versions of the same site with the same information and the same navigation produced a 58 percent improvement in measured usability for concise text at about half the word count, and 47 percent for the same words in a scannable layout.

Combining the improvements produced a 124 percent improvement over the promotional control. Those are enormous numbers from a small old study, and I would not lean on the exact figures, but the direction has never been seriously contested.

The control condition in that study is the interesting part for anybody writing about their own business. It was written in what the researchers called marketese, the boastful promotional register, and users detested it. Web users are busy and want the straight facts, and the write-up notes that credibility suffers when readers can see the site exaggerating.

An FAQ page is where that register does the most damage, because somebody arrives with a specific question and gets a paragraph about your passion for the river. Answer the question. The same discipline applies to the page above it, per the homepage piece.

What questions actually belong on the page?

The ones people ask before booking, in the order they ask them, in their words rather than yours. Everything else belongs on a trip page or nowhere.

The reliable core for a guide operation is roughly a dozen: what is included, what to bring, meeting point and time, weather policy, cancellation and deposit terms, licence requirements, minimum age or suitability for children, boat capacity, what happens to the fish, food and drink, bathroom arrangements, and tipping.

Tipping is on that list because people genuinely want to know and are embarrassed to ask. A one-line answer removes a real awkwardness and costs you nothing.

What does not belong is anything that is really a sales pitch phrased as a question. Nobody has ever typed "why should I choose you?" into anything. If you want to make that argument, make it on a page that is for making it.

What about licence questions?

Answer the shape of it and link to the state agency for the rest. Whether a client needs a licence, whether you can sell one, and whether a charter licence covers passengers varies by state and by water, and the rules get revised.

The safe pattern is to state what applies on your water, say when it was last checked, and point at the official source. Anybody reading it can then verify the current position themselves, which is what they should do anyway.

Do not paraphrase regulation from memory. This is the single most common place a guide's FAQ page goes stale, because a fee schedule or a season date changes and nothing on the page tells anybody it was written three years ago.

Put a date on that answer specifically. "Checked January 2026" is honest, useful, and protects you when something moves.

Should it be one page or spread across the site?

Both, deliberately. The three questions that decide whether somebody books belong on the trip page itself, and the long tail belongs on a single FAQ page.

Splitting on that basis follows what somebody is doing. A person reading about your half-day flats trip wants to know what is included and what to bring while they are reading about that trip, not after a detour to another page.

The FAQ page then catches everything else and works as the place you send people when they message you. A link is a faster reply than a paragraph, and it is the same answer every time.

Where guides go wrong is duplicating the entire FAQ onto every trip page, which makes each page longer, slower and repetitive. Three questions per trip page, everything else in one place. How trip pages should be built otherwise is in the trip pages piece.

Should the answers be collapsed behind clicks?

Only if the list is long. An accordion makes twenty questions scannable and makes six questions annoying, and the deciding factor is whether somebody can see the whole list without scrolling forever.

The case for collapsing is real: the point of the page is finding your question fast, and a wall of expanded answers buries the question list. With twenty items, headings alone let somebody scan the way the research says they will anyway.

The case against is that every collapsed answer costs a tap, and taps on a phone at a boat ramp are not free. Under about eight questions, just show them.

Whichever you choose, make sure the answers are actually in the page rather than loaded in on demand, so somebody using the browser's find function can locate a word in a collapsed answer. That is a technical detail worth asking about, alongside the rest of the accessibility basics in the accessibility piece.

Capt Steve Friedman, FL

Where do the questions come from?

Your own inbox, sent messages and call log, from the last two seasons. Not from a competitor's page and not from a list somebody handed you.

Spend twenty minutes scrolling back through messages and write down every question anybody asked before booking. The frequency will surprise you and so will the specificity: people ask about parking, about whether their partner can come and not fish, about whether there is shade.

Those specific ones are the valuable ones, because they are the questions no generic FAQ page anywhere contains. They are also the ones that show you actually run this operation rather than describing a category.

There is a second source sitting in plain view: your own booking form. One working charter asks six things before a booking, party size and preferred date among them, which is a compact statement of what an operator has to establish before saying yes. Every one of those fields has a mirror-image question the client wants answered first, and if the form asks for party size then your page should say how many the boat takes.

Do the same exercise at the end of every season and add anything new. A page built once and never revisited drifts away from what people are actually asking, which is the quiet failure mode of most of the content on a guide site.

What should the answers say about money?

Enough that nobody has to ask. Deposit amount, when the balance is due, what happens on a cancellation, what happens on a weather cancellation, and whether gratuity is expected.

Those five are the questions people are most reluctant to raise and most likely to walk away over. Somebody who cannot work out your cancellation terms from your site will either ask, which costs you a message, or quietly book somebody whose terms were visible.

Weather deserves separating from ordinary cancellation because the two are genuinely different and clients conflate them. Who decides the trip is off, how far in advance, and whether the deposit moves to another date or comes back. Answer all three explicitly.

The gratuity question is the one guides most often leave off out of awkwardness. Clients want to know and will ask their friends rather than you, which means the answer they act on is somebody else's guess. One plain sentence solves it. What to publish about rates more broadly is worked through in the pricing piece.

How long should the page be?

As long as your real question list and not a word longer. Twelve genuine questions answered in three sentences each is a good page. Thirty questions padded out to look thorough is a worse page than six.

The instinct to pad comes from an era when length was believed to help you rank, which is the same era that produced the markup advice this article opened by retiring. Neither belief was ever a good reason to write something a reader does not want.

Judge each answer by whether removing it would leave somebody uninformed. If the answer to a question is obvious, or if nobody has ever asked it, it is decoration.

Length also has a direct cost on a phone, where a long page is a slow page and a slow page loses people before they read anything at all. That trade is set out in the speed piece.

What do experienced guides do differently?

They write the answer once in the FAQ and then paste the link, rather than retyping it. And they add a question the moment somebody asks it twice.

The paste-the-link habit is what converts the page from a website asset into an operating tool. Somebody asks what to bring, you send the link, they get a complete answer instead of a hurried one typed from a boat ramp.

The twice rule keeps the page alive with almost no effort. Two people asking the same thing in a season is a signal, and adding it takes two minutes while it is fresh.

Experienced operators also answer the uncomfortable questions rather than avoiding them. What happens if we do not catch anything. What if the weather turns. What if I get seasick. Those get asked either way, and answering them plainly reads as confidence, while omitting them reads as evasion. That candour is the same instinct behind the bio piece.

What are the common mistakes?

Marketing dressed as questions. Answers that bury the answer. Regulation quoted from memory. And a page that has not been touched since the site launched.

The buried answer is the most common and the easiest to fix. Read your own FAQ page and check whether each answer's first sentence would satisfy somebody who read nothing else. Most will not, and rewriting the first line of each is an hour's work.

The stale page is the most damaging because it actively misleads. A cancellation policy you changed, a meeting point you moved, a boat you sold, all still described in the present tense, is worse than having no FAQ page at all.

The last one worth naming is copying somebody else's questions. A competitor's FAQ answers a competitor's clients, and half of it will not apply to your water, your boat or your rules. Take the structure if you like, never the content. This sits alongside everything else in the mistakes piece.

What surprises people?

That Google removed the FAQ documentation outright rather than quietly leaving it up. That the canonical research on scanning is from 1997. And that the best FAQ page is mostly logistics rather than persuasion.

The removal is worth understanding as a pattern rather than a one-off. How-to rich results went the same way in the same announcement, deprecated on desktop as well from September 2023. Features get built, get abused, and get retired, and any website advice pinned to a specific rich result has a shelf life.

What does not have a shelf life is answering somebody's question quickly and honestly. That was the reason to have the page before the markup existed, it is the reason now, and it will still be the reason when whatever replaces search results has come and gone. Everything else about building the thing lives on the guide websites hub.