For years, schema markup was the SEO world’s quiet cheat code: paste in some JSON-LD, watch the star ratings and FAQ dropdowns light up your listing, and steal clicks from rivals who didn’t bother. Then 2025 happened. Google quietly retired seven structured data features, gutted FAQ and HowTo rich results for almost everyone, and the comforting old playbook stopped working overnight.
But here is what most people missed in the panic: schema didn’t die — it got promoted. In 2026, the same code that once decorated your search snippet has become the language AI engines use to decide whether your brand is trustworthy enough to cite at all. The businesses winning AI Overviews, ChatGPT answers and Gulf-wide local search aren’t the ones with the prettiest snippets anymore. They’re the ones whose content machines can actually understand. This guide shows you exactly how to be one of them — what schema markup really is, which types still earn their place, how to add and validate it without breaking anything, and how I use it on real client sites across Egypt, Saudi Arabia and the Gulf.
What schema markup actually is
Strip away the jargon and schema markup is a translation layer. Your page is written for humans — sentences, headings, images. A search engine sees text, but it has to guess what that text means. Is “Apple” the fruit or the company? Is “$49” a price, a discount, or a phone number? Is the person named at the top of the article the author, the subject, or a quoted source? Schema markup removes the guesswork by labelling your content in a vocabulary machines already understand.
That vocabulary is schema.org — a shared, collaborative standard founded by Google, Microsoft, Yahoo and Yandex. It defines roughly 800 different types of things you can describe, from an Article to a Product to an Event to a LocalBusiness, each with its own properties. Structured data is the broad concept of organising information this way; schema markup is the specific code you write, using the schema.org vocabulary, to do it. In everyday SEO conversation the two terms are used interchangeably, and that is fine — just know that schema markup is how you implement structured data in practice.
Schema markup is code you add to a webpage to help machines understand the meaning behind your content.
Schema markup is code that helps search engines understand the information on a page.
The crucial word in both definitions is meaning. Classic SEO is about words and links; schema is about entities and relationships. It lets you state, in a form a machine can’t misread, that this organisation is run by this person, who is an expert in these topics, who wrote this article, which is about this product, which has this price and this rating. That web of verified relationships is the foundation everything else in this guide builds on.
Why 2026 changed everything
If you learned schema two or three years ago, half of what you know is now wrong — not because the technique broke, but because Google changed what it shows. Two big moves reshaped the landscape, and you need to understand both before you write a single line of markup.
Google retired the display widgets
In June 2025, Google deprecated seven structured data types as part of what it called “simplifying the search results page.” It then continued the trend, curtailing FAQ and HowTo rich results so heavily that for most sites the familiar dropdowns simply vanished from normal listings. FAQ rich results now appear mainly for well-known government and health sites. Search Console reporting and API support for the deprecated types is being removed on a rolling basis through January 2026.
The seven retired types were niche: Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. Google’s own explanation was unsentimental.
Our analysis shows that they’re not commonly used in Search, and we found that these specific displays are no longer providing significant additional value for users.
Two things matter here. First, none of this hurt rankings — Google confirmed the changes were purely about the look of the results page, not about who ranks where. Second, the underlying schema is still valid. If you have FAQPage markup on your site, leave it; it remains useful for machine understanding even though the visual dropdown is gone for most queries. The mistake is to keep expecting the old widget, or worse, to keep stuffing pages with FAQ schema purely to chase a display feature that no longer exists.
Schema got promoted to a trust signal
While Google was tidying the visible SERP, the invisible half of search exploded. Google AI Overviews and AI Mode, ChatGPT, Perplexity and Gemini now answer a huge share of queries directly, and they lean heavily on structured data to do it. When an AI engine assembles an answer, it has to decide which sources to trust and cite. Clean, accurate schema — especially data about who you are and what you know — is one of the strongest signals it has that your content is verifiable and authoritative.
So the strategic value of schema flipped. It used to be a cosmetic layer that decorated your snippet. Now it is an entity-verification layer that helps machines decide whether you are a credible source at all. That is a promotion, not a demotion — and it is exactly why the brands treating schema as legacy decoration are quietly losing ground to the ones treating it as infrastructure. If you want the full picture of how this plays out, I go deeper in my guide on winning AI Overviews and in my technical SEO service.
Does schema markup actually help SEO?
This is the question every client asks, and the honest answer has two halves that both need saying.
Half one: schema is not a direct ranking factor. Google has stated this repeatedly and plainly. Adding schema markup will not, on its own, lift your position for a query. If a competitor outranks you, marking up your pages will not leapfrog them. Anyone selling schema as a magic ranking lever is selling you a myth.
Half two: schema is one of the highest-leverage indirect moves you can make. Here is why that is not a contradiction. Rich results — even the ones that survive in 2026, like product ratings, prices, and breadcrumbs — pull more clicks from the same position. The data is consistent: structured-data listings see click-through-rate improvements of roughly 20-35% over plain listings, and pages that earn rich results have been measured at around 35% higher CTR. More clicks at the same rank means more traffic, more engagement signals, and a stronger business — even though the markup itself never touched the ranking algorithm.
Schema markup won’t guarantee rankings or citations. But without it, your content is less likely to be understood, trusted, or surfaced.
That last line is the whole strategy in one sentence. Schema doesn’t push you up; it makes you eligible — eligible for rich results, eligible for AI citations, eligible to be understood correctly in the first place. And the case studies bear it out. When I rebuilt the technical foundation for Roseberry in Saudi Arabia — clean Organization and Product schema among many other fixes — the store climbed from roughly 25 impressions a day to 51.5M impressions and 545K clicks over sixteen months. Schema wasn’t the cause of that growth, but it was part of the platform that made the growth possible and legible to Google.
| Claim about schema | True? | What it really means |
|---|---|---|
| Schema directly raises your ranking | No | Google has confirmed it is not a ranking factor |
| Schema can lift click-through rate | Yes | Rich results earn roughly 20-35% more clicks at the same position |
| Schema helps AI engines cite you | Yes | Structured data verifies entities and claims for AI Overviews and chatbots |
| FAQ schema still triggers the SERP dropdown | Rarely | Curtailed in 2025; now mainly government and health sites |
| Schema guarantees a rich result | No | Eligibility only — Google still decides whether to show it |
JSON-LD vs Microdata vs RDFa
There are three technical formats for writing structured data, and in 2026 the choice is genuinely simple: use JSON-LD. It is the only format Google actively recommends, and the reasons are practical, not dogmatic.
JSON-LD (JavaScript Object Notation for Linked Data) sits in a single block in your page’s <head> or <body>, completely separate from your visible HTML. Microdata and RDFa, by contrast, weave their attributes into your HTML tags, wrapping every marked-up element. That difference sounds minor and is anything but.
| Format | Where it lives | Pros | Cons |
|---|---|---|---|
| JSON-LD | A self-contained script block, separate from content | Google-recommended; easy to template server-side at scale; clean; validates reliably | None significant for modern sites |
| Microdata | Inline attributes on your HTML elements | Works; older support | Tangled with markup; error-prone; painful to maintain |
| RDFa | Inline attributes (extends HTML5) | Flexible for linked data | Most verbose; hardest to author and debug |
To be eligible for rich result appearance in Google Search results, your structured data shouldn’t violate the content policies for Google Search.
Because JSON-LD lives apart from your content, you can template it once and inject it across thousands of pages — generating a Product block from your product database, or a BlogPosting block from your CMS, without touching a single line of visible markup. That is exactly how this very site does it, and it is why every serious technical SEO standardised on JSON-LD years ago. If your developer is still hand-weaving Microdata into product templates, that is technical debt worth retiring.
The five schema types that matter in 2026
There are hundreds of schema types, but for most businesses, five do almost all the real work. The discipline is to apply each one where the content genuinely matches it — never to scatter markup across pages just because you can. Mismatched schema (claiming a Product on a blog post, or Review on a page with no review) violates Google’s content policies and can disqualify you from rich results entirely.
1. Organization — your entity foundation
This is the most important and most neglected type. Organization schema, placed on your homepage and ideally referenced site-wide, tells search engines and AI exactly who you are: your legal name, logo, founder, social profiles, contact points, and — critically — your areas of expertise. It is the anchor of your entity SEO: the single, authoritative record that everything else attaches to. Get this right and AI engines have a clear, verifiable identity to cite. Skip it, and you are an anonymous string of text competing against brands the machines already trust.
2. Article / BlogPosting — for content
Every guide, news piece and blog post should carry Article or BlogPosting schema declaring the headline, author (linked to a real Person entity), publish and modified dates, and publisher. This is what lets a search engine attribute your expertise to a named human — central to E-E-A-T — and what helps AI engines understand that this is editorial content from a credentialed source. This article you are reading uses exactly this markup.
3. Product — for e-commerce
Product schema is where rich results still genuinely pay off. It carries name, description, image, brand, price, availability and — via AggregateRating and Review — star ratings. Those stars and prices survive in 2026 SERPs and reliably lift click-through. For any store, this is non-negotiable; it is a core part of how I approach e-commerce SEO. When I drove a niche store to #1 in Saudi Arabia in 166 days, clean Product and rating markup was part of making every listing as clickable as its ranking deserved.
4. LocalBusiness — for physical presence
If you serve customers in a place, LocalBusiness schema declares your name, address, geo-coordinates, opening hours, area served and phone. It is the structured backbone behind local pack visibility and, increasingly, behind AI assistants answering “best [service] near me” queries. For brands across Egypt and the Gulf, this is one of the most under-used levers I find — pair it with a well-optimised Google Business Profile and the two reinforce each other.
5. BreadcrumbList — for structure
BreadcrumbList schema describes where a page sits in your site hierarchy, and it produces the breadcrumb trail you see in many listings instead of a raw URL. It is small, it is cheap, and it both improves the snippet’s appearance and reinforces your site architecture for crawlers. There is almost no reason not to have it.
Schema markup for AI search and entity authority
This is the part of the guide that did not exist three years ago, and it is now the most important. AI Overviews, AI Mode, ChatGPT, Perplexity and Gemini do not rank ten blue links — they synthesise an answer and cite a handful of sources. Getting cited is the new winning, and structured data is one of the clearest ways to earn it.
The mechanism is trust through verification. When an AI engine drafts an answer, it needs to know which claims are reliable and which sources have genuine authority on the topic. Accurate Organization data tells it who you are. The knowsAbout property — a rising priority for 2026 — explicitly declares the topics your organisation or author is expert in, building a machine-readable map of your topical authority. When AI Mode is choosing whose words to cite for a query category, that declared-and-corroborated expertise is exactly the kind of signal it leans on.
This is entity SEO in its purest form: you are not optimising a page for a keyword, you are establishing a verified identity that knows things, so that machines reach for you when those things come up. The brands that win AI citations are rarely the ones with the cleverest copy. They are the ones whose identity, expertise and content relationships are unambiguous in code.
A word of caution that comes straight from Google: there is no special “AI schema.” You do not need exotic markup, llms.txt tricks, or AI-only structured data. What earns AI citations is the same accurate, policy-compliant schema that earns rich results, sitting on fast, crawlable, genuinely expert pages. Do the fundamentals exceptionally well and you are optimised for both classic search and AI answers at once.
How to add schema markup, step by step
Let me make this concrete. Here is the exact process I follow, regardless of platform.
Step 1 — Decide what each page truly is. Before any code, classify the page. Is it your homepage (Organization)? A blog post (BlogPosting)? A product (Product)? A location (LocalBusiness)? Schema must describe what is genuinely on the page. This single decision prevents the most common errors.
Step 2 — Generate the JSON-LD. You have three good options depending on scale:
- CMS plugin. On WordPress, a dedicated schema plugin (or a strong SEO plugin) can output clean JSON-LD automatically from your post and product data. This is the fastest route for most small and mid-size sites. I cover platform specifics in my WordPress SEO guide.
- A schema markup generator. For one-off pages, a reputable schema markup generator lets you fill in fields and copy out valid JSON-LD to paste into the page.
- Server-side templating. For stores and large sites, the professional approach is to template the JSON-LD against your database so every product, article or category page emits correct schema automatically. This is how serious sites scale to thousands of pages without manual work.
Step 3 — Place it in the page. Inject the JSON-LD block into the page’s HTML — conventionally in the <head>, though Google reads it in the <body> too. With a plugin or server-side template this happens automatically; for hand-coded pages you paste the script block in yourself.
Step 4 — Reference, don’t duplicate. Connect your entities with @id references so the author of an article links to a single Person entity and the publisher links to your one Organization. This avoids contradictory, duplicated identity data — a subtle but real source of confusion for both Google and AI.
Step 5 — Validate before you trust it. Never assume markup is correct because it looks right. Validation is step five, and it is non-negotiable — which is the next section.
Validate and audit at scale
Broken schema is worse than no schema — it wastes effort and can disqualify you from rich results. There are three layers of checking, and I use all three.
Single-page validation. Use Google’s Rich Results Test to confirm a specific URL is eligible for rich results and to see exactly which features it qualifies for. Pair it with the Schema Markup Validator (the schema.org tool, the successor to the old Structured Data Testing Tool) to check the markup against the full vocabulary, not just Google’s supported subset. Between them they catch the vast majority of syntax and eligibility errors on any given page.
Search Console. Google Search Console reports structured-data status across your site over time and flags errors on indexed pages — though remember that reporting for the deprecated types is being removed through January 2026, so don’t be alarmed when those specific reports disappear.
Site-wide crawling. Single-page tools are useless for a 5,000-page store. To catch errors at scale, crawl the whole site with a tool like Ahrefs Site Audit (or a comparable crawler) that surfaces every structured-data error and warning across every URL at once. This is how you find the one broken template silently corrupting schema on a thousand product pages.
| Tool | Best for | What it tells you |
|---|---|---|
| Rich Results Test (Google) | A single URL | Whether it’s eligible for rich results, and which ones |
| Schema Markup Validator (schema.org) | A single URL or snippet | Whether the markup is valid against the full vocabulary |
| Google Search Console | Site-wide, over time | Errors on indexed pages and rich-result performance |
| Ahrefs Site Audit (or similar) | The whole site at scale | Every structured-data error and warning across all URLs |
Schema for Egypt, Saudi Arabia and the Gulf
For businesses across Egypt, Saudi Arabia and the wider Gulf, schema markup is one of the most practical and under-exploited levers available — precisely because so few competitors do it well. And it works regardless of the rich-result types Google retired.
The priorities are clear. LocalBusiness and Organization schema with accurate name, address, area served and contact details help both Google and AI assistants understand and surface your business for local English-language searches across the region — the “best [service] in Riyadh” or “[product] store in Cairo” queries that increasingly get answered by AI. For e-commerce, Product schema with AggregateRating supports the rich results that still survive and the AI citations that are rising. None of this depends on the FAQ or HowTo dropdowns Google curtailed.
I have seen this compound in practice. Conscent grew from 61K to 1.2M impressions once the technical foundation, structured content and clean markup were in place. Oxford Egypt and other regional clients gained the same kind of legibility — the quiet advantage of being a site that machines can read precisely while competitors remain a blur of unlabelled text. In a market where most rivals have never touched structured data, doing it properly is a genuine edge. It is a core part of how I approach technical SEO and full-funnel SEO services for clients in the region.
The takeaway for the Gulf is the same as everywhere, only sharper: classic rich results are quieter than they were, but the deeper job of schema — making your business unmistakably understandable to search engines and AI — has never mattered more. The brands that win the next few years of English-language search across Egypt, Saudi and the Gulf will be the ones whose identity, locations and products are written in a language the machines can trust.
Frequently asked questions
What is schema markup, and how is it different from structured data? Schema markup is the code you add to a page using the schema.org vocabulary, while structured data is the broader concept of organising information in a machine-readable way. In practice the terms are used interchangeably: schema markup is the most common way to implement structured data, and Google recommends doing it with JSON-LD.
Does schema markup help SEO rankings? Schema markup is not a direct ranking factor. Google has repeatedly confirmed that adding it will not, on its own, move your position. Its value is indirect but real: it can earn rich results that lift click-through rates by roughly 20-35%, and in 2026 it helps AI systems verify, trust and cite your content — which is increasingly where visibility is won.
Which schema types still matter in 2026 after Google’s deprecations? Focus on Organization (your entity foundation), Article/BlogPosting, Product, LocalBusiness and BreadcrumbList. Google deprecated 7 niche types in 2025 (such as Vehicle Listing and Claim Review) and curtailed FAQ and HowTo rich results for most sites, so apply schema that matches genuine content intent rather than spreading it across every page.
Why did Google remove FAQ and HowTo rich results? Google said these displays were not widely used and no longer added significant value, so it simplified the results page. FAQ rich results now appear mainly for well-known government and health sites. The schema itself is still valid and useful for AI understanding — you just shouldn’t expect the old FAQ dropdown in normal listings.
Which format should I use — JSON-LD, Microdata or RDFa? Use JSON-LD. It is the only format Google recommends because it keeps the markup separate from your visible HTML, is easy to template and inject server-side at scale, and validates more reliably. Microdata and RDFa are more error-prone and harder to maintain.
How does schema markup help with AI search and AI Overviews?
AI systems like Google AI Overviews/AI Mode, ChatGPT, Perplexity and Gemini lean heavily on structured data to understand content, verify claims and establish entity relationships. Accurate schema — especially Organization data and the knowsAbout property — increases the probability of being cited in AI answers even when no traditional rich result is shown.
How do I add and validate schema markup on my site? If you use a CMS like WordPress, a schema plugin can add JSON-LD automatically; otherwise inject the JSON-LD into your page’s HTML. Validate a single page with Google’s Rich Results Test and the Schema Markup Validator, and audit the whole site with a crawler such as Ahrefs Site Audit to catch errors at scale.
Is schema markup worth it for local businesses in Saudi Arabia and the Gulf? Yes. LocalBusiness and Organization schema with accurate name, address, area served and contact details help Google and AI assistants understand and surface your business for local English-language searches across the Gulf, while Product and AggregateRating schema support e-commerce visibility — all without depending on the rich-result types Google retired.