What to read on a client's website that most writers skip entirely

The brief landed at 9am. Write a 1,500-word article about their custom packaging solutions for e-commerce brands. The website had twelve pages. By 9:47am, the writer had read the About page, skimmed Services, and started drafting.

That's how most client website research goes. And it's why most first drafts come back gutted with comments like "this doesn't sound like us" and "we don't call it that."

The pages writers skip aren't hidden. They're just boring-looking. But they contain exactly the information that separates a draft the client loves from one they have to rewrite themselves.

Why the obvious pages aren't enough when you research a client website as a writer

About pages are written for investors and job candidates. Services pages are written for Google. Neither is written the way the business actually talks to customers.

The About page gives you founding story, mission statement, maybe some team photos. Fine for context. Useless for voice. The Services page lists what they do in the broadest possible terms — "comprehensive solutions" and "tailored approaches" — because it's trying to rank for everything.

Writers who stop there end up writing in that same generic register. They use industry language instead of brand language. They describe the product in terms the client would never use with an actual customer.

The real research client website writer work happens elsewhere.

The three pages that actually tell you how the brand sounds

These aren't glamorous. They're often buried in the footer or hidden behind a hamburger menu. But they contain the specific language patterns that make a brand sound like itself.

1. The FAQ page

FAQ pages are where brands stop performing and start explaining. The questions are phrased the way customers actually ask them — not the way marketers wish they did. The answers tend to be shorter, more direct, less polished.

Look for: the exact words they use to describe their product, how they handle objections, whether they're formal or casual when someone's confused. A brand that writes "Yep, we can do that" in their FAQ is a different brand than one that writes "Yes, this service is available upon request."

Also note what questions they answer. That tells you what customers find confusing — which means that's what your article needs to make clear.

2. Case studies or project pages

Case studies force specificity. The brand can't hide behind "solutions" when they're describing an actual project for an actual client.

You'll find real product names here, not category labels. You'll see how they describe their process when they have to show it working. You'll notice whether they lead with the client's problem or their own capabilities.

Pull terminology directly from these pages. If they call their process "the intake audit," call it that in your article. If they refer to a specific product as "the Flex Series," don't call it "their flexible product line."

3. The blog archive (not just recent posts)

Skim at least ten posts, going back a year or more if you can. You're not reading for content — you're reading for patterns.

How long are their paragraphs? Do they use subheadings every 200 words or let sections run long? Do they start with anecdotes or get straight to the point? Do they ever use first person?

The blog is where tone patterns emerge. A brand might be formal on the Services page but surprisingly casual in posts. Or they might maintain a consistent academic tone everywhere. Your article should match what they actually publish, not what their homepage implies.

The footer goldmine: what the boring links reveal

Scroll down. Way down. The footer often contains pages the brand doesn't promote but maintains because customers need them.

Terms of service and privacy policy won't help your writing (unless you're writing about those topics). But look for: glossary pages, resource libraries, comparison charts, customer portals, or partner pages.

Glossary pages are pure gold for a freelance writer doing client research. They tell you exactly what the brand calls things and how they define industry terms. If the glossary says "white-label" and your draft says "private-label," you've already lost credibility.

Comparison charts show you how the brand positions against competitors. That competitive positioning shapes every claim you can make. If they position on quality, don't emphasise price. If they position on speed, don't lead with thoroughness.

What to capture while you read

Don't just read — extract. Keep a running document with these categories:

Product terminology: The exact names of products, services, features, and processes. Spell them the way the brand does, including capitalisation.

Customer language: How they describe who they serve. "E-commerce brands" is different from "online retailers" is different from "DTC companies." Use their version.

Voice signals: Three to five adjectives that describe how they sound. Conversational? Technical? Enthusiastic? Reserved? This becomes your filter for every sentence you write.

Phrases to steal: Specific constructions that feel distinctly theirs. Maybe they always say "Here's the thing" before making a key point. Maybe they never use contractions. These micro-patterns are what make a draft sound right.

When you're ready to analyse a brand's website before writing a single word, this capture process should take thirty minutes, not three hours. You're not reading comprehensively — you're scanning for patterns.

Where BrandDraft AI fits into this process

This research is exactly what BrandDraft AI automates — you give it a website URL and it reads the pages that matter, extracts the terminology and tone patterns, then generates articles that reference the brand's actual products and voice instead of generic industry language.

Whether you use the tool or do it manually, the principle is the same: the About page tells you who they say they are, but the FAQ, case studies, and blog archive tell you who they actually sound like.

The checklist version

Before your next client project, hit these pages in order:

1. FAQ — for voice and customer objections
2. Case studies — for product terminology and process language
3. Blog archive (10+ posts) — for tone patterns and structural preferences
4. Footer links — for glossaries, comparisons, and hidden resources
5. Then and only then — About and Services for context

This writer website research checklist takes an extra twenty minutes. But it's the difference between a draft that needs heavy revision and one that makes the client ask how you knew exactly how they talk.

The pages most writers skip are the pages that contain the answers. They're just not where anyone expects to find them.