Does Schema Markup Help AEO? What FAQ Schema Can and Cannot Do

Schema markup is the AEO topic where the gap between what is sold and what is true is widest. Open any AEO checklist and it will tell you to add FAQ schema, HowTo schema and a dozen other types, as if structured data were the lever that makes an AI system quote you.

I build structured data into this site and I include it in client work, so I have no interest in dismissing it. But I also read what Google actually says about it, and the honest position is more modest than the checklists. Here is what schema does, what it does not, and how to use it sensibly as a UK business.

What does Google say about schema and AI search?

Google says structured data is not required for generative AI search and that there is no special schema.org markup you need to add. It adds that it is still a good idea to continue using structured data as part of your overall SEO, because it helps with eligibility for rich results on Google Search. That is from its own guide to generative AI features, which lists over-focusing on structured data among the things you can ignore.

Read that carefully, because it says two things at once. Schema is not an AI visibility lever, and schema is not worthless. The first half kills the claim that adding a particular markup type gets you into AI Overviews. The second half keeps the case for doing it properly.

Then why bother with schema at all?

Because it makes the facts about your business unambiguous to any system that reads it, which is valuable whether or not it is an AI ranking input. Google's guidance on its AI features also says structured data should match the visible text on the page, which tells you what it is for: to state, in a machine-readable way, what the page already says.

• Identity. One organisation, with one name, one address, one phone number and one set of social profiles, declared once and referenced everywhere.
• Disambiguation. A system that sees the same business described identically in markup, on the page and on the Business Profile has less reason to doubt it.
• Rich results. For the types that still earn them, schema is the route to the enhanced listing.
• Consistency checking. Writing the markup forces you to decide the facts, which exposes the inconsistencies you did not know you had.

This is the logic I describe in what entity building actually is: schema is one of several ways a business becomes a thing rather than a string. It is a clarity tool, not a ranking trick.

Does FAQ schema help me appear in AI answers?

There is no evidence from Google that it does, and its guidance says no special markup is needed. FAQ schema became the poster child of AEO advice, so it deserves a direct answer. In August 2023 Google announced it would limit FAQ rich results to well-known authoritative government and health websites, which removed the visual benefit for almost every business site.

The questions and answers themselves are still valuable on the page. A clear question heading with a direct answer helps a reader, and it helps any system extracting an answer, because the text is plain and well organised. The markup around it is optional. If you have FAQ schema, keep it accurate and make sure it matches the visible FAQ. If you do not have it, do not rush to add it for AI.

Note also that HowTo rich results were retired in 2023, according to the technical guidance I have seen. If an AEO checklist still tells you to add HowTo markup for visibility, it is out of date.

Which schema types are worth adding for a UK local business?

Use the most specific LocalBusiness subtype that is true, for example a dentist or legal service type where one exists, and match it to your primary Business Profile category. That agreement between the markup and the profile is worth more than any extra type.

How do I connect the markup into one graph?

Give your organisation a stable ID and reference that same ID from every page, service and person node. Many sites carry disconnected blocks: an Organization in the header, a LocalBusiness on the contact page and a Person on the about page, none aware of the others. That is three objects, not one entity.

1. Pick one canonical ID for the organisation, usually the homepage URL with a fragment, and never change it.
2. Reference it from each page's markup, as the publisher, provider or parent organisation.
3. Link people and services to the organisation by ID rather than repeating the details.
4. Add sameAs links to genuine profiles: Companies House, LinkedIn, your regulator's register, your Business Profile.
5. Keep every value identical to the visible page and to your Business Profile.

What should I be careful not to do?

Do not mark up anything the visitor cannot see, and do not mark up your own reviews as a ratings feature. Google's guidance is that structured data should match the visible text on the page. Hidden or invented markup is a spam-policy risk, not a shortcut.

• Self-serving review markup. As I understand Google's rules, reviews of your own business that you host and mark up do not qualify for review rich results for LocalBusiness and Organization types. Check the current documentation before adding it.
• Invented ratings. A rating that does not exist on the page is a markup abuse. It also fails the honesty test I hold every page to.
• Marking up services you do not offer or areas you do not serve, to widen coverage.
• Duplicating conflicting blocks from a theme, a plugin and a hand-written snippet, so the page carries three versions of the business.
• Treating a valid test result as success. A validator tells you the syntax is correct. It does not tell you the facts are.

How do I check my structured data?

1. Run the page through Google's Rich Results Test and the Schema Markup Validator, and fix errors first.
2. Compare the markup to the page. Every value should be visible somewhere on it.
3. Compare it to your Business Profile. Name, address, phone, hours and categories should agree character for character.
4. Search your own site for stray extra blocks from plugins and themes.
5. Recheck after every redesign, because a template change often silently deletes or duplicates markup.

What does a minimal good setup look like for a London practice?

Three linked blocks cover most of what a single-location professional practice needs. This is an illustration of the shape, not code to paste, and every value must match your visible page and Business Profile.

1. The organisation: the most specific business subtype that is true, with name, full address, phone, opening hours, the areas served and sameAs links to your Business Profile, your regulator's register entry and your professional profiles.
2. The people: one Person block for each named practitioner, with role and credentials, linked to the organisation by its ID.
3. The services: one Service block for each genuine service, such as each treatment or each legal service, linked to the organisation as provider.

Then make every visible detail agree. If the address is written two ways on the contact page and the footer, the markup cannot rescue it. This is the same discipline I describe for regulated firms in the post on AEO for solicitors and dentists.

How often should I revisit it?

After every redesign, every change of address, hours or service, and once a quarter regardless. Structured data rots silently. A theme update duplicates a block, a plugin adds a conflicting one, a price changes on the page but not in the markup. None of it throws an error, and all of it weakens the clarity the markup was there to create.

What is my view on schema and AEO?

Do it properly once, keep it truthful, and stop expecting it to do the work of content. I would rather a client had accurate Organization, Service and Person markup tied together by ID than twenty types sprayed across the site. The first is a clear statement about the business. The second is noise.

The thing that earns an AI citation is still a page with something worth quoting on it, which I cover in how to write content AI quotes. Schema is the label on the box. It helps to have a clear label, and it never made the contents better.