Philippines staffing blog ·

Write knowledge article titles in the customer's search language

A title built from internal product names is hard to find, so the desk should start from real search queries and test the title before publishing.

Write knowledge article titles in the customer's search language help desk operations illustration

Direct answer

Operational guidance

Start from the search log, not the product name

The best title uses the words a customer types, not the words the product team uses in a release note. Pull a month of search queries that ended without a click or with a quick exit. Those queries show the vocabulary gap between the help center and the people it serves. Group the queries by intent so one article can answer several phrasings without repeating the same page.

Separate a query that names a feature from one that describes a problem. A feature name may change, while a description such as cannot sign in stays stable across releases. Write the title around the stable description and put the current feature name in the body. That choice keeps the article findable after a rebrand or a menu change. Keep a short list of stable problem phrases beside the release calendar.

Use the words customers type in the title

Put the search phrase near the front of the title and keep the sentence short. A title that reads reset a forgotten password is easier to match than an internal label such as credential recovery workflow. Use the customer's verb and noun, even when the product documentation uses different terms. The title is a signpost, not a place to demonstrate terminology.

Include one common synonym only when it does not make the title awkward. Search engines and help-center search both match words, and a second term can bridge two audiences. Do not stack five variations into one title, because the result reads like a keyword list and helps nobody. Choose the phrase that appears most often in the queries you reviewed.

Keep titles distinct from each other

Two articles with nearly the same title compete for the same query and confuse the reader who sees both. Review the list of titles together and look for pairs that differ only by a word the customer will not notice. Merge the pair or rewrite one around a different intent. Distinct titles also make the search result page easier to scan.

Check the titles against the saved replies and the intake form. When a form label, a reply subject, and an article title use three different phrases, the desk creates three vocabularies for one problem. Align them at the same review. The alignment reduces both search failures and the time an agent spends explaining which page to read. One shared phrase is worth more than three clever variants.

Put the product area in the body

The title should carry the customer's problem, while the body should name the product, plan, and version it applies to. That division keeps the title short and still tells a reader whether the article is relevant. Put the product area in the first sentence and in a structured field if the platform supports one. Do not make the customer decode an internal product code to find the right page.

Use a short summary under the title to confirm the match. The summary can repeat the search phrase in a natural sentence and state the outcome the article delivers. A reader who lands from a search result should know within one line whether to continue. If the summary repeats the title word for word, it adds nothing and should be rewritten.

Test titles with a small set of queries

Before publishing, ask three people who did not write the article to search for it using the words they would naturally use. Watch where they look and which result they choose. A title that only the author can find is not finished. Record the queries used in the test so the next review can repeat the same set. Choose people who do not know the internal names for the task.

Repeat the test after a rename or a navigation change. The article may still be correct while the title no longer matches how customers describe the task. A small test set of ten queries is enough for a single topic area. Keep the results with the article record, not in a separate spreadsheet that nobody opens during review. A title that worked last year can fail after a single menu change.

Review titles after a rename

A product rename changes the words in the interface, the release notes, and the sales material at different times. Review the article titles when the customer-facing name changes, not only when the workflow changes. Add the old name as a redirect or a synonym for a transition period. Remove the old name when the search log shows customers have moved on.

Assign the title review to the article owner and give it a date. The owner compares the current title with recent queries and with the client's current vocabulary. Record the decision even when no change is needed, so a later reviewer knows the check actually happened. An undocumented review looks the same as no review. Set the next review date at the same time so the check does not drift.

Limits and a practical standard

Search language is not stable, and a title that matches this quarter's queries may miss next quarter's. The desk can control the vocabulary it studies, the clarity of the title, and the review date. It cannot make every customer use the same words or guarantee that the search tool ranks the article first. State that limit so a missed search does not become a claim that the article was wrong.

A practical standard is a query review before writing, a short title in customer language, a distinct set of titles, and a retest after a rename. Keep the test queries with the article and assign the next review date. Read the search log monthly rather than only when a customer complains. That rhythm catches vocabulary drift before it becomes a support queue problem.

Authoritative sources

Related planning pages