What Is Schema Markup and Why Your Website Needs It

On 7 May 2026, Google switched off FAQ rich results. The expandable question and answer dropdowns that used to sit under search listings stopped appearing, and within days a lot of business owners were told that schema markup was finished. That advice is wrong, and following it will quietly cost you visibility. Schema markup matters more in 2026 than it did three years ago, just for a completely different reason. Here is what it is in plain language, what actually changed this year, which types your website genuinely needs, and how to add and check them without hiring a developer.

What Schema Markup Actually Is

Schema markup is a block of code you add to a web page that tells search engines and AI systems what the page means, not just what it says.

Take one line from a contact page: Meridian Dental Clinic, +971 4 555 1234, open Sunday to Thursday, 9am to 6pm. You read that and instantly know which part is the business name, which is the phone number, and which is the opening hours. A machine has to work it out. Usually it works it out correctly. Sometimes it does not, and sometimes it does not bother. Schema markup removes the guessing by labelling each piece explicitly: this string is the name, this one is the telephone, these are the opening hours.

Three words get used interchangeably and they should not be. Schema.org is the shared vocabulary, the dictionary of agreed labels. Structured data is your actual information written in that vocabulary. Rich results are what Google chooses to display when it reads your structured data, such as star ratings, prices, breadcrumb trails or event dates. You control the first two. Google decides the third, and it changes its mind regularly.

The format Google recommends is JSON-LD, which sits in your page as a standalone script tag. It is completely invisible to visitors. Nothing about your design changes. It is a separate layer of meaning attached to a page that already exists.

Why Schema Suddenly Matters More, Not Less

The confusion is understandable, because Google has spent three years switching things off. The short version of what has actually gone:

• How-to rich results were deprecated on desktop in September 2023 and no longer appear anywhere. The documentation has been removed from Google Search Central entirely.
• In June 2025, Google retired seven types in one pass: Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. Book Actions was quietly reinstated in November 2025 because a Search feature still uses it.
• In January 2026, Practice Problem structured data lost its Search Console reporting, Rich Results Test support and search appearance filter.
• On 7 May 2026, FAQ rich results stopped appearing. The Search Console report and Rich Results Test support went in June 2026, and Search Console API support ends in August 2026.

If you have been pulling FAQ rich result impressions into a monthly report, export that history before the API cutoff or your baseline will return empty values and nobody will know why.

Read that list quickly and it looks like a retreat. It is not. Google Search Central confirmed in its own November 2025 announcement that structured data support continues, and John Mueller has pointed out that markup types have always come and gone. What is being removed are visual features that were rarely used or easy to abuse. What is being kept is everything that maps to a real business.

Two more things worth being precise about. FAQPage is not a deprecated Schema.org type. The markup is still valid, it will not throw errors, and Google has said unused structured data does not cause problems in Search. What ended was the SERP feature, not the vocabulary. And none of these removals touched rankings. Your position did not change because a dropdown disappeared.

The interesting change happened alongside the March 2026 core update, and it got far less attention. Google's AI Mode, powered by Gemini, began treating structured data as a way to verify claims, confirm which entity a page belongs to, and assess whether a source can be trusted, rather than as a trigger for something visual. Accurate schema that matches your visible content raises the odds of being cited inside an AI answer even when no rich result shows at all.

That matters because of where citations are now coming from. An Ahrefs study of roughly 863,000 search results in February 2026 found that only 38 percent of pages cited in Google AI Overviews also rank in the top 10 of normal search results, down from 76 percent in mid-2025. Being cited and being ranked have started to come apart. Whatever helps a machine understand and trust a page is worth more than it was.

What Schema Markup Will Not Do For You

Worth saying clearly before anyone spends a weekend on this. Schema markup is not a direct ranking factor. Adding it does not push you up the results page on its own.

• It will not rescue thin or unhelpful content. A well-labelled bad page is still a bad page.
• It will not create rich results for types Google has switched off. No amount of FAQ markup brings the dropdowns back.
• It will not help if the markup contradicts what is on the page. Google reads that as a mismatch, and in the case of reviews and ratings, it can trigger a manual action.
• It will not replace a Google Business Profile for local visibility. LocalBusiness schema supports your profile, it does not stand in for it.

What it does do is make you easier to understand, easier to display well, and easier to trust. Those are compounding advantages, not overnight ones.

The Schema Types Most Business Websites Actually Need

Ignore the full Schema.org vocabulary. It runs to hundreds of types and almost none of them apply to you. For a normal business site, whether you run a clinic, a law firm, a logistics company, a salon or a manufacturing operation, this is the whole list in the order we would build it.

