Published September 1, 2026.
As a library grows, titles tend to converge around familiar phrases. A uniqueness review helps an editor catch collisions while keeping titles specific, readable, and faithful to the article.
Search the full inventory
Compare the proposed title and its important noun phrases across blog, research, service, resource, and alternative pages. Include live indexes as well as source files so an undeployed or historical route is not overlooked.
Test the promise
Ask what the reader will be able to do after reading. The title should name that purpose without claiming a result the body cannot support. Adding a year, adjective, or punctuation mark does not create a distinct purpose.
| Risk | Editorial response | | --- | --- | | Exact title match | Stop and reconcile identity | | Same task, different words | Refresh or consolidate | | Related task, unclear distinction | Narrow the title and opening | | Distinct task | Document the difference |
Check metadata alignment
After approval, confirm the HTML title, visible heading, index card, structured headline, and canonical route all describe the same article. Variations may fit interface constraints, but they should not change the promise.
Follow the title-description alignment check and the primary-body duplicate check.
Frequently asked questions
Can two titles share the same main keyword?
Yes, when they serve clearly different tasks and the distinction is visible. A shared term alone is not a duplicate.
Who approves a major title change after publication?
The accountable editor should approve changes that alter public identity or search intent, with redirects considered separately if the route changes.