Structure

Navigation labels are interface copy, not branding

Navigation is a utility layer

I've audited enough small-site navigation to know the pattern: someone decides "Services" is boring, so it becomes "Solutions" or "What We Do" or—heaven help us—"Our Magic." Then analytics show that page gets half the traffic it should, and everyone blames the design.

The problem isn't the design. The problem is treating navigation labels like branding opportunities instead of what they actually are: interface copy with a single job—tell people where they're going before they click.

Navigation labels are wayfinding. They're road signs, not billboards. When you make someone guess what "Offerings" means versus "Services" versus "Products," you've added cognitive load to a decision that should be automatic. Every millisecond of hesitation is friction you chose to install.

The test most nav fails

Can a first-time visitor predict what they'll find before clicking? Not approximately—precisely. If your "Insights" link goes to a blog, case studies, whitepapers, and a newsletter signup, you've failed. That's four different content types under one vague umbrella label.

I don't care if "Insights" polls well in your brand workshop. A label that encompasses everything explains nothing. Split it. "Case Studies" and "Blog" are boring precisely because they're unambiguous. Boring is the point.

The same disease infects mega-menus. I've seen navigation schemes where "Resources" drops down to reveal twelve links spanning everything from documentation to event calendars. That's not architecture—that's abdication. You're making users parse a junk drawer instead of doing the information architecture work yourself. [Taxonomy before taxonomy](/posts/taxonomy-before-taxonomy-name-your-buckets-once) applies to navigation hierarchies just as much as content categories.

Stop optimizing for cleverness

Your navigation is not the place to showcase your copywriter's wit. It's infrastructure. If you wouldn't replace "Emergency Exit" signs with "Swift Egress Portal," don't replace "Contact" with "Let's Connect."

Here's what actually works: conventional labels, predictable hierarchy, and ruthless specificity. "About" goes to about content. "Services" lists services. "Blog" is blog posts. If you have products and services, you have two top-level links—not one link called "What We Offer" that makes people guess.

The moment you see analytics showing people using site search to find content that's theoretically in your navigation, you've proven your labels are failing. They're clicking around, not finding it, and resorting to search because your clever label didn't communicate.

Build it like you'd explain it

Test by explanation: if you had to tell someone over the phone where to find something, what would you say? "Click Services" is clear. "Click Solutions—well, it's kind of like services but we call them solutions" is a design smell.

This extends to URL structure too. If your navigation says "Insights" but the URL is `/blog`, you've introduced a second point of confusion. Label and destination should match. Consistency across navigation text, page titles, and URLs isn't pedantry—it's reducing the number of synonyms someone has to mentally map.

When to break the rules

Almost never. But fine: if you're in a specialized domain where your audience uses specific jargon, use that jargon. A medical site can say "Providers" instead of "Doctors" if that's the industry term. A developer tool can use "Docs" instead of "Documentation."

The principle holds: use the label your specific audience expects, not the label you wish they expected. If you're serving a general audience, default to the most common, most boring, most obvious label that exists. [Page titles for people who don't read your nav](/posts/page-titles-for-people-who-dont-read-your-nav) applies here—many users skip navigation entirely and rely on search results or direct links.

The fix is usually obvious

Audit your navigation right now. For each label, ask: would a stranger know exactly what's behind this link? If the answer involves explaining, clarifying, or contextualizing, the label is wrong.

Replace vague labels with specific ones. Split overloaded categories. Match labels to URLs to page titles. Make your navigation so obvious it's invisible. That's not a failure of creativity—it's navigation working exactly as it should.

← All posts