vamseeachanta Title Best Practices (+2)
Title Best Practices
| Good Title | Bad Title | Why |
|---|---|---|
| "How to configure SSO with Okta" | "SSO Setup" | Specific, includes the tool name customers search for |
| "Fix: Dashboard shows blank page" | "Dashboard Issue" | Includes the symptom customers experience |
| "API rate limits and quotas" | "API Information" | Includes the specific terms customers search for |
| "Error: 'Connection refused' when importing data" | "Import Problems" | Includes the exact error message |
Keyword Optimization
- Include exact error messages -- customers copy-paste error text into search
- Use customer language, not internal terminology -- "can't log in" not "authentication failure"
- Include common synonyms -- "delete/remove", "dashboard/home page", "export/download"
- Add alternate phrasings -- address the same issue from different angles in the overview
- Tag with product areas -- make sure category and tags match how customers think about the product
Opening Sentence Formula
Start every article with a sentence that restates the problem or task in plain language:
- How-to: "This guide shows you how to [accomplish X]."
- Troubleshooting: "If you're seeing [symptom], this article explains how to fix it."
- FAQ: "[Question in the customer's words]? Here's the answer."
- Known issue: "Some users are experiencing [symptom]. Here's what we know and how to work around it."