Schema Markup for AEO: The Structured-Data Layer for Answer-Engine Citation

Schema markup is structured data that tells search engines what a page is, who wrote it and what it contains, in a form a machine can read without guessing. For answer engine optimisation (AEO), the types that matter most are Article or BlogPosting, FAQPage, HowTo where there are real steps, Organization with sameAs links, and author Person. Schema makes your page easier for AI engines to read and quote. It does not, on its own, get your brand named in the answer. That depends on how clearly the AI understands your business and on what other sites say about you.

This guide covers which schema types matter for AEO, why they help, how to validate them, and the mistakes to avoid, updated for November 2026 with what our own checks showed about schema’s limits.

What did we see in 2026 about schema and AI naming?

Our 2026 checks show that clean markup helps engines read you, but being named depends mostly on how many trusted sources describe you the same way.

• September 2026, a branding agency client. Across 40 Google AI Overview results, a business found on one source was named 27% of the time; on three or more sources, 87%. Schema on the brand’s own site is one source. The other two have to come from elsewhere.
• August to September 2026, Qwang Coffee, Alva Chew’s own store. On a domain registered on 23 August 2026, it was indexed in 1 hour, on page one in 24 hours and cited in a Google AI Overview in 48 hours. The same site and the same markup gave different results on different engines and on different days. Schema didn’t change; the engines did.
• 2 November 2026, Stridec itself. We asked 15 buyer questions from a Malaysian location across five AI engines and collected 270 answers. The businesses named were the ones the engines found described clearly on several local sources, not simply the ones with the most markup. Markup is necessary groundwork. It is not what gets you recommended in a market where few sources mention you.

So treat schema as groundwork that makes everything else easier to read, and put most of your effort into being described clearly and consistently, on your site and off it.

What does schema markup do for AEO?

Schema markup gives answer engines explicit facts they would otherwise have to infer. It is JSON-LD (or, less often now, microdata or RDFa) in the page that describes the content using the schema.org vocabulary. Readers don’t see it; crawlers and engines read it as a structured layer alongside the page: what kind of page this is, what it contains, who wrote it and which organisation publishes it.

How it helps: when an answer engine picks sources, it weighs relevance, authority, freshness and how easy the page is to quote. Schema helps most with the last. A page with FAQPage schema, where the questions and answers are exposed as structured data, is easier to pull from than the same content in unmarked prose. A page with Article schema, where the author is named and linked to verified profiles through sameAs, gives clearer authority signals than a name buried in a byline. Schema doesn’t ensure a citation; what we see is consistent with it raising the odds.

The flip side: missing schema has a cost. A well-written page without Article schema, FAQPage markup or author Person markup can still be quoted, because engines read unmarked content too. But it competes with pages that do carry the signals, and on close calls the marked-up page tends to win. Treat schema as standard practice on any page you want quoted.

Why is Article or BlogPosting the baseline schema?

Article schema (or BlogPosting for blog content, NewsArticle for news) is the baseline because it states the basic facts about the page: its headline, when it was published, when it was last changed, who wrote it and who publishes it. The fields that matter most: headline (matching the page’s H1), datePublished (ISO 8601 format), dateModified (when the page was last meaningfully updated), author (a Person, ideally with sameAs links) and publisher (an Organization with name and logo).

Why each one counts. Headline gives the engine the page’s main topic in machine-readable form. datePublished and dateModified let engines favour recent content where recency matters. Author Person names the human responsible; with sameAs links to the author’s verified profiles (LinkedIn, the company team page, public bylines), it builds a consistent picture of the writer. Publisher Organization, with name and logo, and with its own Organization schema on the homepage carrying sameAs links, ties the page to a business the engine can verify.

The implementation is JSON-LD in the page. A typical Article block carries @type, headline, image (with width and height), datePublished, dateModified, author (a Person with name, url and sameAs) and publisher (an Organization with name and logo). On WordPress, current versions of SEO plugins such as Yoast, Rank Math and AIOSEO generate this when set up properly. On custom builds, it is generated from the CMS data. Either way, check it with Google’s Rich Results Test.

Why is FAQPage schema the key AEO pattern?

FAQPage schema matters most for AEO because its shape matches how answer engines want to pull content: a question, then its answer. The schema marks a page or section as a list of Question items, each with an acceptedAnswer. An engine reading it gets ready-made question and answer pairs it can use when a search matches one of the questions.

The implementation: an FAQPage object with a mainEntity array of Question items. Each Question has a name (the question) and an acceptedAnswer (an Answer with a text field). The text is the full answer, and engines pull from it. Questions should be the ones readers actually ask, in their words. Answers should stand on their own in one to three short paragraphs, because an engine may lift a single pair without the rest of the page.

Match the markup to real content. FAQPage schema on a page with no visible FAQ, or where the marked-up questions and answers differ from what is on the page, is treated as gaming and may be ignored. The visible FAQ and the schema must mirror each other exactly. Don’t put content in the markup that readers can’t see.

A dated note on Google: since August 2023, Google shows FAQ rich results (the expandable questions under a result) only for well-known, authoritative government and health sites. Most sites no longer get that visual result. The markup is still worth having for AEO, because it tells engines plainly which questions the page answers, but don’t expect the old rich result.