1. Organization. Your identity block. Legal name, website, logo, address, phone, and a sameAs list pointing at your LinkedIn, Instagram, Google Business Profile and any other verified profile. This is the single most valuable piece of schema on most sites, because it is how machines connect the scattered mentions of your business into one entity. Add it once, sitewide.
2. LocalBusiness. Use this if customers can visit you or if you serve a defined area. It carries address, geo coordinates, opening hours and price range. Pick the most specific subtype that fits, such as Dentist, LegalService or HomeAndConstructionBusiness, rather than the generic parent.
3. BreadcrumbList. Small, boring, still supported, and it shows in search results as a readable path instead of a raw URL. If your site has any depth of navigation, this is a ten minute job with real payoff.
4. Product with Offer and AggregateRating, if you sell anything with a price online. This is where star ratings, price and stock status come from. Partial implementation gets you nothing, so complete it properly or leave it out.
5. Service, if you sell work rather than products. It will not produce a rich result, but it makes each service page unambiguous about what you do and where you do it, which is exactly the comprehension layer AI systems lean on.
6. Article or BlogPosting with a real named Person as author, for every post on your blog. Headline, publish date, modified date, author, publisher. An anonymous byline reads as low confidence to both ranking and citation systems now, and this is where the author gets attached.
7. Event and JobPosting, only if you genuinely run events or hire through your site. Both still produce rich results and both are easy to get wrong when the underlying content is thin.

The one rule that beats every checklist

Only mark up information that is genuinely visible on the page. Almost every serious schema problem traces back to breaking this rule: ratings that appear nowhere, prices that do not exist, opening hours copied from a template. If a visitor cannot see it, do not label it.

How to Add Schema Markup Without a Developer

For most businesses this is a one-afternoon job, not a project.

1. On WordPress, install Rank Math or Yoast. Both generate Organization, LocalBusiness, BreadcrumbList and Article schema from settings you fill in once. Fill them in properly, including the social profile URLs, because that is the sameAs list. If you run WooCommerce, Product schema is generated for you from your product data.
2. On Shopify, your theme almost certainly outputs Product schema already. Do not add a second layer through an app until you have checked, because duplicate Product blocks confuse more than they help.
3. On Framer, Webflow, Wix or a custom build, you paste a JSON-LD script into the head or the custom code section. Sitewide code for Organization, per-page code for everything else.
4. Whatever the platform, do Organization first and get it exactly right. Then breadcrumbs. Then Article on the blog. Then Product or Service. Working in that order means the identity layer is solid before you build anything on top of it.

How to Check That It Is Actually Working

Adding schema and never verifying it is how sites end up with three years of broken markup. Four checks, in order:

1. Run the page through Google's Rich Results Test. This tells you what Google can read and whether you qualify for any rich result. It only covers types Google supports, which is the point.
2. Run the same page through the Schema Markup Validator at validator.schema.org. This checks your markup against the full vocabulary, including types Google does not report on, such as Service. Use both, because they answer different questions.
3. Open Search Console and check the enhancement reports under Experience and Enhancements. Errors and warnings appear here across your whole site, not one page at a time.
4. Wait four to six weeks before judging the impact. Google recrawls and recaches pages on its own schedule, and reading results after a week tells you nothing.

Five Mistakes That Show Up Again and Again

We have worked with over 100 businesses across the UAE, the GCC and the USA since 2021. The same handful of structured data problems come up constantly.

• Two or three competing Organization blocks. The theme outputs one, a plugin outputs another, and somebody pasted a third into the header years ago. Pick one source of truth and delete the rest.
• Review or rating markup for reviews that appear nowhere on the page. This is the fastest route to a manual action of anything on this list.
• Template placeholders left in place. Real sites are running live with a sample company name, a demo logo URL and an address in another country, because nobody opened the plugin settings after install.
• Business details that drift. The schema says one phone number, the footer says another, the Google Business Profile says a third. Every mismatch weakens the entity.
• Still planning around FAQ and How-to rich results. Keep the FAQ content if it genuinely answers what customers ask, because it is useful to readers and to AI systems pulling short answers. Just stop treating the markup as a way to win SERP space that no longer exists.

Quick Answers

Does schema markup improve my Google rankings?

Not directly. It improves how your result is displayed and how accurately search engines and AI systems understand your business. Those effects show up as click-through rate, citation rate and better matching to relevant searches, not as a position jump on its own.

Should I remove my FAQ schema now that the rich result is gone?

There is no urgency. FAQPage is still a valid Schema.org type and Google has confirmed unused structured data does not cause problems. Clean it up during your next maintenance cycle, and stop adding it to service or product pages purely to capture search real estate that no longer exists.

How long does it take to add schema to a normal business website?

On WordPress with a proper SEO plugin, an afternoon covers Organization, LocalBusiness, breadcrumbs and Article. A custom-coded site with product pages and multiple locations is a few days of careful work. Auditing and fixing an existing site with years of accumulated markup usually takes longer than starting from scratch.

Is schema markup worth it for a small business with 10 pages?

Yes, and arguably more so. A ten page site has fewer signals for a search engine to work with, so the ones you do give it carry more weight. Organization plus LocalBusiness on a small site is one of the cheapest pieces of SEO work available.

Schema markup was never really about the star ratings. It was always about making your business legible to machines that have to decide, in a fraction of a second, whether you are the right answer to somebody's question. That decision used to happen in a ranked list. Increasingly it happens inside a written answer where only a handful of sources get named. Clean, honest structured data is one of the few things you fully control on that side of the equation. It costs very little and it stops being optional a little more every year.