URL Slug Guide: Thai or English, Length, Encoding and 301 Redirects

URL Slug Guide: Thai or English, Length, Encoding and 301 Redirects

SEONovember 18, 2026
By Antonio Fernandez

TL;DR

  • A URL slug is the last part of a URL that names one page. Use readable words, hyphens instead of underscores, and one consistent case, as Google's URL structure documentation recommends (it says URLs are case sensitive).
  • A Thai slug is a supported choice: Google says to use words in the reader's language and to percent-encode non-ASCII characters. Each Thai character becomes 9 characters (for example ก becomes %E0%B8%81).
  • Pick one slug pattern for the whole site and set it before publishing. Changing a slug changes the URL, so it needs a single-hop 301 redirect from the old URL.
  • Google gives no fixed slug length, and says keywords in the URL path alone have hardly any effect on ranking beyond appearing in breadcrumbs. Keep the slug short enough to understand at a glance.

A URL slug is the final part of a URL that identifies one specific page, such as url-slug-explained in example.com/blog/url-slug-explained. A good slug uses readable words separated by hyphens, is short enough to understand at a glance, and does not change after publishing. Thai or English both work; choose by the language of your readers and the tools your team uses.

It looks like a small decision, but a wrong one is expensive to fix, because changing a slug changes the page's URL. This guide covers what a slug is, how it differs from a URL and a permalink, what the %E0 encoding of Thai slugs means, how to write slugs that suit SEO, how long they should be, and how to set up a 301 if you must change one, including the steps in WordPress and Shopify.

What is a slug?

A slug is the part of a URL that names one page. It sits after the last slash of the path. In the address example.com/blog/how-to-pick-a-slug, the slug is how-to-pick-a-slug. The word blog is a category or folder, which some sites call a base or prefix, and it is not part of the slug.

Content management systems normally generate the slug from the title, and you can edit it before publishing.

The three terms overlap because they describe levels of the same thing.

  • URL is the full address of a page: protocol, domain name, path and sometimes parameters.
  • Slug is the last segment of the path that identifies a single page.
  • Permalink is the full URL of a page that is meant to stay permanent. WordPress uses the word formally for the URLs of posts and pages, and a permalink structure is the rule that decides how URLs are built, for example post name only, or category followed by post name.

An illustrative case: if a site's permalink structure is /blog/ followed by the post name, and a post titled "Setting up a URL slug" has the slug setup-url-slug, then its permalink is https://example.com/blog/setup-url-slug/. Change one word in the slug and the permalink changes with it.

Should you use a Thai or English slug?

There is no single right answer for every site. Google's documentation on URL structure recommends using words in your audience's language, including transliterated words, for example German words for a German audience. That means a Thai slug for Thai readers is a supported choice, not something to avoid.

The trade-offs are real, though. The table sets them out.

Should you use a Thai or English slug?
OptionUpsideWatch out for
Thai slugThai readers see at once what the page is aboutBecomes a long encoded string when copied or shared in some apps, and is easy to mistype when writing redirects
English slugShort, easy to copy, never encodedMay not match the language of Thai queries and content
Romanized ThaiReadable for Thai people and never encodedNo single standard, so different editors spell the same word differently

A practical rule is to pick one pattern and apply it across the whole site. Mixing patterns page by page makes redirects, reporting and internal link rules harder to manage. On a bilingual site, using Thai or romanized slugs on the Thai version and English slugs on the English version is a sensible pattern, as long as it is applied to every page.

Does a Thai slug encoded as %E0 hurt SEO?

Short answer: it is not a ranking problem in itself, but you should understand what happens. A standard URL can only hold a limited set of ASCII characters. Characters outside that set, including Thai letters, are converted to their UTF-8 bytes and written as %XX. A Thai character takes three bytes, so it becomes nine characters: ก turns into %E0%B8%81, and the seven-character word การตลาด becomes 63 characters in encoded form.

