URL guides

Choose a readable path segment for a multilingual page

·

Imagine publishing a page titled Café & شاي 2026. The slug needs to make sense to someone sharing the menu. Google recommends descriptive words, the language of the audience and hyphens between words. No universal character count establishes whether a page will rank.

Text to Slug

Enter Café & شاي 2026 and generate the slug. The result is café-شاي-2026. The ampersand and spaces form a single word boundary. The Arabic text remains readable to your audience. Use the plain slug in a CMS field that performs its own URL encoding.

Google Search Central: URL structure best practices

Choose the representation your CMS expects

The same é can be written as one Unicode character or as e followed by a combining acute accent. Normalization gives the same slug for both spellings. The UTF-8 encoding of é uses two bytes, displayed as %C3%A9 in the encoded segment.

A field that accepts human-readable slugs may encode a pasted percent sign as %25. Inspect the saved path. If café appears as caf%25C3%25A9 and the site displays percent sequences to readers, try the plain café value in a draft.

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

Check two different titles before publishing

With accent folding enabled, Café Menu and Cafe Menu both become cafe-menu. Check the proposal against the routes under the same parent in your publishing system. A descriptive distinction such as cafe-menu-evening is more useful to diners than a number chosen merely to avoid a collision.

Google Search Central: URL structure best practices

Common questions

Does the generator remove words like the or of?

It keeps the title’s words. Edit the input when a shorter phrase conveys the same meaning to your readers.

What happens with a title made entirely of punctuation?

It produces a diagnostic. Supply a meaningful title containing at least one letter or number before downloading.

Sources

Put it into practice.

Related guides