AI Search8 November 20265 min read

Schema markup for AI search: what helps and what's hype

Google says AI Overviews need no special schema. Which markup is still worth adding for a UAE business, and which AI-schema pitches to push back on.

The short answer

Schema markup labels facts already on your page so software can read them without guessing: who you are, where you are, what a page says and when it changed. Google's documentation says no special schema is needed to appear in AI Overviews or AI Mode. Add the basics because they're cheap and accurate, and be wary of anyone selling schema as an AI ranking lever.

Google's documentation on its AI features says there are no extra requirements for appearing in AI Overviews or AI Mode beyond being indexed and eligible to show with a snippet, and it says no special schema is needed. So a quote that sells schema as the way into Google's AI answers is selling something Google hasn't said. Schema still earns its place, for a narrower reason: it states your facts in a form software can read without guessing.

What does schema markup do?

Schema markup labels facts that are already visible on the page, using the shared vocabulary at schema.org. A paragraph saying 'open Monday to Saturday, nine to six' makes sense to a person. The same fact in structured data is a fixed field a crawler can read without interpreting prose, which matters most for the facts that are expensive to get wrong: address, hours, phone number and who you are.

What markup can't do is create a fact the page doesn't state, or rescue a weak page. Whether any assistant other than Google reads your markup when it writes an answer isn't documented in the sources we checked, so a claim that markup 'feeds' ChatGPT or Perplexity is unproven. Judge it as housekeeping that keeps your facts consistent, which is where it's easiest to defend.

Which schema types are worth adding?

Organisation and LocalBusiness belong on almost any business site, Article and DefinedTerm depend on what you publish, and Product matters if you sell online.

What each type states, and what usually goes wrong
Type	What it states	Who needs it	The usual mistake
Organisation (schema.org's organisation type)	Legal name, brand name, logo, website, phone and links to your official profiles through the sameAs field	Every business, once, on the home page	Retyping a slightly different version of the name on every page
LocalBusiness, or a subtype such as Dentist or Restaurant	Address, phone, opening hours and the area you serve	Any business with a place customers visit or a defined service area	One block for six branches, or a template's Monday to Friday hours on a business that trades on Saturday
Article	Headline, publisher, date published and date updated	Anyone publishing guides or news	Changing the updated date when nothing was updated
DefinedTerm	A term, its definition and the glossary it belongs to	Sites that run a glossary	Marking up one-line stubs that define nothing
Product and Offer	Name, price, currency and availability	Online stores	A price in the markup that differs from the price on the page

Notice what's missing: no type is named after AI. The vocabulary is the one search engines have used for years, so an AI-specific schema pitch has to be selling these same fields under a new label, or something nobody has documented.

The hours field deserves care in the UAE. The federal government's weekend has been Saturday and Sunday, with a half day on Friday, since 1 January 2022, but The National's report of the change says private companies can set their own working week. Copy your hours from your own door, including any Friday break and your Ramadan timetable, not from a template or a government calendar.

Does FAQ schema still do anything?

FAQ markup no longer earns an ordinary business site anything visible in Google's results. Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites, so the markup won't give your site the expandable answers under a search listing, and nobody should promise it.

That change concerned how a result is displayed. It said nothing about whether questions and answers on your page are useful, and they are, to readers. If your CMS produces FAQ markup automatically, leave it on. If a quote lists it as a paid deliverable, skip it and spend the money on better answers: the post on writing FAQs that AI assistants quote covers the writing.

How do you add schema without making a mess?

Six steps take a site from no markup to markup that somebody maintains.

01Mark up only what a visitor can read on the page. If a fact isn't visible there, it doesn't go in the markup.
02Define the organisation once, with a fixed identifier, and refer to it from every other block instead of retyping it.
03Put your legal name in the legal name field, your trading name in the name field and your Arabic name in the alternate name field, spelled the way every profile spells it.
04Give each branch its own local business block, with its own address, phone number and hours.
05Test with Google's Rich Results Test and the Schema Markup Validator, then test again after every site change.
06Name one owner. When a phone number or a Ramadan timetable changes, the markup changes the same day.

The third step ties schema to your wider identity work. The post on entity SEO explains why the same name has to appear in the same form everywhere, and the technical SEO checklist shows where markup sits among the other fixes.

Which AI schema pitches should you push back on?

Five are worth refusing, or at least questioning hard.

'Schema for AI Overviews' as a line item. Google says no special schema is needed to appear in them.
A monthly schema retainer. Markup is set up once and changes when your facts change, so ask what exactly will be different each month.
An llms.txt file bundled in as AI optimisation. Google's guide to generative AI features calls new AI text files such as llms.txt unnecessary, and the llms.txt guide covers what the file is and isn't.
Rewriting your pages into tiny fragments so they can be lifted out. The same Google guide says content doesn't have to be broken into tiny pieces.
Review stars, awards or ratings added to markup when the page doesn't show them. That's markup describing things a visitor can't see, and it's the one schema habit worth refusing outright.

This site marks up its organisation, articles, FAQs and glossary terms as part of our SEO work, and we can't show you that any of it changes what an assistant says. We do it because it's cheap and because writing it forces the business facts to agree with each other.

Ask any provider one question before you pay for schema: what does the markup say that the page doesn't? If the answer is anything at all, the proposal is the problem.

Questions people ask

01Does schema markup help with AI search?

On Google's own AI features, Google says no special schema is needed. Its documentation lists no extra requirements beyond being indexed and eligible to show with a snippet. Markup still helps search engines read your facts, so add the basics, but nobody can honestly sell it as the way into AI Overviews or AI Mode.

02Which schema types should a UAE business add first?

Start with organisation markup once on the home page, then local business markup for each branch with its real hours, including Friday and Ramadan timings. Add article markup to blog posts and product markup if you sell online. Add defined-term markup only if you run a glossary, and test each type with Google's Rich Results Test.

03Is FAQ schema still worth using?

Only as a by-product. Since August 2023 Google shows FAQ rich results only for well-known government and health websites, so an ordinary business shouldn't expect expandable answers in search. Keep the markup if your CMS generates it for free, but put your effort into writing clear answers on the page itself.

04Can schema markup do harm?

Markup that contradicts the page, or describes things a visitor can't see, such as a rating that isn't shown, publishes a claim you haven't made visibly. That's worse than no markup. Keep it to what's on the page, update it when your facts change, and read Google's structured data guidelines before adding anything unusual.