Guides
Step-by-step guides for generating Google-eligible rich results with schemaorg-kit. Each guide covers the required and recommended fields, common mistakes, and a complete working example you can copy into your project.
Rich Result Types
| Guide | Google Rich Result | Eligible Content |
|---|---|---|
| Article | Article snippet with author, date | Blog posts, news, editorial |
| Product | Price, availability, reviews | E-commerce product pages |
| Local Business | Business info, hours, map | Restaurants, shops, services |
| Event | Date, location, ticket link | Concerts, workshops, webinars |
| Recipe | Cook time, rating, nutrition | Food & cooking content |
| FAQ | Expandable Q&A pairs | Support pages, product pages |
| Job Posting | Salary, location, apply button | Careers / jobs pages |
| Organization | Knowledge panel signals | Brand / company pages |
| Video | Video thumbnail, duration | Video pages |
| Software App | Rating, price, platform | App landing pages |
| Dataset | Dataset discovery card | Open data, research |
| Course | Provider, duration | E-learning pages |
| Vacation Rental | Amenities, rating | Property listings |
| Book Actions | Read / Borrow buttons (invite-only) | Book & publishing pages |
| Website & Sitelinks | Sitelinks search box | Homepage |
| Claim Review | Fact-check verdict label | Fact-checking articles |
| Discussion Forum | Forum thread snippet | Forums, communities |
| Education Q&A | Flashcard / practice Qs | Study & flashcard pages |
| Math Solver | Math solver feature | Online math tools |
| Profile Page | Creator profile signals | Author & profile pages |
| Person | Author / creator identity | Author bios, team pages |
| @graph — Multi-Schema Pages | Combined signals | Any page with multiple entities |
How Google Rich Results Work
Google’s crawlers read the JSON-LD in your <head> and use it to enhance your listing in search. Your structured data must:
- Match the visible page content — don’t describe content that isn’t on the page
- Be complete — required fields must be present and non-empty
- Use the right
@type— Google only enhances supported types - Be accessible — paywalled content needs special markup
Test your output at Google’s Rich Results Test.