Page titles for people who don't read your nav
Most people arrive without context
I used to write page titles assuming people would see the navigation, read the breadcrumbs, or at least know what site they were on. Then I looked at the analytics.
Half the traffic came from search. Another chunk from direct links. Some from bookmarks saved months ago. Almost nobody was clicking through from the homepage like I imagined.
Every page title needs to work as if it's the first thing someone sees. Because often, it is.
The standalone test
Open your page in a new tab. Cover everything except the title (the H1, not the meta title — though they should usually match).
Can someone tell what this page is about? Can they tell what kind of page it is — a guide, a reference, a product page, a blog post?
If the title only makes sense after reading the intro paragraph, it's not doing its job.
**Instead of:** "Getting Started"
**Try:** "Getting Started with Email Templates"
**Instead of:** "Configuration"
**Try:** "How to Configure SMTP Settings"
**Instead of:** "Best Practices"
**Try:** "Best Practices for Product Photography"
The pattern is simple: include enough context that the title works alone.
When specificity feels redundant
I know the worry. If your nav already says "Documentation > API > Authentication" and your breadcrumb shows the same path, isn't "Authentication" enough for the title?
Maybe — if everyone arrives through that path. But they don't.
Someone searches "API authentication" and lands directly on your page. Someone bookmarks it and comes back three weeks later. Someone shares the link in Slack without any explanation.
In all those cases, "Authentication" by itself is too vague. "API Authentication" is clearer. "How API Authentication Works" is clearest.
The navigation can be minimal because it has hierarchy. The page title can't rely on that hierarchy.
Titles that show the page type
I'm learning that the best titles often signal what kind of page this is:
- Guides use "How to..." or "[Noun]: A Practical Guide"
- References use plain nouns: "CSS Grid Properties" or "Error Codes"
- Comparisons use "vs" or "compared": "Markdown vs Rich Text Editors"
- Troubleshooting uses "Why..." or "Fixing...": "Why Images Aren't Loading"
This isn't a rigid formula. It's about setting expectations fast. Someone should know immediately whether they're about to read a tutorial, scan a reference, or troubleshoot a problem.
The search results preview
Before you publish, search for the topic your page covers. Look at the titles in the results.
Your title will sit in that list. Does it stand out? Does it clearly differentiate from similar pages? Does it tell someone why they should click yours instead of the one above it?
I'm not saying to optimize for clicks over clarity. I'm saying clarity usually wins clicks anyway.
If your title is "Features" and the page next to yours is "Features You'll Actually Use: A Complete Guide," guess which one sounds more helpful.
When short titles still work
Sometimes a short, simple title is exactly right. "Pricing" works for a pricing page. "About" works for an about page. "Blog" works for a blog index.
The difference is that these pages are **expected**. People know what "Pricing" means. They don't need extra context.
But most pages aren't like that. Most pages need to explain themselves because nobody's expecting them.
If you're not sure whether your page is in the "expected" category, assume it's not. Add the context. You can always trim later if it feels redundant.
Start with the page title, not the nav label
I used to write the navigation first and then figure out page titles. That was backwards.
Now I write the page title first — the full, standalone version. Then I figure out what the nav label should be. Often it's shorter, because the nav has hierarchy to lean on.
But starting with the full title forces me to think about clarity first, brevity second. That order matters.
A page title is the first thing most people see. Make sure it tells them where they are.