The value of FAQPage schema grows with the quality of the questions. Questions that match what people really ask, with answers that lead with the direct answer, give engines strong material to quote. Questions written to stuff keywords are worth less even when the markup is correct.

When should you use HowTo schema?

Use HowTo schema only when the page walks through real, ordered steps. It describes a task as a sequence: the task name, optionally a description, time and cost, and an array of HowToStep items, each with a name and text. For how-to searches (“how to do X”, “steps to set up Y”), an engine reading HowTo markup gets a clean, ordered list of steps.

The test is whether the page is genuinely a sequence. An article on “how to write for AI Overview” that discusses techniques without ordering them doesn’t fit HowTo. An article on “how to set up Article schema on WordPress” that walks through step 1, step 2, step 3 fits it cleanly.

The implementation: a HowTo object on the page with the step array filled in. Each HowToStep needs a short name and the step text; image, supply, tool and totalTime can be added where they apply. Show the same steps on the page, as a numbered list or headed sections, so the markup and the page match.

A dated note on Google: in September 2023 Google stopped showing HowTo rich results in search. The markup can still help engines read your steps clearly, but it no longer earns a special result on Google. If your steps are clear on the page, with action-verb step names and self-contained instructions, engines can follow them with or without the markup.

How do Organization sameAs and author Person schema build authority?

Organization and Person schema with sameAs links help engines confirm who you are and who wrote the page. Organization schema describes the business: name, logo, url, foundingDate, address where it applies, and most importantly the sameAs array. That array lists the business’s official pages elsewhere: its LinkedIn page, X profile, Facebook page, a Wikipedia entry if one exists, and official directory listings. Engines use these links to check that the business is the same everywhere.

Why it matters: when an engine weighs a source’s authority, one factor is whether the business is described consistently across the web. A brand with Organization schema pointing to verified profiles presents a clear, checkable identity. A brand that exists only on its own site is treated more cautiously. sameAs lets the engine cross-check instead of taking the brand’s word for it. It doesn’t replace the other sites themselves: the profiles and mentions have to exist and say the same thing.

Author Person schema does the same for writers. Each article’s Person should carry the author’s name, a url to their author page on your site, and sameAs links to their LinkedIn, the company team page, bylines elsewhere and academic profiles where relevant. Where author expertise matters (medical, legal, financial and specialist technical topics), this is a meaningful signal.

Keep the full Organization schema on your homepage as the main reference, and update the sameAs list as your profiles change. Article schema can point to the Organization by URL rather than repeating it on every page. Author Person on articles should point to each author’s profile page, which carries the full Person schema with sameAs links.

How do you validate schema, and what mistakes should you avoid?

Validate every page before it goes live; it catches most mistakes. Google’s Rich Results Test reads a page’s structured data and reports errors and warnings. The Schema.org Validator checks it against the wider schema.org vocabulary. Editor plugins for VS Code and others catch JSON-LD errors as you type. Schema with errors doesn’t get used, schema with warnings may be partly used, and schema that validates cleanly gets the full benefit.

The mistakes we see most: missing required fields (Article without datePublished, Person without name); links to things that don’t exist (an author URL that returns a 404); mismatched content (FAQPage questions that aren’t on the page); stuffed schema (several FAQPage blocks for one FAQ, Product schema on an editorial article); dates not in ISO 8601; and a dateModified that wasn’t updated when the page changed. Each one reduces or removes the benefit.

The AEO schema checklist for a typical article:

• Article or BlogPosting with headline, datePublished, a current dateModified, author Person (name, url, sameAs) and publisher Organization (name, logo, URL).
• FAQPage on the FAQ section, with questions and answers matching the page exactly.
• HowTo only if the article has real, ordered steps.
• Organization schema on the homepage, with sameAs links to verified profiles.
• Person schema on author pages, with sameAs links to verified author profiles.
• A clean pass in Google’s Rich Results Test and the Schema.org Validator.
• Visible page content that matches the structured data.

This is the groundwork under the writing work covered elsewhere on this site, from how to get cited in AI Overview to how Google AI Overview selects sources. Necessary, but not enough by itself.

Conclusion

Schema markup for AEO gives answer engines explicit facts about what a page is, what it contains and who produced it. Article or BlogPosting is the baseline. FAQPage on a real FAQ is the most useful pattern because it matches how engines pull answers. HowTo fits genuine step-by-step pages. Organization and author Person with sameAs links help engines confirm who you are. Validation catches most mistakes before they cost you.

Schema is groundwork under the content work, not a substitute for it. Missing schema doesn’t waste good writing, but close calls tend to go to the page with the structured data in place. Match the markup to the real page, validate before publishing, and keep sameAs and dateModified current. Then put the bigger effort into being described clearly and consistently across the web, because that is what gets a brand named.

What to do next

With the markup in place, the next step is to see whether AI actually names you, and to decide who does the rest of the work.

• Check whether Google’s AI Overview names you today with the free AIO Visibility Checker.
• If AI names a competitor and not you, read why ChatGPT recommends your competitor and what to do.
• Choosing a route? Compare hiring a GEO agency, training your team or doing it yourself.
• Vetting an agency? See how GEO results are measured and the red flags when hiring an agency.

Frequently asked questions