Hamza, Taa Marbuta and Alef: How Arabic Spelling Variants Split Saudi Search Demand (and What It Means for Google Ads)

About a third of Saudi car insurance searches skip the hamza. In Semrush’s September 2026 data, which we pulled on 1 October 2026, “car insurance” written ta’min sayyarat (alef with hamza) gets 22,200 monthly searches and tamin sayyarat, typed without the hamza (bare alef), gets 12,100: 35% of the pair. Google Ads treats misspellings as close variants, but negative keywords do not follow the same rule.

How much Saudi search demand is typed without the hamza?

It depends on the phrase. In our Semrush pull, 35% of combined car insurance searches drop the hamza, against 2.6% for the car rental head term. Yet the four highest-volume rental modifiers we pulled, such as “car rental office” (maktab tajir sayyarat, 27,100 searches), all appear in the hamza-free spelling.

The table below shows every spelling pair in our Saudi Arabia dataset where both forms were returned. All figures are Semrush estimates of average monthly searches and cost per click, not data from a live Google Ads account. Arabic-language queries are shown as English translations and transliterations.

The rental long tail tells a different story from its head term. The four hamza-free modifiers in our pull (office, offices, shop, companies) total 52,700 monthly searches, while the three hamza-spelled city terms total 10,900. Our export did not include the hamza versions of the office and shop phrases, so we cannot compare those pair by pair.

Arabic spelling variant pairs, with examples

Most Arabic spelling variants in search come from a few letter swaps that keyboards and habit make easy. The hamza drops off alef, waw and yaa, and the taa marbuta at a word’s end gets typed as haa. Final alef maqsura and yaa also swap. Each swap creates a second string for the same word.

Information-retrieval researchers have treated these swaps as one word for more than two decades. A 2002 University of Massachusetts paper normalized the alef forms to bare alef, final alef maqsura to yaa and final taa marbuta to haa before running Arabic retrieval tests (Larkey, Ballesteros and Connell, SIGIR 2002).

Rows marked “no pair in our pull” are there so you know what to check. We have no volume for them and publish none.

Is Semrush merging sharika and sharikah (“company”)?

We think the identical figures point to merged source data, and we cannot prove it. Both moving pairs, “company” spelled with taa marbuta (sharika) and with haa (sharikah), show exactly the same volume and the same CPC to the cent, yet different keyword difficulty scores. Two independently measured strings rarely match on two metrics at once.

The Dammam pair shows 14,800 searches and $3.41 for both spellings, with keyword difficulty of 35 and 33. The Riyadh pair shows 12,100 searches and $4.20 for both, with difficulty of 21 and 26. Semrush scores difficulty from the pages ranking for each keyword, which explains why it differs while volume and CPC do not.

Google’s own planning tool groups variants openly. Keyword Planner defines average monthly searches as searches for a keyword and its close variants (Google Ads Help, Keyword Planner forecasts). If a third-party tool draws on grouped data, two spellings can inherit one number.

What we cannot tell you is how the real 14,800 splits between sharika and sharikah. Read the pair as one demand pool of unknown division, and never add the two figures together in a forecast. The insurance pair, with different volumes and CPCs, looks separately measured.

Does Google Ads match Arabic spelling variants automatically?

Partly, by Google’s own description. Google lists misspellings, singular and plural forms, stemmings, abbreviations and accents as close variants for exact and phrase match in all languages, and every match type is eligible with no opt-out. Google does not document whether a dropped hamza or a taa marbuta typed as haa counts as a misspelling.

The definition sits in Google’s close variants page (Google Ads Help, keyword close variants). The same page names Arabic among the languages where implied words count as close variants for exact match. It gives no Arabic spelling examples.

So the honest position is this. An exact match keyword [ta’min sayyarat] (“car insurance” with the hamza) is designed to reach tamin sayyarat too, but only your search terms report proves it in your account. Check the report before you assume coverage.

Adding the second spelling as its own keyword does not make you bid against yourself, because Google enters only one of your similar keywords in each auction. It does give you a separate row for spend, conversions and cost per lead, which is what you need when 35% of a phrase’s demand arrives in the second spelling.

If you would rather have someone else read those reports, ask our paid search team to audit your Arabic search terms.

Negative keywords: where spelling variants bite

Negative keywords are where spelling variants cause real waste. Google states that negative keywords do not match close variants, so a negative for one spelling is not guaranteed to block the other. Google’s own example treats sidewalk cafe and sidewalk café as two different negative keywords. Add every spelling you want blocked.

Google’s negative keyword page contains a tension worth knowing (Google Ads Help, negative keywords). It says negatives automatically account for casing and misspellings. It also says negatives do not match close variants, and that you must add synonyms and plural forms yourself.

For Arabic, nobody outside Google knows which side of that line a missing hamza falls on. The cheap fix is to remove the question. If you block the Arabic name of the Saudi Bar Association (al-hay’a al-sa’udiyya lil-muhamin, with taa marbuta) because people searching for the Saudi Bar Association are not hiring a lawyer, add the haa spelling (al-hay’ah al-sa’udiyyah lil-muhamin) as well.

Apply the same rule to job-seeker, free and DIY terms in your sector. One extra line in a negative list costs nothing; one unblocked spelling on a $4.20 moving keyword costs real money every day it runs.

Arabic ad copy: character limits and spelling choice

Arabic ad copy gets the standard responsive search ad limits: 30 characters per headline, 90 per description and 15 per path field. Google counts double width only for Korean, Japanese and Chinese, and Arabic is not on that list. A hamza or a taa marbuta therefore costs the same single character as the letter it replaces.

