How to write unique title tags across a tool site
Give every tool and guide one task-and-outcome title that stays distinct from adjacent pages without keyword padding.
Write the title from the page's specific task and finished outcome, then add only the context needed to distinguish it from neighboring pages. Audit the full inventory before publication; a title is not unique merely because one adjective or keyword order changed.
Start with the page's one defensible promise
Summarize the job in a verb, the object being changed or understood, and the result the user receives. Use the actual page interface and evidence to decide the promise, not a keyword list detached from the product.
Distinguish adjacent pages with meaningful context
Add a source type, output, privacy boundary or method only when it changes the choice. JSON formatting and JSON-to-CSV both begin with JSON, but one returns validated indented JSON while the other returns a flat CSV file. That difference belongs in their titles.
Keep the highest-signal words easy to scan
Put the recognizable task and outcome before the site suffix. Remove repeated qualifiers, empty superlatives and lists of near-synonyms. A concise title can still be specific; a long title can still be ambiguous.
Audit strings and promises before publishing
Check exact title duplicates, near-duplicate wording, repeated H1s and duplicated primary intent. Review the title beside its canonical route, description and neighboring search result so a string-level fix does not hide a page-level overlap.
Check the source against the result
Two adjacent pages both start with JSON, but one validates syntax and the other flattens records into a spreadsheet file.
JSON Formatter – Validate and Inspect JSON Locally | MCXAI JSON to CSV – Flatten Data in Your Browser | MCXAI
The shared JSON term preserves the family, while validate and inspect versus flatten into CSV makes the choice clear without stuffing variants.
Pair title review with intent review
A unique string is not enough when two routes still promise the same task. Check the route, primary intent and evidence together.
Open the duplicate-intent audit guide