Technical
Schema for Arabic websites: what helps and what is decoration
Ilyes Massoudi6 min readThe short answer
Structured data, or schema, is markup in a page's code that tells the search engine what the page contains in a language a computer understands: this is a local business with its address and phone, this is a product with its price, this is an article with its author and date, these are questions and answers. It does not raise rankings directly, but it qualifies your page for rich results such as stars, prices and breadcrumbs beneath your listing, and helps search and answer engines understand your entity. Four types help most Gulf sites: LocalBusiness, Product, Article and BreadcrumbList. Write it in Arabic on the Arabic page, in JSON-LD, and test it in the Rich Results Test.
What schema actually does
A search engine reads your page as text and guesses what is in it. Structured data ends the guessing: a small block in the code states, in a standard format, that this page is a dental clinic in Riyadh with this address, this phone and these hours; or that this is a product at this price in stock now; or that this is an article written by this person on this date.
What you get in return is three things, in this order of importance:
- Eligibility for rich results. Star ratings, prices, availability, product images and breadcrumbs beneath your Google listing. They raise click-through rate without any change in ranking.
- Entity understanding. Google and answer engines connect your business name, website, profile and accounts into one entity, which helps knowledge panels and AI answers.
- Clarity for crawlers. The page type is declared, not inferred.
What you do not get: a higher ranking directly. Schema does not compensate for weak content.
The four types that help most Gulf sites
| Type | For whom | What appears in results | Note |
|---|---|---|---|
| LocalBusiness | Any business with a location or service area | Name, address, phone, hours | Use the precise subtype: Dentist, Restaurant, RealEstateAgent |
| Product with Offer | Stores | Price, availability, rating | Exact price and currency, availability kept current |
| Article | Blogs and guides | Author, date, image | Links the author to one stable Person entity |
| BreadcrumbList | Everyone | The page path instead of the URL | Simple and visibly effective |
Add Organization or Person once at site level, with a stable identifier every page references. That is what makes your business one entity rather than a repeated name.
What has lost its effect
FAQPage. It used to show questions beneath the listing and expand it. Since 2023 Google restricts that display to a limited set of government and health sites. It still helps page understanding and does no harm, but pay nobody for it as a way to expand your listing.
HowTo. Removed from rich results on mobile and desktop. Do not invest effort in it.
Self-serving ratings. Rating schema you write about your own business on your homepage violates Google’s guidelines and can trigger a manual action. Ratings belong on specific products or services from real customers.
How to write it in Arabic
Rule one: text values in the language of the page. The Arabic page carries the business name, description and address in Arabic; the English page in English. The common mistake is copying the English block onto the Arabic page unchanged.
Rule two: JSON-LD format in the page head or at its end, which Google recommends, and which is easier to maintain than markup embedded in elements.
A short example for a local business on an Arabic page:
{
"@context": "https://schema.org",
"@type": "Dentist",
"@id": "https://example.com/#business",
"name": "عيادة النور لطب الأسنان",
"address": {
"@type": "PostalAddress",
"streetAddress": "طريق الملك فهد",
"addressLocality": "الرياض",
"addressCountry": "SA"
},
"telephone": "+966500000000",
"openingHours": "Sa-Th 09:00-21:00",
"url": "https://example.com/ar/"
}Rule three: a stable @id for the business and the person, referenced by every page rather than redefined. One entity, not twenty copies.
How to validate for free
- Google’s Rich Results Test: paste the URL and look at the detected types, errors and warnings. Errors block the rich result; warnings do not.
- The Schema.org validator for any type Google’s test does not display.
- The Enhancements reports in Search Console after some weeks: they show eligible pages and errors per type.
The mistakes that leave schema without effect
- English markup on an Arabic page, or the reverse.
- An address or phone in the markup that differs from what is visible on the page and in the Business Profile. Consistency is a condition.
- A generic “Organization” type for a business with a precise subtype.
- A price in the markup that differs from the price on the page, or stale availability.
- Two conflicting blocks from two WordPress plugins.
- Schema for content that is not actually on the page, such as questions the reader cannot see. An explicit violation.
This site as a sample
View the source of any page on this site and search for application/ld+json: you will find one Person entity with a stable identifier that every article references, an Organization, a Service, and breadcrumbs, in Arabic on the Arabic pages and English on the English ones. In the Digital Presence Audit the technical diagnosis covers the structured data that is present, missing and conflicting, with ready snippets for the developer.