Homepage Copy for Guide Sites

Nobody reads your homepage. In the study everybody quotes on this, 79 percent of test users scanned every new page they landed on and only 16 percent read word by word. The same research measured what actually fixed it, and the answer was unglamorous: cutting the word count roughly in half improved measured usability by 58 percent, making the layout scannable improved it by 47 percent, and writing plainly instead of promotionally improved it by 27 percent. All three together came to 124 percent. That study is from 1997, which is worth saying out loud rather than passing off as fresh, and its conclusions are echoed in accessibility guidance that was updated in 2024. The practical upshot has not changed: a homepage is a scanning problem, not a persuasion problem, and it works when it answers a stranger's questions in the order they ask them. What belongs on the rest of the site is a separate inventory.

Does anyone actually read a homepage?

Almost nobody, in the sense you mean. Nielsen Norman Group found that 79 percent of their test users always scanned any new page they came across, while only 16 percent read word by word. People arrive looking for a specific answer and hunt for it.

Read the finding carefully, because the useful part is not the headline number. It is the behaviour underneath: visitors are picking out individual words and sentences, not consuming your paragraphs in order. That means the words carrying meaning have to be the ones a scanning eye lands on, which is headlines, the first few words of each paragraph, and link text.

Worth being straight about the source. That study was published on 30 September 1997, and Nielsen Norman Group have since published newer work on how people read online. It gets quoted constantly without the date attached, which is a small dishonesty worth not repeating. Treat it as a durable finding about human attention rather than a fresh measurement, and check the newer material if you want the current picture.

Tyee Charters, WA

What does the research say fixes it?

Three changes, measured separately against a promotional-writing control. Concise text, about half the word count, was 58 percent better on measured usability. A scannable layout of the same words was 47 percent better. Objective rather than boastful language was 27 percent better. Combined, 124 percent.

The ordering is the interesting part and it runs against instinct. The biggest single win was not better words, prettier design or stronger persuasion. It was fewer words. Half the word count, same information, dramatically easier to use.

Second was layout that supports scanning: the same text broken into a list rather than a paragraph. Nothing was added and nothing was rewritten. It was simply arranged so that a scanning eye could find the parts.

Third, and the one guides resist most, was dropping the promotional voice. Writing "Nebraska has several attractions" instead of "Nebraska is filled with internationally recognized attractions" measurably improved not just what users preferred but how well they performed on tasks: time, errors, memory and understanding of the site structure all got better.

Why does promotional writing actively cost you?

Because the reader has to spend effort filtering it. The researchers' explanation was that promotional language imposes a cognitive burden: somebody reading a boastful claim reacts by thinking "no it is not," and that reaction slows them down and distracts them from the thing they came to do.

That mechanism explains why phrases like "premier guide service" and "unforgettable experiences on legendary water" do not just fail to persuade. They cost you attention you needed for the sentence that names your river. The reader is not neutral about a claim they cannot verify; they are actively taxed by it.

The same research recorded that users detested that promotional style, and that credibility suffers when a site clearly exaggerates. For a guide business asking a stranger to wire a deposit, credibility is the entire conversion, so an exaggeration that reads as harmless marketing is doing real damage.

The replacement is not modesty, it is specificity. "Wade trips for brown trout on the upper Madison, March through October, two anglers per guide" outperforms any adjective, because it is checkable and it answers something. The federal plain language guidelines make the same argument for government writing, and the reasoning transfers exactly: write for the person reading, not for the person writing.

The headline: what must it name?

The water, the fish and the reader, in one line a stranger can parse in under two seconds. If your headline would still make sense on a competitor's site four states away, it is not a headline, it is a slogan.

Run that test first, because it eliminates most of what guides put there. "Your adventure awaits" fits anybody. "Fly fishing done right" fits anybody. "Guided wade and float trips for trout on the Missouri below Holter" fits exactly one operation and tells a stranger whether to keep reading.

