<p>There is technically nothing wrong with using them in a URI since they are valid URI characters.  Even multi-byte characters (Chinese, Korean, Japanese, etc.) are valid in the URI (i.e. domain.com/漢字漢字).</p>

<p>However, some people have requested that they not be allowed in the slug, so for the upcoming 2.2 release, we've added a config setting where you can disable the behavior and multi-byte characters are stripped and high-ASCII characters like ó are swapped with their low-ASCII counterparts (o).</p>

<p>I can't speak to any other non-technical reasons why they might not want to be used (SEO, etc.).</p>

CC BY-SA 3.0
2014-08-28T23:16:30.583Z
2014-08-28T23:16:30.583Z
Brad Bell
<p>I'm working on a site with both english and spanish locales. Crafts localization features have been awesome so far, and I've been embracing Craft's ability to easily localize URLs.</p>

<p>For example, if I have a section on conservation, the english url would be:</p>

<pre><code>www.mysite.com/conservation
</code></pre>

<p>And the spanish one would be:</p>

<pre><code>www.mysite.com/es/conservación
</code></pre>

<p>Am I going to run into any technical issues by allowing accented characters in my urls?</p>

<localization><url>
Is there any downside to using localized characters in urls?
# Is there any downside to using localized characters in urls?

(Asked by: username_0 on 2014-08-28)

I'm working on a site with both english and spanish locales. Crafts localization features have been awesome so far, and I've been embracing Craft's ability to easily localize URLs.
For example, if I have a section on conservation, the english url would be:
www.mysite.com/conservation

And the spanish one would be:
www.mysite.com/es/conservación

Am I going to run into any technical issues by allowing accented characters in my urls?

**Tags:** localization, url

---

## 1 answers

### Answer by username_1 on 2014-08-28. Score: 2 | Accepted answer

There is technically nothing wrong with using them in a URI since they are valid URI characters. Even multi-byte characters (Chinese, Korean, Japanese, etc.) are valid in the URI (i.e. domain.com/漢字漢字).

However, some people have requested that they not be allowed in the slug, so for the upcoming 2.2 release, we've added a config setting where you can disable the behavior and multi-byte characters are stripped and high-ASCII characters like ó are swapped with their low-ASCII counterparts (o).

I can't speak to any other non-technical reasons why they might not want to be used (SEO, etc.).


---

