Structured data is one of those topics where Arabic site owners get two kinds of advice: “add every schema type you can find” or “don’t bother”. Google’s own documentation sits somewhere more useful than both, and it is clear on one point above all: correct markup makes a page eligible for rich results, but Google does not promise to show them. This guide covers what to add, how to write it with Arabic text, and what to stop spending time on.
The problem: markup treated as a ranking trick
Structured data is a standard way to describe what a page contains: that it is an article with an author and a date, a product with a price, or a shop with an address and opening hours. Google reads it to understand the page and, for supported features, to decide whether it can show a richer result.
What it is not, in my reading of the documentation, is a shortcut to higher positions. Google states plainly: “Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly.” Treat markup as a way to describe your page accurately, not as a ranking lever.
Google accepts three formats: “JSON-LD, Microdata, RDFa”. Its recommendation is also direct: “In general, Google recommends using JSON-LD for structured data if your site’s setup allows it”. JSON-LD sits in a script block, separate from your visible HTML, which makes it far easier to maintain on an RTL theme where you do not want to touch the layout markup.
Adding structured data, step by step
- List your page types. A typical Arabic publisher has articles, category pages and an about page. A shop adds product pages and maybe a physical location. Types worth considering include Article, Product, LocalBusiness, BreadcrumbList and Organization. Pick only the ones that describe what your pages really are.
- Choose JSON-LD. If your CMS or plugin already outputs JSON-LD, check what it produces before adding a second block by hand.
- Put the markup on the page it describes. Google’s policy: “Put the structured data on the page that it describes, unless specified otherwise by the documentation.” Product markup belongs on the product page, not on the homepage.
- Mark up only what readers can see. “Don’t mark up content that is not visible to readers of the page.” If the author name is in the JSON-LD, it should appear on the page too.
- Save files as UTF-8 so Arabic strings are stored correctly, and keep the Arabic values identical to the visible text.
- Validate each template with the Rich Results Test before rollout.
- Monitor the rich result reports in Search Console after launch, and recheck whenever you change themes or plugins.
- Keep mobile and desktop equal. Google asks that mobile and desktop sites have the same structured data, so a separate mobile template needs the same blocks.
An Arabic article example
Here is a minimal Article sample for an Arabic post. The headline and author match what the reader sees, and the URL uses percent encoding, which is how non-ASCII characters are written in links.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "دليل البيانات المنظمة للمواقع العربية",
"inLanguage": "ar",
"datePublished": "2026-06-11",
"author": {
"@type": "Person",
"name": "إيهاب"
},
"mainEntityOfPage": "https://example.com/ar/%D8%AF%D9%84%D9%8A%D9%84-%D8%A7%D9%84%D8%A8%D9%8A%D8%A7%D9%86%D8%A7%D8%AA-%D8%A7%D9%84%D9%85%D9%86%D8%B8%D9%85%D8%A9"
}
On a bilingual site, the English sibling gets its own block with its own English headline and its own URL. What caught my attention when auditing bilingual themes is how often the English block is simply copied onto the Arabic page, so the markup describes a headline the Arabic reader never sees. That breaks the visibility rule above.
A note on FAQ markup: on 8 May 2026, Google’s documentation changelog recorded that the FAQ rich result is being deprecated. As of this writing, I would not add FAQ markup in the hope of getting FAQ rich results. If your FAQ section helps readers, keep the content on the page; just don’t plan around a rich result that Google is retiring. Check the changelog for any further details Google publishes.
Rollout checklist
| Check | How | Tool |
|---|---|---|
| Format is JSON-LD | View the page source and find the script block | Browser view source |
| Markup matches visible text | Compare headline, author and prices with the page | Manual review |
| Markup is on the right page | Confirm each type describes the page it sits on | Manual review |
| Arabic text displays correctly | Confirm UTF-8 and read the parsed values | Rich Results Test |
| No errors in templates | Test one URL per template | Rich Results Test |
| Mobile has the same markup | Inspect the live URL with the smartphone crawler | URL Inspection in Search Console |
| Ongoing health | Review rich result reports monthly | Search Console |
| No deprecated types in focus | Read recent entries | Search Central documentation changelog |
Common mistakes
- Marking up hidden or invented content. Reviews that don’t exist, ratings that don’t appear on the page, or text only present in the JSON-LD. Beyond breaking the guidelines, this is where manual actions come from. Google explains that “A structured data manual action means that a page loses eligibility for appearance as a rich result.”
- Expecting markup to guarantee rich results. Valid markup is a prerequisite, not a promise. Google says so directly.
- Keeping effort on deprecated types. Time spent polishing FAQ markup for rich results is better spent on Article or Product markup that still has a supported feature.
- Mobile and desktop out of sync. A separate mobile template missing the JSON-LD means the version Google indexes may carry no markup at all.
- Two plugins, two blocks. An SEO plugin and a theme both outputting Article markup with different dates or authors confuses the picture. Keep one source.
My advice is to start small: one correct Article or Product template, validated and monitored, beats ten half-filled types. Structured data rewards accuracy far more than volume.
Sources
- Google Search Central, introduction to structured data markup in Google Search, documentation page consulted 11 June 2026, https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
- Google Search Central, general structured data guidelines, documentation page consulted 11 June 2026, https://developers.google.com/search/docs/appearance/structured-data/sd-policies
- Google Search Central, latest documentation updates (changelog entry of 8 May 2026 on the FAQ rich result), consulted 11 June 2026, https://developers.google.com/search/updates
- Google Search Central, mobile-first indexing best practices, documentation page consulted 11 June 2026, https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing