Schema Markup for Search: A Practical Technical Guide

What schema markup does

Schema.org provides a shared vocabulary for describing page content in machine-readable form. Search engines can use structured data as an explicit clue about the page and, for supported types, to determine rich-result eligibility. Correct markup does not guarantee a rich result, ranking or citation.

Google’s AI Search documentation says there is no special schema markup required for AI Overviews or AI Mode. Use structured data for accurate description and documented Search features—not as an AI-citation switch. For a broader view, see our GEO and SEO comparison and source-citation guide.

The separate llms.txt guide explains a community proposal for a Markdown index; it is not a schema vocabulary or crawler directive.

Choose a type that matches the page

Page	Possible type	Editorial check
Organization homepage or about page	Organization	Use accurate official details and profiles; do not add properties that are not supported
Article or guide	Article or a relevant subtype	Match the visible headline, author, dates and image
Product page	Product	Keep price, availability and other offer details current and visible
A page with navigation hierarchy	BreadcrumbList	Ensure the breadcrumb represents the actual path a user can follow

This is not a complete list of Google-supported Search features. Check Google’s current documentation for the type, required properties, policies and eligibility rules that apply to the page.

Google recommends JSON-LD in most cases because it is straightforward to maintain, but it also supports Microdata and RDFa. Choose a format the team can keep synchronized with the visible page.

Write and maintain accurate markup

A practical workflow:

1. Identify the page’s purpose and the structured-data type that describes it.
2. Read the current feature-specific guidelines and general structured-data policies.
3. Mark up only information that is present on the page or otherwise valid for that entity.
4. Validate syntax and rich-result eligibility with Google’s Rich Results Test where applicable; use the Schema.org validator to check vocabulary.
5. Compare the rendered page with the JSON-LD after release and correct inconsistencies when content changes.

For Organization data, Google says markup on the home page can help it understand organization details and disambiguate organizations in Search. The sameAs property can point to genuine external profiles or pages with more information; it does not prove identity by itself.

For article data, make sure the title, author, dates and image accurately reflect the article. Do not invent authors or review details. dateModified should reflect a substantial update rather than a cosmetic change.

FAQ and HowTo markup: check the current feature status

Google restricted FAQ rich results to well-known, authoritative government and health sites and deprecated HowTo rich results in 2023. Adding those types should not be presented as a way to obtain the former Search appearances or to prompt AI systems to quote the page. Visible, useful question-and-answer or instructional content can still help readers without relying on those rich-result displays.

Google may change its search appearances. Validate against current documentation rather than older tutorials or plugin defaults.

What structured data does not prove

A valid JSON-LD block proves only that the markup parses and describes the supplied facts. A passing Rich Results Test can indicate eligibility for a supported rich result; Google does not guarantee that it will appear. Neither tool establishes that an AI assistant fetched the page or used its structured data in an answer.

Treat non-Google behavior as provider-specific. Unless a service documents how it uses structured data, claims that schema increases citation likelihood are hypotheses. Keep page content accurate and cite authoritative sources for claims that readers need to verify.

FAQ

Does schema markup improve rankings?

Structured data can help search engines understand page content and can support eligibility for specific rich results. Google says it does not guarantee rich-result display, and structured-data issues do not directly change ordinary web ranking. Do not claim a ranking lift from markup alone.

Does schema markup help AI systems cite a page?

There is no general guarantee. Google says no special schema is required for its AI Search features. Other systems’ use of schema is provider-specific unless documented.

Should every article use FAQ or HowTo schema?

No. Google restricted FAQ rich results and deprecated HowTo rich results. Use only types that describe visible content and fit the current guidelines; do not add markup to chase unsupported features.

How do I validate structured data?

Use the Rich Results Test for supported Google rich results and the Schema.org validator for vocabulary and syntax. Then confirm that the live page and markup agree.