Google's documentation says non-ASCII characters should be percent-encoded, and also says to use words in your readers' language. The two fit together. Browsers often display Thai URLs in readable form, but when you copy one into some other place you may see the long %E0 form. Three things deserve attention.

  1. Expanded length. A short Thai slug becomes much longer once encoded, so writing a long Thai title straight into the URL produces a longer address than necessary.
  2. Inconsistent forms. A link written in readable form and one written in encoded form point to the same page, but if a tool or sitemap uses a different form, reports may show two URLs. Use one form everywhere you control.
  3. Case of the hex digits. %e0 and %E0 are the same under the standard, but some systems compare them literally. When writing a redirect by hand, copy the URL from the browser instead of typing it.

Google's documentation does not say that Thai slugs are penalised, and its SEO starter guide says keywords in the URL path alone have hardly any effect on ranking beyond appearing in breadcrumbs. Treating the slug as a main ranking lever is an overreading. The reason to set it well is that readers and tools can understand the address, and you never have to change it later.

How to set a URL slug that suits SEO

These rules apply to any site, and most come from Google's URL structure documentation.

  1. Use readable words. Google recommends readable words over long ID strings. A slug like /p/42-3a5ebc9 tells a reader nothing.
  2. Separate words with hyphens. Google recommends hyphens (-) rather than underscores (_) because hyphens mark word boundaries more clearly.
  3. Use one case, such as lowercase throughout. Google treats /APPLE and /apple as distinct URLs and advises converting all text to the same case if your server treats them the same. All lowercase is the simplest way to do that.
  4. Include only what identifies the page. Drop filler words, dates and version numbers that will go out of date.
  5. Avoid special characters. Google follows the URL standard IETF STD 66, which requires reserved characters such as the question mark to be percent-encoded, so keep such characters out of slugs.
  6. Set it once, in the form you will keep. Changing it later means redirect work.

An illustrative example: suppose the post title is "10 ways to choose running shoes for beginners, our latest updated edition". The slug the system generates may be as long as the whole title. Cut it to the core of the page, for example how-to-choose-running-shoes or running-shoes-beginners. Drop the number and the words "latest edition", because next year it will no longer be the latest.

How long should a slug be, and should it include keywords?

Google does not set a correct slug length. The workable rule is to keep it short enough for a person to understand at a glance. For Thai, count the length in encoded form too.

On keywords, including the main query of the page in the slug is reasonable, because it is the phrase that describes the page, and a person who sees the address in a result or a shared message knows where the link leads. Stuffing repeated or near-identical queries into the slug has no benefit and looks like spam to readers. A slug like /seo-service-seo-agency-seo-bangkok improves nothing.

There is one more choice: whether to keep a folder in the path, for example /blog/post-name versus /post-name. A folder helps separate content types and makes reporting by section easier. Decide once when you plan the site structure, because changing it later affects every page in that folder.

How to change a slug later and set up a 301

Changing a slug gives the page a new URL. Old links, bookmarks and search results that point to the old URL break unless you redirect. You need to send visitors and Googlebot from the old URL to the new one with a 301, which is a permanent redirect. Google's documentation says permanent redirects make the target URL appear in search results, and that a server-side redirect has the highest chance of being interpreted correctly.

Recommended steps:

  1. Ask whether the change is needed. If the page is already in search results and has earned links, a slug that is plain but works is not worth the risk of changing. Change it when it is wrong: a typo, an outdated date, or an internal ID that should not be exposed.
  2. Record the exact old URL before editing. Copy it from the browser address bar.
  3. Change the slug and set a 301 from the old URL to the new one. Point it to the new URL in a single hop, not through a chain.
  4. Update internal links to the new URL directly. Do not leave internal links depending on a redirect forever.
  5. Update the sitemap and canonical tag to the new URL, and remove the old URL from the sitemap.
  6. Test it. Open the old URL in a browser, confirm it lands on the new URL with a 301 status, then inspect the new page with URL Inspection in Search Console.
  7. Keep the redirect for a long time. External sites may link to the old URL indefinitely, so do not remove the redirect after a few weeks.

