Published September 8, 2026.
Two unique slugs can still create the same reader experience. A title-collision review compares the promise behind each draft before both pages reach the index.
Normalize the promise
Rewrite the proposed title as a plain sentence: audience, task, constraint, and outcome. Search the content inventory for the main noun, verb, and close synonyms. Compare descriptions and openings, not titles alone.
Decide whether the page is distinct
A separate article should have a different job, evidence set, workflow, or decision point. A new adjective, year, or “checklist” suffix is not enough. When the promises overlap, strengthen the angle, merge the idea into an existing page, or stop the draft.
Preserve the decision
Record the closest pages and one sentence explaining the distinction. That note helps future editors understand why both routes exist and prevents the same topic from returning under another name.
Run the check across the day's batch as well as the back catalog. This keeps BusinessGrowthAssistant's daily cadence focused on useful coverage rather than raw URL volume.