Naming the reader matters as much as naming the water. A beginner and a seasoned angler are looking for opposite signals, and a headline that quietly picks one saves everybody time. Being explicit that you run beginner-friendly half days, or that you run technical dry-fly water and expect a competent caster, filters the calls you do not want and wins the ones you do.

The subhead: the one sentence under it

One sentence, and its job is to answer the question the headline just raised. If the headline names the water and the fish, the subhead names the season, the boat or the format, and who it suits. Not a paragraph, and not a mission statement.

The discipline that works is to write it as though finishing the visitor's own sentence. They have just read the headline and thought "okay, but," and whatever follows their "but" is the subhead. Usually it is when, how long, how much, or is this for me.

Keep it under about twenty-five words. The research on cutting word count applies most sharply here, because this is the sentence with the highest chance of being read at all, and every clause you add lowers the odds of the whole thing landing.

The first button: what should it say?

Say what happens next, in the visitor's words. "Check available dates" or "See trips and rates" beat "Learn more" and "Submit," and accessibility guidance explicitly names ambiguous link text like "click here" and "read more" as the thing to avoid.

The W3C's Web Accessibility Initiative puts it plainly: write link text so that it describes the content of the link target, and avoid ambiguous text such as click here or read more. That is written for screen reader users, who hear links out of context, and it happens to be the same advice that makes a button work for everyone else.

Place one primary button high and repeat it further down. Two competing buttons of equal weight at the top is the common error; the visitor now has a decision to make before they have any information, and the usual outcome is neither. Where that button should land, and what the page behind it must do, is worked through in booking page best practices.

Proof: what belongs above the fold?

One or two specific, checkable things. A named review count from a platform people trust, the years you have run this water, a licence or certification if it applies. Not a wall of first-name testimonials, and not badges nobody recognises.

Specificity is what separates proof from decoration. "Trusted by anglers everywhere" is decoration. "Guiding the Green since 2009" is proof, because it is a fact somebody could check and would be embarrassing to invent.

The 1997 research also noted that credibility rises with good writing and with outbound links to other sites, on the reasoning that a site willing to point elsewhere is not hiding. For a guide that translates neatly: linking to the state agency's regulations page, or to the fishing report you actually use, costs you nothing and signals that you are a real operator rather than a landing page.

The trip list: prices or not?

Put the trips on the homepage with enough detail to self-select, and make the price question a deliberate decision rather than an accident. Whichever way you go, the visitor should not have to guess whether they can afford you.

Three to five trips is usually right for the homepage: format, duration, party size, and either the rate or a clearly signposted route to it. More than that and you have built a catalogue, which belongs deeper in the site on its own pages.

The prices decision has real arguments on both sides and it deserves its own treatment rather than a throwaway line here, which is why it is handled in the piece on publishing your rates. What is not defensible is the accidental middle, where a rate is technically somewhere on the site but nobody can find it.

The photographs, and their alt text

Your own photographs, of your own water, with real clients where you have permission. And every one needs alt text describing what it shows, because accessibility guidance asks for alternative text that provides the information or function of the image.

Stock photography is the fastest way to signal that you are not a real operation, and anglers spot it immediately because they know what that water looks like. A slightly imperfect phone photo of your actual river outperforms a beautiful photograph of somebody else's.

Alt text is the part everybody skips. W3C's guidance is that for every image you write alternative text conveying the information or function, while purely decorative images need none. "Angler netting a brown trout on the lower Madison in October" is useful; "IMG_4021" is not; and a decorative texture behind a heading needs nothing at all. What makes a trip photograph worth using in the first place is covered in the piece on photos that book clients.

Solitude River Trips, ID

The page title, which is not your headline

The title is the text in the browser tab and the search result, and it follows a different rule. W3C's guidance is to give each page a short title describing its content and distinguishing it from other pages, putting the unique and most relevant information first, ahead of the organisation name.

That ordering is the bit guides get backwards. "Smith Guide Service | Home" leads with the thing nobody searched for. "Madison River fly fishing guide, Ennis MT | Smith Guide Service" leads with the words somebody typed, and the business name still gets its place.