Two common errors are redirecting every old URL to the home page, which discards the page's relevance, and leaving the old URL to return a 404 while links still point to it.

Setting slugs in WordPress and Shopify

WordPress

In the dashboard, go to Settings and choose Permalinks. Pick the Post name structure, which puts each post's slug directly into its address. After that, every post and page has a slug field in the editor sidebar, and you should edit it before the first publish. If the title is in Thai, WordPress generates an encoded Thai slug automatically, which you can shorten by hand. For posts, WordPress core keeps past slugs and redirects them, but its redirect code skips hierarchical post types such as pages, so set a 301 yourself for pages and test posts too. If you change the permalink structure of the whole site, prepare redirect rules for every URL as separate work. If you want a team to set WordPress up properly, see WordPress web design.

Shopify

In Shopify the equivalent of a slug is the URL handle. Shopify's help documentation says that when you change a URL on your store, you can create a URL redirect, and it manages redirects under Content, then Menus, in the admin. After you change a handle, create the redirect from the old URL to the new one, and check the redirects list again after bulk changes. For stores that need handle structure and redirects planned across the whole catalogue, see Shopify SEO.

What URL slugs mean in the Thai market

These points apply specifically to Thai-language sites.

  • Choose what your editors can maintain. If the content team can type Thai slugs correctly every time and the tools support it, Thai slugs work. If not, use English or a romanized form with a written pattern.
  • Test sharing for real. Copy a link into LINE and Facebook and see how it appears, because how an encoded URL is displayed can differ from app to app.
  • Watch spelling. A Thai word with tone marks or stacked vowels spelled wrong by a single character becomes a different URL. Check the slug spelling before every publish.
  • Bilingual sites. Give the Thai and English versions consistent slugs and set hreflang correctly. Our earlier post on Thai-language SEO covers the wider picture.

Planning URL structure across a whole site belongs to SEO in Thailand, and if you suspect your site has URL problems, an SEO audit checks for duplicate slugs, redirect loops and multiple URL forms of the same page.

Common mistakes with URL slugs

  • Letting the system build it from a long title. A slug as long as a sentence is hard to read and expands ninefold once Thai is encoded.
  • Using underscores or spaces. Google recommends hyphens.
  • Mixing upper and lower case. It risks two URLs for one page.
  • Putting dates or years in the slug. When the content is updated the URL looks old and gets changed.
  • Changing a slug without a 301. Old links and search results land on a 404.
  • Redirecting everything to the home page. It discards relevance.
  • Repeating keywords in the slug. It does not help rankings and looks like spam.

FAQ: URL slug questions

What is a URL slug?

A URL slug is the final part of a URL that identifies one page, such as url-slug-explained in example.com/blog/url-slug-explained. Content management systems usually generate it from the title and let you edit it.

Do Thai slugs make rankings worse?

There is no evidence in Google's documentation that they do. Google recommends words in the reader's language and percent-encoding for non-ASCII characters, which a Thai slug already follows. The things to watch are encoded length and consistent URL forms.

Should I change the slug of a page that already ranks?

Generally no. If the slug works, leave it. Change it only for a clear reason such as a typo, and always set a 301 from the old URL to the new one.

Should a slug contain keywords?

It should contain the words that describe the page plainly, which often includes the main query naturally. Do not repeat keywords, because it does not help rankings and makes the address look like spam.

Hyphens or underscores in a slug?

Use hyphens. Google's URL structure documentation recommends hyphens over underscores because hyphens mark word boundaries more clearly.

A good slug is one you set once and never have to touch again. If you want help reviewing your site's URL structure and redirects, talk to us about an SEO audit.

Antonio Fernandez

Antonio Fernandez

Founder and CEO of Relevant Audience. With over 15 years of experience in digital marketing strategy, he leads teams across southeast Asia in delivering exceptional results for clients through performance-focused digital solutions.

Share to:
Copy link:

Read us often? Add Relevant Audience as a preferred source so our articles surface more in your Google results.