The end of duplicate-name chaos for professionals

There are thousands of professionals named John Smith, and most of them deserve a page Google ranks. There is exactly one john-smith. That single collision — two people, one URL — is the entire problem a name platform has to solve, and the way it's solved decides who gets found and who gets a punishment slug.

First-come-first-served sounds fair until you're the second John Smith. The person who typed their name into a form three weeks after you doesn't deserve to be invisible — they deserve a URL that can actually win. Our slug engine makes that the default outcome, not a workaround.

The collision problem is a ranking problem

Google has one #1 result for a query. When two identical pages compete for john-smith, one of them is structurally doomed — it splits the very small number of ranking signals either page can earn. The loser doesn't just rank second; it usually vanishes from the first page entirely, because Google prefers the page with the cleaner signal.

The fix isn't to make the fight fairer. It's to end the fight — to give each professional their own query to win.

A slug chain that turns collisions into keywords

When john-smith is taken, the slug engine walks a curated chain of descriptors instead of appending meaningless digits: john-smith-designs, john-smith-codes, john-smith-austin. Each one is a real keyword — name plus profession or location — that a person can actually rank for.

This is the part most people miss: a long-tail query like john-smith-designs is often more winnable than the bare name. It has lower competition, higher intent (someone searching for a designer named John Smith is closer to hiring), and a title that tells Google exactly what the page is about.

Race-safe by construction

Two people claiming in the same millisecond is not a theoretical problem — it's a Saturday afternoon. Every claim runs inside a database transaction against a unique constraint on the slug, so the second claim can never silently overwrite the first.

• Each claim is atomic: the slug is reserved and the page is created in the same transaction.
• A unique index on the slug makes a double-claim a guaranteed failure, not a race condition.
• The losing claim walks the descriptor chain automatically and gets its own winnable URL.
• Load-tested at 1,000 concurrent claims with zero duplicate slugs — ever.

What this means for your page

The slug you hold is unique forever. It can't be taken from you by a faster claim, and nobody else can be silently pointed at your URL. If you share a name with a thousand people, you get a query you can win — not a punishment.

Duplicate-name chaos ends the moment the platform treats every professional as deserving of a URL. That's the whole engineering thesis: one person, one winnable slug, no exceptions.