It also has to be unique per page. A site where every tab reads the same is a site where search results and browser history are useless, which is a small quiet friction on every return visit.

The footer: what people scroll past everything to find

A phone number that is a real link on a phone, an email at your own domain, the water you run, and the season. The footer is where people go when they have decided and want to act, so it should never be the place your contact details are missing.

Make the phone number tappable. A number rendered as text or, worse, inside an image, forces somebody to memorise it and switch apps, and a meaningful share of them will not. The email should be at your own domain rather than a free address, for reasons that go beyond appearances and are set out in the piece on business email.

What should you cut first?

Half of it, starting with anything that describes feelings rather than facts. The single largest measured improvement in that research came from concision alone, at 58 percent, and it required adding nothing.

Go through the page and mark every sentence that would survive being moved to a competitor's site. Those are the sentences doing no work. In most guide homepages that is the opening paragraph about passion for the sport, the section about commitment to an unforgettable experience, and roughly half the adjectives.

Then check what is left against the question list at the top of this page. If a block does not answer one of those questions, it is either decoration or it belongs on a deeper page, and the deeper pages are where detail earns its place, particularly the individual trip pages.

What do experienced guides do differently?

They write the page as answers to the questions they get on the phone. They name the water in the first line. And they read it aloud on a phone screen before publishing, which catches almost everything.

The phone-questions habit is the strongest one, because those questions are free research you already have. The things people ask before booking, in the order they ask them, is the outline of a working homepage. Most guides have heard the same six questions several hundred times and never thought to answer them on the page.

Reading it aloud on a phone catches the rest. Marketing language is much more obvious in your own voice than on a screen, and the phone view is where most of your visitors are anyway. Anything you would be embarrassed to say to a client's face should not be on the page, and a slow-loading hero image is instantly obvious in a way it never is on a desktop, which is the subject of the piece on phone speed.

What are the common mistakes?

A headline that fits any guide anywhere. A hero image with words over it that nobody can read on a phone. Two competing buttons above the fold. And an opening paragraph about your passion for the sport instead of what you do and where.

The passion paragraph is nearly universal and it is worth understanding why it fails. It is not that the passion is fake. It is that everyone writes it, so it distinguishes nothing, and it occupies the position on the page where a scanning reader is most likely to be looking. Correct information in that spot converts; a shared sentiment does not.

The competing buttons mistake is quieter. "Book now" next to "Contact us" next to "View trips" gives the visitor a choice they lack the information to make. Pick the one action you want and make the others secondary. The wider catalogue of what goes wrong is in the ten most common guide website mistakes.

What surprises people?

That cutting words was the single biggest measured improvement. That boastful copy makes a site measurably harder to use rather than merely annoying. That the accessibility rule about link text is also the conversion rule. And that the study everybody cites is from 1997.

The overlap between accessibility guidance and plain good copy is the useful surprise. Descriptive link text, meaningful headings, short sentences, real alt text: all of it is written for people using assistive technology, and all of it independently makes the page work better for the angler scrolling on a boat ramp with one bar of signal.

The date surprise matters because of how the finding is usually deployed. A number quoted for thirty years without its date is the kind of thing worth checking before you repeat it, on your own site as much as anywhere else. Research and guidance both get revised, so look at the current versions before you treat any of this as settled.

How do you test it in ten minutes?

Open the page on a phone, and without scrolling, answer three questions: what does this business do, where, and what do I press. If a stranger cannot answer all three from what is visible, the page has not started working yet.

Then hand the phone to somebody who does not fish and ask them the same three questions. They will tell you in about fifteen seconds what six months of tinkering would not, because they have none of the context you cannot unsee.

Finally, count the words above the first button. If it is more than about fifty, the research says cutting is your highest-return edit, and it costs nothing but nerve. The rest of the material on building a site that books trips sits under the guide websites topic.