---
slug: "use-plain-language-in-navigation-labels-instead-of-internal-product-names"
name: "Use plain language in navigation labels instead of internal product names"
category: "navigation"
grade: "tested"
page_types: ["homepage","product"]
sites_observed: 3
evidence_count: 1
example_ids: []
version: 3
updated_at: "2026-10-15T14:40:37.228Z"
url: "https://liftwire.io/tactics/use-plain-language-in-navigation-labels-instead-of-internal-product-names"
---

# Use plain language in navigation labels instead of internal product names

**Evidence grade: Tested.** Outside evidence supports it: a published experiment, or customer sites where verify_change found the change live long enough ago to count as kept.

Observed on 3 corpus sites. Page types: homepage, product.

## Why it works

Menu items that use internal product names or jargon require visitors to have pre-existing knowledge to understand what they mean. This creates friction because user testers could not guess what unfamiliar terms referred to. Using clearer, more descriptive labels helps visitors quickly identify relevant sections without needing to decode terminology.

## Evidence

- [A case study in redesigning navigation](https://conversion-rate-experts.com/sfg20-navigation-win-report) (experiment, supports)

## Examples

No published examples yet.

## Implement it

The full implementation spec (where on the page, structure, copy patterns, acceptance criteria) is returned by `get_tactic` through the Liftwire MCP server. Setup: https://liftwire.io/mcp