Batch slugify a list of titles with unique URL slugs

It lowercases text, removes common Latin accents, replaces punctuation and spacing with hyphens, and preserves digits. When two titles produce the same base slug, the later result receives an incrementing numeric suffix, so every returned value is unique. The original order remains unchanged, making the output easy to align with an import file, content queue, migration plan, or publishing workflow.

Create a clean slug for every title

Provide the titles in the exact order in which you want results returned. Each title is normalized into a compact URL component: uppercase letters become lowercase, common Latin diacritical marks are removed, and each run of spaces or punctuation becomes one hyphen. Leading and trailing separators disappear. Digits remain available, which is useful for release names, numbered chapters, years, and product editions. The operation expects actual strings rather than silently converting objects, booleans, or numbers, because accidental coercion can create plausible but incorrect URLs. A title must also produce at least one ASCII letter or digit after normalization. This makes failures visible when an input contains only punctuation, whitespace, or characters outside the supported transliteration range. The response contains a slugs array in the same order as the titles array and a count, so callers can confirm that every submitted row has a corresponding result. Nothing is fetched, stored, reordered, or inferred from external sources; identical input always produces identical output.

Resolve collisions without losing order

Different titles can normalize to the same slug. Capitalization, accents, repeated spaces, and punctuation distinctions all disappear during slugification, so “Cafe News,” “Café News,” and “cafe-news” share the base cafe-news. The first occurrence keeps that base. Later occurrences receive -2, -3, and further increasing suffixes as needed. Uniqueness is checked against every slug already emitted, not merely against a count of identical source strings. That detail matters when a natural title already ends in a number or when several different spellings collapse to one form. Processing remains left to right, which gives the input order clear precedence and makes reruns reproducible. If editorial priority matters, place the preferred title first so it receives the unsuffixed slug. The capability does not inspect an existing website or database, so it cannot know which slugs are already published there. Include relevant existing titles in the submitted sequence, or compare the returned array with your own reserved-slug index before writing routes.

Use the result safely in publishing workflows

Batch output is particularly useful at the boundary between editorial data and a content management system. Keep each returned slug beside the source row rather than sorting the slugs independently; positional correspondence is the simple contract that lets a spreadsheet import, migration script, or static-site generator attach the right route to the right record. Validate the entire request before persisting changes, because one invalid title rejects the operation instead of returning a partial result that could leave a migration half applied. The algorithm intentionally targets conservative ASCII URL components. It does not perform language-specific transliteration for every writing system, choose keywords, shorten long titles, check trademarks, or guarantee uniqueness against records omitted from the request. Those are separate editorial or storage concerns. For automation, one request costs $0.002, while the same deterministic logic can be exercised in the browser interface. Save the source titles along with the resulting slugs when redirects or future title changes must be audited, and avoid regenerating established public routes unless your redirect policy is ready.