Description
Write titles in Arabic, publish with clean, readable URLs in English (Latin) letters.
WordPress turns an Arabic title like مرحبا بالعالم into a link full of percent codes:
example.com/%d9%85%d8%b1%d8%ad%d8%a8%d8%a7-%d8%a8%d8%a7%d9%84%d8%b9%d8%a7%d9%84%d9%85/
Paste that link into an email, a WhatsApp message or a spreadsheet and that is exactly what people see. Arabic to Latin creates this slug instead:
example.com/mrhba-balaalm/
It works automatically for every new post, page, product, category, tag and uploaded file. No API key, no external service, no AI credits: the transliteration runs inside WordPress.
Optional: with the AI connector set up in WordPress (Settings → Connectors, WordPress 7.0+) or your own Claude or ChatGPT API key, authors can also ask for an English slug that describes the post (طبخة ملوخية → molokhia-recipe), right in the block editor or the classic editor. It’s off by default and only used when the author picks the suggestion.
What it does
- Transliterates new slugs of posts, pages, custom post types, WooCommerce products, categories, tags and custom taxonomies from Arabic script to Latin letters.
- Works in the block editor (Gutenberg), the classic editor, Quick Edit, the REST API, WP-CLI, imports and XML-RPC.
- Transliterates uploaded file names:
صورة.jpgbecomessura.jpg(optional). - Supports Arabic, Persian (Farsi), Urdu, Kurdish and Maghrebi letters, Arabic-Indic and Persian digits (٢٠٢٦ → 2026) and diacritics (مُحَمَّد → muhammad).
- Handles text pasted from PDFs and Word: Arabic letter shapes and ligatures such as ﻻ and ﷲ are read as ordinary letters, also on servers without the PHP intl extension.
- Readable results: و and ي become the vowels u and i inside words, so سعيد becomes said, not sayd, and يوسف becomes yusf.
- Regional spelling styles: Standard, Egyptian (جمال → gmal), Maghreb / French (شكور → chkour, وجدة → oujda), Franco-Arabic / Arabizi chat numbers (حبيبي → 7bibi) or Persian (Farsi), which reads the letters the Persian way: خانه → khane not khanh, وردپرس → vrdprs, قیمت → ghimt, while ماه stays mah, or Urdu, which writes common words and places the way Roman Urdu does: اردو زبان → urdu-zaban, کراچی → karachi, یہ کیا ہے → yeh-kya-hai.
- Editable table: override any letter, for example ع = 3 for Franco-Arabic (Arabizi) style, or whole words (محمد = mohammed) from the settings page.
- Latin slug preview in the block editor while you type the title, before the first save.
- Optional AI slug suggestions through WordPress’s AI connectors (7.0+) or your own Claude (Anthropic) or ChatGPT (OpenAI) key: an English slug that says what the post is about, the way people search for it (طبخة ملوخية → molokhia-recipe), or a translation of the title (molokhia-dish). Names, dishes and places stay in their usual spelling. Suggested in the block editor and the classic editor, used only when the author clicks it; cached, with a daily limit. Off by default.
- Converts existing Arabic slugs on request: preview first, choose post types and taxonomies, and follow a progress bar; any number of posts, no timeouts. Old URLs keep working: they redirect (301) to the new ones, for posts, pages, categories and tags.
- Never touches what isn’t a slug: heading anchors from table-of-contents plugins and CSS classes on your public pages keep their Arabic, so links people already shared still work.
- Never changes existing links on its own. Activating the plugin only affects new slugs.
- Leaves other languages alone: accented letters, Cyrillic and other scripts are handled by WordPress exactly as before.
Works with multilingual plugins
The plugin detects Arabic script, not the site or post language. So it behaves the same whichever multilingual plugin you use, and in every language of the site:
- WPML: tested with WPML 4.9.7: Arabic translations from the block editor, WPML’s Taxonomy Translation screen, duplicates,
/ar/URLs, and conversion of existing Arabic slugs with redirects. - Polylang: tested with Arabic, English and German languages, including
/ar/URLs and translated categories. - TranslatePress: tested together with its own slug filter;
/ar/URLs and redirects keep the language prefix. - Any other plugin that creates posts and terms through the standard WordPress functions.
Need native Arabic slugs in a specific case? The arabic_to_lat_should_transliterate filter lets you decide per slug (see FAQ).
Works with WooCommerce, ACF and multisite
- WooCommerce: product, product category, product tag and attribute term slugs are transliterated. New global attributes get a Latin name (اللون → pa_allun), which also avoids WooCommerce’s limits on long Arabic attribute names. Existing attributes and internal keys stay exactly as they are, so variable products created before you installed the plugin keep working in the cart.
- Advanced Custom Fields: new fields get Latin field names from Arabic labels (الاسم الكامل → alasm_alkaml). Existing fields are never renamed.
- Multisite: network-activate it; every site keeps its own spelling style and replacements.
For developers
- WP-CLI:
wp arabic-to-lat convert --dry-run,wp arabic-to-lat convert --post_type=product --taxonomy=product_cat,wp arabic-to-lat slug "مرحبا بالعالم"(formats: table, csv, json, count) - Filters:
arabic_to_lat_pre_transliterate(replace the result, e.g. with a translation),arabic_to_lat_should_transliterate,arabic_to_lat_is_public_request,atl_table,arabic_to_lat_convert_post_types,arabic_to_lat_convert_taxonomies,arabic_to_lat_batch_seconds - Action:
arabic_to_lat_slug_converted - REST:
GET /wp-json/arabic-to-lat/v1/slug?title=…(users who can edit posts) - Source, issues and pull requests: github.com/khusamalfas/Arabic-to-latin. Wrong transliteration, a missing letter or a bug: open an issue there with the input and the slug you expected. Install the plugin from here, not from GitHub.
بالعربية
إضافة لتحويل روابط ووردبريس العربية (الاسم اللطيف أو الـ slug، والروابط الدائمة) إلى حروف إنجليزية (لاتينية) مقروءة تلقائياً، بدلاً من الرموز الطويلة مثل %d9%85%d8%b1. تعمل مع المقالات والصفحات والمنتجات والتصنيفات والوسوم وأسماء الملفات المرفوعة، وتدعم الحروف الفارسية والأردية والأرقام العربية. متوافقة مع WPML و Polylang و TranslatePress و WooCommerce ومحرر المكوّنات (غوتنبرغ). لا تغيّر الروابط القديمة إلا عند طلبك، مع تحويل 301 من الرابط القديم إلى الجديد.
به فارسی
افزونهای برای تبدیل خودکار نامکهای فارسی، عربی و اردو در وردپرس به حروف لاتین (انگلیسی) خوانا، بهجای کدهای طولانی مانند %d9%85%d8%b1. برای نوشتهها، برگهها، محصولات، دستهها، برچسبها و نام فایلها کار میکند و با WPML، Polylang، TranslatePress و ووکامرس سازگار است. پیوندهای یکتای قدیمی فقط به درخواست شما تغییر میکنند و با ریدایرکت 301 به نشانی جدید میروند.
Who makes it
Arabic to Latin is a personal project by Khusam Alfas, who works at SEO Revolution, WordPress Agentur in Berlin. It is not a SEO Revolution product, and SEO Revolution does not provide support for it. For questions and bug reports, please use the support forum here on WordPress.org.
External services
The plugin works without any external service. Only if you switch on the optional AI slug suggestions does it connect to an AI provider:
- WordPress AI connector (WordPress 7.0+): the request goes through WordPress’s built-in AI Client to the service you set up in Settings → Connectors (for example Anthropic, OpenAI or Google Gemini at
https://generativelanguage.googleapis.com), under that service’s terms, which its provider plugin lists. - Anthropic (Claude) with your own API key,
https://api.anthropic.com/v1/messages— Commercial Terms, Privacy Policy. - OpenAI (ChatGPT) with your own API key,
https://api.openai.com/v1/responses— Services Agreement, Privacy Policy, API data usage.
What is sent, and when: the post title and the first 300 words of the post text, each time an author clicks “Suggest” in the block editor or the classic editor, or an administrator clicks “Test connection”. Nothing is sent automatically, on saving or publishing, or about visitors. The provider returns a suggested slug.
Installation
- In your WordPress admin go to Plugins → Add New, search for Arabic to Latin and click Install, then Activate.
- That’s it: new slugs are transliterated from now on.
- Optional: go to Settings → Arabic to Latin to try a title, add your own replacements, or convert slugs that already exist.
Manual installation: upload the arabic-to-lat folder to /wp-content/plugins/ and activate the plugin in the Plugins menu.
FAQ
Will activating the plugin change or break my existing links?
No. Activation only affects slugs created from then on. Existing Arabic URLs keep working exactly as before. Converting existing slugs is a separate, optional step under Settings → Arabic to Latin, with a preview.
What happens to old URLs if I convert existing slugs?
They redirect with a 301 to the new URL, for posts, pages (including child pages), custom post types, categories, tags and custom taxonomies, including paginated archives (/page/2/), feeds and tracking parameters like ?utm_source=. Back up your database first, and update links in menus or other sites where you can.
I edit an old post or category whose slug is still Arabic. Will its URL change?
No. Saving an old post, page, category or tag, from the block editor, the classic editor, Quick Edit or the term edit screen, keeps its slug. Only a slug you actually retype changes, and then the old URL redirects to the new one.
What if I deactivate the plugin after converting?
Your new Latin slugs stay. Old Arabic post URLs keep redirecting (WordPress does that itself), but old page and category URLs only redirect while the plugin is active.
I’m moving my site with an importer. Will my Arabic URLs change?
No. When an importer brings in posts and terms with their slugs (the WordPress Importer and others that use WordPress’s import mode), those slugs are kept, so the moved site keeps its URLs. Items imported without a slug get a Latin one.
Are Latin slugs better for SEO than Arabic slugs?
Google can read Arabic URLs, so they are not a ranking problem in themselves. Latin slugs are shorter, look clean when shared in email, chat, social media and printed material, and don’t get cut off or garbled by tools that don’t handle encoded URLs. Choose what fits your audience. You can also keep Arabic slugs for one language of a multilingual site with a filter.
Why transliterate instead of translating the slug to English?
Translation needs an external service or an AI API key, costs money per post, sends your content to a third party and can produce a slug that doesn’t match the page. Transliteration is instant, free, private and predictable. You can always type an English slug yourself; the plugin never overwrites a slug you entered in Latin letters.
If you do want English slugs, switch on the optional AI suggestions (see below): they use your own API key, only run when an author asks, and transliteration stays the default.
Can I change how a letter is written?
Yes. Under Settings → Arabic to Latin → Custom replacements, add one line per change, for example ع = 3 or ة = h. You can also replace whole words: محمد = mohammed. Changes apply to new slugs.
Does it work with WPML, Polylang and TranslatePress?
Yes. The plugin works from the characters in the title, not from the language setting, so every language of a multilingual site behaves the same. WPML, Polylang and TranslatePress were tested with /ar/ language URLs, translated posts and translated categories.
How do I keep Arabic in some slugs or file names?
Use the arabic_to_lat_should_transliterate filter. It receives the text and a context (save for slugs, file for file names); return false to keep the Arabic. For example, to keep Arabic file names but transliterate slugs, add this to your theme’s functions.php or a code snippets plugin:
add_filter( 'arabic_to_lat_should_transliterate', function ( $yes, $text, $raw, $context ) { return 'file' === $context ? false : $yes; }, 10, 4 );
You can also simply untick Transliterate file names in the settings.
Which spelling style should I choose?
Standard fits most sites. Choose Egyptian if your readers write ج as g (Gamal, Giza), Maghreb for French-style spellings common in Morocco, Algeria and Tunisia (ch, ou), or Arabizi if your audience writes Franco-Arabic with chat numbers (3 for ع, 7 for ح). The settings page shows the same street name in every style. It applies to new slugs only.
Will it change the anchors of my table of contents?
No. On public pages the plugin only transliterates when a post or term is actually being created. Heading anchors and CSS classes that themes and table-of-contents plugins build from Arabic text stay as they were, so links with #anchors that people shared keep working.
Does it work with WooCommerce?
Yes. Product, category, tag and attribute term slugs are transliterated. Existing variable products keep working, and WooCommerce attribute terms are never touched by the converter, because existing variations depend on them.
Does it support Persian (Farsi) and Urdu?
Yes: پ چ ژ گ ک ی and the Urdu letters ٹ ڈ ڑ ں ے ہ are included, as are Persian digits.
For Urdu sites, choose the Urdu spelling style in Settings → Arabic to Latin. Urdu, like Persian, does not write short vowels, so a letter table alone gives ardu for اردو and krachi for کراچی. The Urdu style knows about 60 common words and place names as whole words (اردو → urdu, لاہور → lahore, اسلام آباد → islamabad, ہے → hai) and writes a final ہ after a consonant as a (زندہ → zinda). Other words still get the letter-by-letter spelling (بڑا → bra). Corrections from Urdu readers are welcome on GitHub (issue #2).
Does it work with ACF (Advanced Custom Fields)?
Yes. When you add a field with an Arabic label, the generated field name is Latin, so you can use get_field( 'alasm_alkaml' ) instead of an Arabic key. Existing fields keep their names, because your content is stored under them.
My site has thousands of posts. Will the conversion time out?
No. It runs in short batches with a progress bar until everything is done, and you can limit it to some post types or taxonomies. On the command line, use wp arabic-to-lat convert.
How do the AI slug suggestions work?
They suggest an English slug that says what the page is about, instead of a letter-by-letter transliteration. For طبخة ملوخية the normal slug is tbkha-mlukhiya; the AI suggests molokhia-recipe (style “Describe the post”: the words people search for) or molokhia-dish (style “Translate the title”). Names of people, places and dishes keep their usual Latin spelling.
To use it, go to Settings → Arabic to Latin → AI slug suggestions, switch it on and choose where the AI comes from. On WordPress 7.0 and later, the WordPress AI connector uses the AI service you already set up in Settings → Connectors (tested with the official providers for Anthropic Claude, OpenAI and Google Gemini), with no key to paste here. On any version you can instead choose Claude or ChatGPT and paste your own API key.
In the block editor a panel “English slug (AI)” appears (in the classic editor, a box with the same name in the sidebar): click “Suggest”, and the post title and the start of the post are sent to the provider. Nothing changes until you click “Use this slug”, and you can still edit it. While the feature is switched off, nothing is sent anywhere.
What do AI suggestions cost, and can they run up my bill?
You pay your AI provider per request; the plugin itself is free. One suggestion sends the title and up to 300 words of the post (about 500 to 1,800 tokens) and gets a short answer back. At the providers’ list prices on 12 November 2026, one suggestion costs roughly:
- Claude Haiku 5.5 or GPT-6 Luna: less than 0.05 cent
- Claude Sonnet 5.5 or GPT-6.1 Sol: 0.3 to 0.9 cent
- Claude Opus 5.5 (the default for Claude): 0.6 to 1.7 cents
- GPT-6 Astra (the default for ChatGPT): 1.5 to 4.3 cents
Prices change: check Anthropic’s pricing and OpenAI’s pricing. With the WordPress AI connector, the cost depends on the service and model set up there.
The settings page shows this cost beside each model, so you can choose with the price in view. You can also type the ID of a model released after this version of the plugin, and with the WordPress AI connector pick one of the models it offers or let WordPress choose.
To keep the bill predictable, asking again for the same title and text is answered from a cache for free, a daily limit (100 requests by default, changeable in the settings) stops requests until the next day, and each user who is not an administrator can make at most 25 paid requests a day. At the default limit, even the most expensive model stays under about $5 a day.
Where is my API key stored?
Encrypted in the database, using a key derived from your site’s WordPress salts, and never shown again on the settings page (only its last four characters). To keep it out of the database entirely, define ARABIC_TO_LAT_ANTHROPIC_KEY or ARABIC_TO_LAT_OPENAI_KEY in wp-config.php. Uninstalling the plugin deletes a stored key.
I used version 0.3. Anything to do?
No. Your existing slugs stay as they are and the atl_table filter still works. Version 1.0 fixes slugs not being converted in the block editor and no longer turns non-Arabic characters into dashes.
Screenshots
Changelog
1.2.2
- New: choose the AI model with its cost in view. Each Claude and ChatGPT model in Settings → Arabic to Latin shows what one suggestion costs (for example Claude Haiku 5.5: under 0.05 cent; GPT-6 Astra: 1.5 to 4.3 cents), with the date of the prices and links to both pricing pages. Under the daily limit, an estimate of what today’s requests cost at most.
- New: with the WordPress AI connector (7.0+), pick one of the models it offers, or let WordPress choose as before. If that model is no longer available, WordPress uses another one instead of failing.
- New: an advanced field for the ID of a model released after this version. Only lowercase letters, digits, dots and hyphens are accepted.
- New: AI slug suggestions in the classic editor, as an “English slug (AI)” box in the sidebar that works like the block editor panel.
- New: an Urdu spelling style (issue #2). Urdu writes no short vowels, so letters alone gave ardu for اردو and krachi for کراچی. The style knows common words and place names (اردو → urdu, لاہور → lahore, اسلام آباد → islamabad) and writes a final ہ after a consonant as a (زندہ → zinda). Opt-in; the Standard style and every other style give exactly the slugs they gave before.
- OpenAI accounts with no credit left now get the billing message instead of “wait a minute and try again”.
- Hardening: settings written from code (WP-CLI, imports, other plugins) are checked like the settings form; uninstalling on a multisite network removes the settings and stored API keys of every site, not only the main one; without the PHP intl extension, the Persian and Urdu letter shapes copied from PDFs (پ چ ژ ک گ ی) are converted too.
- The FAQ gives real prices per suggestion for each model and explains what a suggestion is. Tested with the official WordPress AI providers for Anthropic, OpenAI and Google Gemini.
1.2.1
- Security: uploaded file names are cleaned again with WordPress’s own rules after transliteration. Before, a user allowed to upload files (author and above) could craft a name that placed the file outside the uploads folder, or kept an executable inner extension such as .php. that WordPress normally neutralises. Update recommended.
- Security: each non-administrator now has a daily cap for paid AI suggestions (default 25, filter
arabic_to_lat_ai_user_daily_limit), so one account cannot use up the site’s AI budget. - File names with several dots now get the same treatment as in WordPress: صورة.نسخة.jpg becomes sura.nskha_.jpg, like photo.copy.jpg becomes photo.copy_.jpg.
- Fixed a PHP warning in old-URL redirects when a page’s parent had been deleted.
1.2.0
- New: optional AI slug suggestions, through the AI connector set up in WordPress 7.0+ (Settings → Connectors) or with your own Claude (Anthropic) or ChatGPT (OpenAI) API key. In the block editor, ask for an English slug that describes the post (طبخة ملوخية → molokhia-recipe) or translates the title (molokhia-dish); it is used only when you click “Use this slug”. Off by default; while off, nothing is sent anywhere.
- Keys are stored encrypted (or defined in wp-config.php) and never shown again. Suggestions are cached, and a daily limit protects your API bill.
- Tested with WordPress’s AI connectors for Anthropic (Claude) and Google (Gemini), including Gemini’s own error answers such as a wrong API key.
- Every AI answer is checked: only a clean Latin slug (a-z, digits, hyphens, up to 8 words) is accepted, and it is made unique like any WordPress slug.
- Transliteration is unchanged: no existing site’s URLs move, and nothing calls the AI on save.
1.1.0
- New: re-convert slugs the plugin already converted, for sites that change spelling style. It is a separate, optional step on the settings page, off by default, with a preview and two confirmations, and old URLs are redirected (301) to the new ones. Only slugs this plugin produced are touched: a slug you typed yourself is recognised and left alone. Uploaded files are never renamed, because there is no redirect for a file. Also available as
wp arabic-to-lat convert --reconvert. - New: a Persian (Farsi) spelling style. The default table reads the letters as an Arabic speaker would, which is wrong for Persian: خانه became khanh instead of khane, وردپرس became wrdprs instead of vrdprs, and قیمت became qimt instead of ghimt. The new style fixes those, and keeps the h where Persian keeps it: ماه is still mah, دانشگاه still danshgah.
- The Standard style and every Arabic slug it produces are unchanged, so no existing site’s URLs move. The Persian style is opt-in, in Settings → Arabic to Latin.
- Known limit: short vowels are still not written, so مشهد is mshhd, not mashhad. A letter table cannot supply vowels that the script does not write. Reports from Persian speakers are welcome on GitHub.
1.0.0
- Rewritten and tested with WordPress 6.4 – 7.1 and PHP 7.4 – 8.4 (with and without the intl extension).
- Fixed: slugs were not transliterated in the block editor (Gutenberg / REST API).
- Fixed: a security issue in the term lookup query.
- Fixed: non-Arabic characters (accents, Cyrillic, …) were replaced with dashes.
- Changed: activating the plugin no longer rewrites existing slugs. Converting them is optional, with a preview, from the settings page or WP-CLI.
- New: 301 redirects from old Arabic URLs of converted posts, pages and terms.
- New: Persian, Urdu, Kurdish and Maghrebi letters, Arabic-Indic and Persian digits, diacritics and shadda.
- New: more readable results (و and ي as vowels inside words).
- New: settings page with a live test, regional spelling styles (Standard, Egyptian, Maghreb, Arabizi) and custom replacements.
- New: Latin slug preview in the block editor before the first save.
- New: converter runs in batches with a progress bar and can be limited to chosen post types and taxonomies (also
--post_type/--taxonomyin WP-CLI). - New: Latin field names for new ACF fields, Latin taxonomy names for new WooCommerce attributes.
- New: heading anchors and CSS classes on public pages are never changed.
- New: multisite support (per-site settings).
- New: compatibility with WPML, Polylang, TranslatePress and WooCommerce (all tested).
- New: developer filter
arabic_to_lat_pre_transliterate. - New: Arabic letter shapes and ligatures from PDFs and word processors (ﻻ, ﷲ) are converted, also without the PHP intl extension.
- Safe editing: saving old posts, pages, categories and tags never changes their Arabic slug; deliberate slug changes on pages and terms redirect from the old URL.
- Imports keep the slugs of the source site.
- Redirects keep query strings and work for paginated archives and feeds.
- Uploaded images keep their Arabic title; only the file name becomes Latin.
- New: WP-CLI commands
wp arabic-to-lat convertandwp arabic-to-lat slug.
0.3
- Fixed description, tested with WordPress 5.7.1, added license.
0.2
- Updated description.
0.1
- Initial release.



