Hamza and Taa Marbuta: Arabic Spelling in SEO
Arabic allows more than one correct spelling for many words. Here's how hamza, taa marbuta and alif maqsura variants affect keywords and how to handle them.
Arabic spelling variants — hamza placement, taa marbuta versus haa, alif maqsura versus yaa — mean the same word can be typed correctly in more than one way, and search behavior splits across all of them. Handle this by researching every variant, picking one for your title and URL, and letting the rest appear naturally in your body text.
This is one of the more technical pieces of Arabic SEO, and it's easy to miss entirely if your keyword tool reports each spelling as its own low-volume row instead of flagging them as variants of one query.
On this page
Why does Arabic spelling vary so much in search?
Because formal written rules and everyday typing habits diverge, and search reflects typing habits. Arabic has clear orthographic rules for where a hamza sits and how a word ends, but a large share of real-world typing — on phones especially — simplifies or skips them, and search engines see both versions typed by real people.
This isn't a sign of poor literacy or a niche edge case. It's closer to how English speakers write "email" and "e-mail," or "color" and "colour," except it happens far more often in Arabic because the affected letters appear inside extremely common words.
Mobile typing makes it more common still. Most Arabic keyboards default to the simpler, unmarked forms unless a user actively selects the marked variant, and predictive text often reinforces whichever form was typed most recently rather than the formally correct one. A generation of searchers who type mostly on phones produces exactly the mixed spelling patterns this post is about, at scale.
None of this is a problem you can research away once and forget. As phones, keyboards and autocorrect defaults change, the balance between spelling variants can shift too, which is one more reason to treat variant-checking as part of a recurring research process rather than a one-time cleanup.
The variants that matter most: hamza, taa marbuta, alif maqsura
Three patterns account for most of the spelling variation that affects Arabic keyword research.
| Variant | What happens | Why it happens |
|---|---|---|
| Hamza on alif | أ or إ is often typed as a plain ا | The hamza seat is easy to omit when typing quickly, especially on phones |
| Taa marbuta | ة is often typed as ه at the end of a word | The two letters look similar and are adjacent on some keyboard layouts |
| Alif maqsura vs yaa | ى is often typed as ي | Many keyboards and autocorrect systems default to the more common yaa form |
These aren't obscure edge cases — they occur inside some of the most commonly searched words in Arabic, which is exactly why they matter for keyword research rather than being a minor spelling curiosity [1].
The hamza case is the most layered of the three, because Arabic actually has several hamza forms depending on the letter it sits on — أ, إ, ؤ, ئ, and the bare ء — each governed by its own placement rule. A keyword tool rarely distinguishes between "wrong hamza seat" and "no hamza at all," which is why manual review of your top keywords, rather than trusting the tool's grouping, is worth the extra time.
Taa marbuta and haa cause a different kind of confusion, because they're pronounced almost identically in casual speech even though they're visually distinct letters with different grammatical roles. That similarity in sound is very likely why the substitution happens so often in typing — people are transcribing what a word sounds like rather than recalling its written form letter by letter.
How do search engines handle these variants?
Partially, and inconsistently across engines and query types. Google's own guidance on consolidating near-duplicate content focuses on full pages and URLs rather than single-word spelling variants within a query, which means you can't assume the search engine silently merges every variant on your behalf [2].
How do you research keywords across spelling variants?
Treat variant-hunting as a required step in keyword research, not an afterthought once a list is built.
Search each seed keyword in both common spellings
Note the top-ranking pages for each. If different pages rank for each spelling, the variant matters enough to plan for explicitly.
Check your keyword tool's suggestions for near-duplicate rows
Look for phrases that differ only by one letter near the end or by a hamza mark, and flag them as the same underlying query.
Add the volumes together
Sum matching variants before deciding whether a topic has enough real search volume to justify a page.
Note which spelling is more common for that specific term
The more common spelling isn't always the formally correct one — check the data for each keyword individually rather than applying one rule everywhere.
Which spelling do you put in your title and URL?
Whichever one your research shows is searched most often for that specific term — and use it consistently across the title, the main heading and the URL. Consistency matters more than which variant you pick, because a page that mixes spellings across its own title and URL looks unpolished and can confuse both readers and crawlers about what the page is actually about.
If you're deciding between an Arabic-script URL and a transliterated one at the same time, that's a related but separate decision — our comparison of Arabic URLs vs transliteration covers it directly, including how spelling variants interact with each URL style.
One more practical habit worth adopting: keep a short internal glossary of the primary spelling you've chosen for each of your recurring priority keywords, and share it with every writer and translator touching Arabic content. A one-page reference stops the spelling drift that naturally happens when three different people write Arabic content for the same site over a year, each defaulting to whatever they personally type.
Does this affect anything beyond the page itself?
Yes — anywhere a keyword gets typed by a human on your team, not just on the published page. Ad campaign targeting, internal search filters, product titles in a store feed and even customer support macros can all end up split across spelling variants if nobody standardizes them, quietly fragmenting data that should be read as one number.
Search Console reporting is a common casualty. Two spelling variants of your main keyword show up as two separate query rows, each with modest impressions, and a quick glance can make a topic look weaker than it actually is until someone adds the rows together by hand. Build that addition into your regular reporting rather than rediscovering it every time.
Do you need a linguist to get this right?
No. This is a pattern-recognition task more than a formal grammar one — you're identifying which two or three spellings a given word commonly takes, not producing a grammatically perfect Arabic sentence. A careful native speaker checking your priority keyword list against actual search results can do this in an afternoon.
Where formal knowledge helps more is in writing the body copy itself, so the finished page uses correct Arabic throughout rather than only around the target keyword. That's a separate skill from variant research, and it's worth having a native editor review the finished draft even when the keyword mapping was done by someone else earlier in the process.
What does a variant-aware keyword sheet actually look like?
Add two columns to your normal keyword spreadsheet: a "variant group" column that assigns matching spellings the same ID, and a "primary spelling" column that names which form goes in the title, heading and URL for that group. Every writer briefed from that sheet then works from the same decision instead of making their own call mid-draft.
Keep the sheet as the single source of truth rather than letting each writer's preference quietly become the standard. A spreadsheet a whole team can see beats a convention that lives only in one person's memory, especially once more than one person is producing Arabic content for the same site.
How this connects to hreflang and translation choices
Spelling consistency matters most on pages connected by hreflang, since a mismatched spelling between your ar tag's target and the actual page content can read as sloppy even though it doesn't break the tag technically. Review your spelling choices alongside the setup in hreflang for Arabic so both are decided together rather than by two different people at two different times.
It also matters during transcreation. A page rewritten quickly for Arabic search behavior can end up mixing spelling variants inconsistently within itself, simply because the writer typed naturally rather than checking against the target keyword. Our guide to translation vs transcreation is worth reading alongside this one if you're briefing that work for the first time.
Questions people also ask
Why does the same Arabic word have more than one correct spelling?
Because certain letters — the hamza seat on alif, the taa marbuta at the end of a word, alif maqsura versus a regular yaa — are written inconsistently in everyday typing even though formal rules exist. Both spellings are understood by readers and typed by real searchers.
Do I need a separate page for each spelling variant?
No. One page should target the primary spelling and naturally include the common variants in its body text, rather than splitting into near-duplicate pages that compete with each other.
Which spelling should I use in my title, URL and headings?
Use whichever variant your keyword research shows is searched most often for that specific term. It's usually, but not always, the more formal spelling — check the data rather than assuming.
Do keyword tools automatically combine spelling variants for me?
Rarely. Most report each spelling as a separate row with its own volume, so you need to identify and add matching variants together by hand before judging whether a topic is worth a page.
Sources
- Arabic (Unicode block U+0600–U+06FF) — The Unicode Consortium (checked 23 September 2026)
- Consolidate duplicate URLs — Google Search Central (checked 23 September 2026)
- Language tags in HTML and XML — W3C Internationalization (checked 23 September 2026)
Get your Arabic spelling variants mapped correctly
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Arabic SEO: the complete guide for 2026Arabic SEO is ranking pages written for Arabic searchers: research in Arabic, write natively, build a clean /ar/ section and earn Arabic links.
- Hreflang for Arabic: The Exact Tags to UseHow to set hreflang for Arabic pages: which language and region codes to use, where the tags go, and the mistakes that break them most often.
- Translation vs Transcreation for Arabic SEOTranslation and transcreation are different products with different prices. Here's when a straight translation is fine, and when Arabic pages need a rewrite.
- Arabic URLs vs Transliteration: Which to UseArabic-script slugs, transliterated slugs or English slugs on your Arabic pages — how each behaves in search, sharing and analytics, and how to pick one.