What is Schema Markup? A Practical Guide to JSON-LD
How structured data helps Google understand your page, and which schema types matter most.
Schema markup is structured data added to a page that explicitly labels what content means — this is a product with this price, this is a question with this answer. JSON-LD is the preferred format: a script block separate from visible content, easier to maintain than annotating HTML tags directly. FAQPage, BreadcrumbList, Article, and Organization schema cover most of what a typical content site needs, each unlocking a different kind of rich result in search.
What schema markup actually does
Schema markup is structured data added to a page that explicitly labels what its content means — this is a product with this price, this is a question with this answer, this is an article by this author. Rather than making search engines infer meaning from plain text, schema states it directly in a machine-readable format, following a shared vocabulary defined by schema.org, a collaborative standard backed by Google, Microsoft, Yahoo, and Yandex.
Search engines use it to power rich results like star ratings, FAQ accordions, and breadcrumb trails directly in search listings — these visually distinct results tend to stand out more and can meaningfully improve click-through rate compared to a plain blue link.
Why JSON-LD is the preferred format
JSON-LD is a script block that sits separately from your visible page content, describing the same information in a structured format search engines can parse directly — unlike microdata, which requires annotating your actual HTML tags with attributes woven throughout the markup, JSON-LD keeps markup and content cleanly separated and easier to maintain.
This separation matters practically: a content editor can update the visible text of a page without needing to understand or accidentally break the structured data, since the JSON-LD block lives independently in the page's head section rather than being interleaved with the content itself.
Common schema types worth using
FAQPage (for question/answer content) can produce an expandable FAQ accordion directly in search results. BreadcrumbList (for navigation trails) shows a page's site hierarchy instead of a raw URL. Article (for blog posts) helps search engines understand publication date, author, and headline for news and content aggregation features.
Organization (for site-wide identity) links a business's name, logo, and social profiles to help establish entity recognition. These four cover most of what a typical content site needs, each unlocking a different kind of rich result in search, though many other schema types exist for specific content — Product, Recipe, Event, HowTo, and dozens more.
Schema type reference table
| Schema type | Used for | Potential rich result |
|---|---|---|
| FAQPage | Question/answer content | Expandable FAQ accordion in search results |
| BreadcrumbList | Navigation hierarchy | Breadcrumb trail instead of raw URL |
| Article | Blog posts, news content | Author, date, headline recognition |
| Organization | Site-wide business identity | Entity recognition, knowledge panel signals |
| HowTo | Step-by-step instructions | Numbered step display in search results |
Generate schema for your page
- Choose the schema type your page needs (FAQ, breadcrumb, etc) with the FAQ Schema Generator.
- Fill in the specific questions, answers, or page details.
- Copy the generated JSON-LD into your page's head section.
Common real-world use cases
Support and help-center pages benefit heavily from FAQPage schema, since a question-and-answer format is exactly what the schema type is built for, and the resulting expandable accordion in search results can capture attention before a competitor's plain listing. E-commerce product pages use Product schema to surface price, availability, and review ratings directly in search results, which studies have repeatedly linked to higher click-through rates than plain listings.
News and blog publishers use Article schema so search engines can correctly attribute authorship and publication date, which matters for content freshness signals and for appearing in news-specific search features. Local businesses use Organization and LocalBusiness schema to reinforce their name, address, and hours consistently across the web, supporting local search visibility alongside their Google Business Profile listing.
Common pitfalls and best practices
- Marking up content that isn't visible on the page. Schema should describe what a visitor actually sees — adding FAQ schema for questions that don't appear anywhere in the visible page content violates search engine guidelines and can lead to a manual penalty.
- Using invalid or malformed JSON-LD. A syntax error in the JSON breaks the entire schema block silently — always validate generated markup before publishing rather than assuming it's correct.
- Adding duplicate schema blocks for the same content. Multiple conflicting schema blocks describing the same entity can confuse search engines about which one to trust, rather than reinforcing the signal.
- Assuming schema guarantees a rich result. Correct schema makes a rich result possible, not automatic — search engines still decide whether and when to actually display it based on many other ranking factors.