Those limits come from Google’s responsive search ad documentation (Google Ads Help, responsive search ads). The same page notes that ad text can appear in bold when it matches or closely matches the search, so standard spelling does not forfeit the visual match.

Language now matters more in setup. Starting September 2026, Google is removing the campaign language setting for Search campaigns and matching ads on the language of the ad itself (Google Ads Help, language targeting). Arabic queries need Arabic ads, in every ad group that targets them.

We write ad copy in standard spelling. A misspelled headline saves no characters and looks careless, which costs trust in regulated sectors like insurance, health and law.

Landing pages: spelling for Quality Score and SEO

Write landing pages in standard spelling, and let the typed variant appear only where it reads naturally. Landing page experience is one input to ad quality, and Google judges relevance by meaning as well as by exact strings. For organic search, the practical test is to compare the results pages for both spellings.

Run that test for your three biggest phrases. If the top results for ta’min sayyarat and tamin sayyarat are largely the same pages, Google is treating them as one query, and one page serves both. If they differ, the variant has its own results page, and your page needs that spelling in a heading or FAQ to compete.

Never build one page per spelling. It splits links and content between near-duplicates, and it creates exactly the thin pages Arabic search already suffers from. Our guide to GEO for Arabic content covers how AI answer engines read the same pages, and our research on Arabic AI citations shows which Arabic sources they quote.

Spelling discipline at this scale is work we have done organically. For Planet VPN’s Arabic site, VOCTOS grew ranked Arabic keywords to 8,800, up 85.7%, with 102,800 monthly organic clicks in September 2025.

The checklist

Use this checklist on any Arabic Google Ads account targeting Saudi Arabia or the Gulf. It covers keywords, negatives, ad copy and landing pages in that order, because that is the order in which spelling errors cost money. Each step uses only Google’s documented behaviour and your own account data.

1. Pull both spellings. For each head term, check hamza, taa marbuta/haa and alef maqsura/yaa forms in Keyword Planner and in your third-party tool. Identical volume and CPC means one merged figure.
2. Add separate exact-match keywords for variants with their own demand. tamin sayyarat at 12,100 searches earns its own row; a merged pair does not.
3. Read the search terms report weekly for the first month. Confirm which spelling triggered which keyword before trusting close variants.
4. Write every negative in every spelling. Cover alef with hamza/bare alef, taa marbuta/haa and alef maqsura/yaa forms, because negatives skip close variants.
5. Write ads in standard spelling, in Arabic, for Arabic queries. Count characters against the 30, 90 and 15 limits.
6. Keep one landing page per intent. Use standard spelling, and add the typed variant only where a real user question contains it.
7. Compare the results pages for both spellings. Identical results mean one query to Google; different results mean the variant needs a visible place on your page.

Our read

Treat spelling variants as one demand pool for strategy and two rows for measurement. The customer typing tamin wants the same policy as the one typing ta’min. What changes is your visibility into cost, conversions and wasted spend, and the negatives are where that visibility pays off fastest.

We disagree with the habit of copying misspellings into ad text to look closer to the query. Google already bolds close matches, the character count is the same, and standard spelling reads as competent to a Saudi buyer. Put the variant in your keyword and negative lists, where nobody sees it.

We also discount any keyword tool figure that shows two spellings with identical numbers. Our Saudi and UAE CPC dataset contains two such pairs, and we flag them there rather than add them up.

FAQ

Do I need to add both ta’min and tamin as keywords?

You do not need to for matching, because Google treats misspellings as close variants. You should when the variant has real demand, as tamin sayyarat (car insurance without the hamza) does with 12,100 monthly Semrush searches in September 2026. A separate keyword gives you separate cost, conversion and search term data for that spelling.

Will my negative keyword block the misspelled Arabic version too?

Do not count on it. Google says negative keywords do not match close variants, and its own help page treats cafe and café as two separate negatives. It also says negatives handle misspellings, without defining Arabic cases. Add every spelling you want blocked, including hamza and taa marbuta/haa forms.

Should my Arabic Google ads use the spelling people actually type?

No. Write ads in standard spelling. Arabic letters with and without hamza count as one character each, so a misspelling saves no space, and Google already bolds text that closely matches the search. Keep the typed variants in your keyword and negative lists instead of in visible ad text.

Why does Semrush show the same volume for sharika and sharikah?

We cannot confirm Semrush’s method. Both moving pairs in our September 2026 pull share identical volume and CPC but different keyword difficulty, which fits grouped source data. Google’s Keyword Planner openly counts a keyword with its close variants. Treat such pairs as one demand pool and never add them.

Does Google SEO treat hamza and no-hamza spellings as the same word?

Google does not publish its Arabic spelling normalization, so test it. Search both spellings from Saudi Arabia and compare the top results. If they are largely identical, one page serves both. If they differ, give the variant a natural place on your page, such as a heading or an FAQ question.

Is Arabic spelling a keyword problem or a measurement problem?

For most Saudi accounts, spelling is a measurement problem first. Google already matches many variants, so the customer usually reaches you. What goes wrong is that you cannot see which spelling cost what, and a negative written in one spelling leaves the other open.

So there are two paths. If your search terms report already shows hamza-free queries arriving under your keywords, spend your time on negatives in every spelling and on separate rows for high-demand variants. If it does not, add the variant keywords first, then rebuild your negatives.

Not sure what your account is matching? Send us one month of search terms, and we will mark every Arabic spelling you are paying for or missing.