URL guides

Check shortcode collisions before importing a batch

·

A team importing event links can check a saved list before a handoff. Export codes from the same route group and include any locally reserved words in the inventory. Two shortcodes under different parents need separate checks if the site treats them as different namespaces.

Slug Availability Simulator

Trace the first unused suffix

Enter spring as the proposal. In the existing list put spring on line one, spring-2 on line two and Spring on line three. With the default case-sensitive comparison the match is line one and the proposed alternative is spring-3. With case ignored, both lines one and three match.

Compare equivalent representations

Try café against caf%C3%A9. After decoding and NFC normalization the two forms match. A decomposed e followed by a combining acute accent matches too. Cafe without the accent remains distinct even with case ignored. The comparison does not transliterate words.

Unicode Standard Annex 15: Unicode normalization formsWHATWG URL Standard: URL path segments

Use the inventory as an import check

A blank inventory means zero entries checked. It gives you no evidence about names currently assigned by a service. Add proposed codes to the list as you process a batch so later rows see earlier choices.

If a copied inventory line contains a full URL or an encoded slash, the tool flags the line instead of silently skipping it. Extract individual shortcodes first. At publication time use the site’s normal uniqueness check because other editors may have claimed a code since export.

Common questions

Why can an encoded and a plain code collide?

Percent encoding represents bytes in a URL. The simulator decodes once and compares normalized text, so two spellings can identify the same code in this model.

Does ignoring case remove accents too?

No. The option lowercases normalized codes. Keep separate notes if the system you publish to has different equivalence rules.

Sources

Put it into practice.

Related guides