On many Arabic sites, the words that appear in Google are the weakest words on the page: an English theme name, a repeated site slogan, or a title copied across fifty posts. This guide covers the three elements you control most directly, and the key idea is simple: write them for the reader, in the page’s own language, and let Google’s documented rules guide you rather than character counters.
What Google shows, and where it comes from
A search result has a title link (the clickable headline) and a snippet (the short text under it). Google’s title link documentation asks that every page have a title in the <title> element, and that the text be descriptive and concise. Google does not always use your title as written. When it generates a title link, it may draw on other sources on the page, including the main visual title, heading elements such as <h1>, and the content of og:title meta tags.
Snippets work in a similar way. Google says snippets are primarily created from the page content itself, and that it sometimes uses the meta description if that gives users a more accurate description of the page. So the meta description is a suggestion, not a command.
The title element on an Arabic page
Describe the page, briefly. A good title tells a searcher what the page is about before they click. Put the specific topic first and keep branding short.
Match the page’s language and script. Google’s title guidance asks site owners to keep the title in the same language and writing system as the page’s main content. An Arabic article gets an Arabic title. An English article gets an English title. This sounds obvious, yet untranslated themes break it all the time.
Avoid stuffing. Google’s wording is direct: it can help to have a few descriptive terms in the title, but there is no reason for the same words or phrases to appear several times.
An illustrative example, invented for this guide:
- Weak:
Home | My Blog | مدونتي | Blog | Arabic coffee - Better:
طريقة تحضير القهوة العربية في البيت خطوة بخطوة | مدونتي
Meta descriptions and headings
Google states: “There’s no limit on how long a meta description can be, but the snippet is truncated in Google Search results as needed.” That is why you will not find a character limit in this guide. Tools that show a counter are estimating display width; they are not quoting a Google rule. Write a unique description for each important page that summarises what the reader will find, in natural Arabic sentences rather than a list of terms.
For headings, the starter guide says that from a Google Search perspective it does not matter if you use them out of order. Headings exist to help readers scan the page. Use them to reflect the real structure of the article: one clear main heading, then sections, then subsections where they help. The number of H1 elements is not something to worry about for ranking.
Step by step
- Audit your templates first. Open three pages of different types (article, category, home) and read the
<title>in the page source. - Localize the theme. Make sure Arabic pages output Arabic site names, category labels and title separators.
- Shorten boilerplate. Move the site name to the end and keep it to a word or two.
- Rewrite titles for key pages. Start with the pages that already get impressions in Search Console.
- Write unique meta descriptions for the same key pages. Describe, do not list.
- Check headings. Confirm the main heading matches the topic and sections follow the article’s logic.
- Review results. Run a
site:search on your domain and look at how titles and snippets appear, then watch the Performance report over the following weeks.
A bilingual template example
A common setup puts Arabic content at /ar/ and English at /en/. A frequent bug is a single global title pattern like {post title} | TechBlog - Learn Tech Online. On Arabic pages, that English suffix becomes a large share of the title. The fix is a per-language pattern: Arabic pages use an Arabic site name and separator, English pages use the English version. Most multilingual setups in WordPress and custom CMS platforms let you define the site name per language.
Template checklist
| Check | How | Tool |
|---|---|---|
| Every page has a title | View source and find the title element | Browser view source |
| Title matches page language | Compare title script with body text | Browser and your CMS |
| Titles are unique | Sort page titles and look for repeats | Site crawler or CMS export |
| Branding is brief | Keep the site name to one short segment at the end | CMS title template |
| No repeated terms | Read the title aloud | Your own judgement |
| Meta descriptions are unique | Check important pages one by one | Your CMS SEO fields |
| Headings reflect structure | Outline the page from its headings only | Browser extension or source |
| Results look right | Search your domain and review titles and snippets | Google site: search and Search Console |
Common mistakes
- The same title on every page, or long boilerplate prefixes. Readers cannot tell your pages apart in results.
- English titles on Arabic pages because the theme or plugin was never localized.
- Stuffing keyword variants into the title. Google says repetition serves no purpose.
- Treating a tool’s character count as a Google rule. Google documents no length limit for meta descriptions, and it may rewrite a title regardless.
- Meta descriptions written as keyword lists. Google may ignore them, and readers will not click on them.
If you run an Arabic site, the first thing I would do today is open the title element of your three main templates. In my view, that single check catches more problems than any tool report.
Sources
- Google Search Central, influencing title links in search results, documentation page consulted 27 October 2025, https://developers.google.com/search/docs/appearance/title-link
- Google Search Central, controlling snippets and meta descriptions, documentation page consulted 27 October 2025, https://developers.google.com/search/docs/appearance/snippet
- Google Search Central, SEO starter guide, documentation page consulted 27 October 2025, https://developers.google.com/search/docs/fundamentals/seo-starter-guide