Google documents dozens of supported structured data types. You need about six.
The rest are edge cases most sites will never touch. Here are the schema types that actually earn rich results and AI citations, and the one rule that stops your markup getting ignored.
Schema markup is a shared vocabulary, usually written as JSON-LD, that labels the meaning of your content: this is an article, this is its author, this is a question and its answer. Search engines read those labels to understand your page beyond the raw words. That understanding is what earns rich results and makes content easy for AI engines to quote.
Google maintains the structured data reference, and the vocabulary itself lives openly at schema.org. Without schema, an engine infers meaning from messy HTML. With it, you hand the engine a clean description it can trust and reuse.
The schema types worth your time
Most sites only need a focused set. These deliver the clearest return.
| Schema type | Use it for | Payoff |
|---|---|---|
| Organization | Your business identity | Knowledge panel, entity clarity |
| Article | Blog posts and guides | Rich results, AI citations |
| FAQPage | Question-and-answer sections | Expandable FAQ results, quotable answers |
| LocalBusiness | Location and contact pages | Local pack and map support |
| HowTo | Step-by-step guides | Step-based rich results |
| BreadcrumbList | Site navigation paths | Cleaner result breadcrumbs |
Organization and Website: your identity layer
Start here. Organization schema declares who you are (name, logo, contact, social profiles), and Website schema defines your site. Together they anchor your entity, which both Google's knowledge graph and AI engines rely on to attribute content to the right business.
Article and FAQPage: your content layer
Article schema marks up your posts with author, publish date, and headline, feeding rich results and giving AI engines clean metadata. FAQPage schema, generated from real question-and-answer content, can earn expandable results and gives generative engines ready-made quotable answers.
One implementation note from our own site: we generate FAQPage schema automatically from question-style headings, so the structured data never drifts out of sync with the visible content. That sync is the part teams usually get wrong.
LocalBusiness and HowTo: your intent layers
LocalBusiness schema carries your name, address, phone, hours, and service area, reinforcing the signals behind local pack rankings. HowTo schema structures step guides so engines can present them as steps. Use each only where the content genuinely matches the type.
The rule that saves you trouble
Only mark up content that actually appears on the page, and validate every type before shipping. Schema that describes things a user cannot see, or that fails validation, gets ignored at best and flagged at worst. Accurate, validated markup is the whole point.
A few more things worth knowing:
- JSON-LD is the format to use. It sits in a script block separate from your visible HTML, so you can add, maintain, and generate it dynamically without touching page layout. Google recommends it over Microdata and RDFa.
- Schema is not a direct ranking factor. It earns rich results and strengthens entity signals, which support rankings and citations indirectly. High leverage, low downside.
- Add Organization and Website first, then Article and FAQPage. Location businesses should add LocalBusiness early too.
I write about this kind of technical SEO at Loop2Tech, a studio in Karachi, Pakistan. The full version, with the schema-by-template breakdown, is on the original post.
What is the one schema type you have never gotten around to adding? For most people it is HowTo.
Top comments (0)