🤔 dont put emoji name in topic slugs

I think it’s fine the way it is… and honestly when a topic title is

I :heart: rock and roll

which transliterates to the slug


that’s basically correct…


Even this example does not make full sense.

Sure it does, I would like to enter in evidence, if it pleases the court, this following video recording


It says “I love rock and roll” :wink: not heart. Ofcourse it makes sense but this is one of the few emojis that results a meaningful slug.

On the other hand, we are only considering English here. What about other languages?

for example If I create a topic like

انا :heart: روك اند رول

It would generate the following slug


In Arabic though you would probably enable encoded slugs, no?

1 Like

I have never found a good user experience with encoded slugs. So I mostly don’t enable them. Having raised this issue,I would like to say that we are still missing customizing slug feature.

Wouldn’t this be a case for a plugin that uses localized emoji short_names?

Unicode provides TTS descriptions for plugins, for example (Spanish names):

:cow: cara de vaca
:ox: buey
:water_buffalo: búfalo de agua
:cow2: vaca
:pig: cara de cerdo
:pig2: cerdo
:boar: jabalí
:pig_nose: nariz de cerdo
:ram: carnero
:sheep: oveja
:goat: cabra
:dromedary_camel: dromedario
:camel: camello
:giraffe: jirafa


As far as I can see, the only potentially serious concern might be having :poop: in a title that might cause a flag for an email client.

Granted, there are many emoji names and an infinite number of possible topic titles. But although the emoji names could make it more difficult to understand the title I can’t think of any combinations where it would render them indecipherable.

1 Like

Yeah localization is a major argument in favor of not doing what we’re currently doing.

1 Like

I would say at least for non English we should stop doing this, can be built into the slug class


AFAIK slugs are for SEO purposes since the topic id is always used at the end.

So you need to ask, what is correct for SEO purposes. If the emoji is part of the content then it is relevant. Otherwise it is not and it hurts SEO.

Would it be that emojis at the beginning and very end of the title are usually not part of the content, while emojis inside the title sometimes may be?

For example:

Why doesn’t :slight_smile: show up? A regression? :thinking:

1 Like

A post was split to a new topic: Allow me to disable emojis in topic titles

Perhaps this might be unrelated but please remember there are URLs that contain emojis otherwise known as emoji domains. For example, we own :peace_symbol:.com.

1 Like

Developers of discourse: even our emoji domain link doesn’t work automatically. For example, the peace sign domain should automatically link to ☮.com (“xn – v4h”) but it doesn’t. It goes to http://☮️.com/ (“xn – v4h2700f”) which is wrong.

Luckily there doesn’t seem to be emoji root domains, or my ignore-emojis-at-end-of-title trick will not work.

Let us know when you own mydomain.:peace_symbol:


1 Like

I may have misunderstood the original request but disabling emojis would be a bad idea since emojis are part of mobile and increasingly so every day. See iPhone X.

I think you have misunderstand.

This is not about disallowing emoji in titles. This is about not including the emoji in the slug on the URL.

The idea is that the emoji name clutters the slug and may harm SEO. On the other side, there are perfectly legit uses of emoji as part of the meaning, so they can’t simply be all filtered out.

A similar idea to filtering common words (like a, the, of) from the slug.


So :bow_and_arrow:.to/:earth_americas::mag_right: won’t work?

Ok, emoji words are now stripped from slugs, as this makes more sense for all languages.