Two pages can rank in the same position on Google and still perform very differently, simply because one shows a star rating, a price, or a recipe time in the search result and the other shows plain blue text. That difference usually comes down to schema markup.
What is schema markup in SEO?
Schema markup is the term used to describe a structured piece of code, typically in JSON-LD format, which is added to a webpage to describe its content in a way that search engines can readily understand. The schema allows a search engine to determine that a page is about a recipe, a product, an event, a local business, etc., based on the schema alone, not just the headings and body text.
This structured layer sits behind the scenes and does not change how a page looks to a visitor. What it does change is how that page can appear in search results, often unlocking star ratings, prices, FAQ dropdowns, or other rich result formats that plain HTML cannot produce on its own.
Why does schema markup in SEO matter for rankings and clicks?
Schema markup does not directly influence ranking position the way backlinks or content quality do, but it strongly influences whether a result gets clicked once it appears. In Google's own published data on structured data, Rotten Tomatoes saw a 25% higher click-through rate on pages carrying structured data compared to pages without it.
Nestlé's figures from the same source show an even larger effect, with rich-result pages generating 82% more clicks than non-rich pages for comparable rankings. Food Network reported a 35% increase in visits after converting roughly 80% of its pages to structured markup, a scale of change that points to consistent implementation mattering as much as the markup itself.
What are the main types of schema in SEO?
Different page types call for different schema, and using the wrong one, or skipping it entirely, leaves potential rich results on the table. The sections below cover the types most sites end up needing.
Product schema
Product schema tells Google the price, availability, and review data for an item. That is what makes star ratings and pricing appear directly in search results for ecommerce listings. It pairs naturally with Review or AggregateRating schema, since price alone rarely earns a rich result without accompanying customer feedback data.
LocalBusiness schema
LocalBusiness schema covers a company's name, address, phone number, hours, and service area, feeding directly into Google's local pack and Maps results. A business with multiple locations typically needs a separate LocalBusiness entry for each address rather than one blanket listing covering the whole company.
Article and BlogPosting schema
Article schema, along with its more specific BlogPosting and NewsArticle variants, marks up headline, author, publish date, and featured image for editorial content. This schema type is what allows a blog post to display an author byline or publish date directly beneath its search listing.
FAQPage and HowTo schema
FAQPage schema formats a set of questions and answers so they can expand directly within the search result, while HowTo schema breaks a process into numbered steps with optional time and material estimates. Both work best on pages where the content genuinely follows a question-and-answer or step-by-step structure, rather than being retrofitted onto prose that does not naturally fit either format.
Review and AggregateRating schema
Review schema captures a single review's rating and text, while AggregateRating summarises many reviews into one score. Star ratings shown beneath a search result almost always trace back to one of these two schema types working correctly.
BreadcrumbList schema
BreadcrumbList schema describes a page's position within a site's navigation hierarchy, and Google frequently displays that breadcrumb trail in place of a raw URL beneath the search result. It also helps search engines understand how a site is structured, supporting crawling beyond the immediate ranking benefit.
List of schemas by page type
| Page type | Primary schema | Common pairing |
|---|---|---|
| Product listing | Product | Review, AggregateRating, Offer |
| Local storefront | LocalBusiness | Organization, GeoCoordinates |
| Blog post | Article or BlogPosting | Person (author), BreadcrumbList |
| FAQ or support page | FAQPage | Organization |
| Instructional content | HowTo | VideoObject |
| Recipe page | Recipe | AggregateRating, NutritionInformation |
| Event listing | Event | Offer, Place |
| Job listing | JobPosting | Organization |
| Video content | VideoObject | BreadcrumbList |
| Any indexable page | BreadcrumbList | Organization |
How do you choose the right schema type for a page?
The safest approach is matching schema to what the page is actually about, rather than adding every available type in hopes of unlocking more rich results. A blog post that reviews a product might justifiably carry both Article and Review schema, but forcing Product schema onto a page with nothing for sale usually triggers a Search Console warning rather than a rich result.
Google's structured data guidelines require that markup reflect content genuinely visible on the page. Schema describing a five-star rating that never appears anywhere in the visible content is treated as manipulative rather than helpful, and pages found doing this can lose their eligibility for rich results altogether.
Margo Digitech builds schema selection into its technical SEO work for every client site, mapping each page type to the markup that fits it rather than applying a single template across an entire catalogue or blog.
Frequently Asked Questions
No, schema markup makes a page eligible for a rich result, but Google decides case by case whether to actually display one. Implementation quality, page authority, and how well the content matches the schema all factor into that decision.
types where they truly represent different content elements of the same, like Article schema along with FAQPage schema for a blog post that is followed by a Q&A section. Putting unrelated schema types on a single page with no content match between the types usually doesn't work out well.
JSON-LD is Google's recommended format, though Microdata and RDFa remain technically valid alternatives embedded directly within HTML tags. Most modern SEO tools and CMS plugins default to JSON-LD because it can be added as a separate script block without touching the page's existing markup.
Google typically needs to recrawl and reprocess a page before any rich result appears, which can take anywhere from a few days to several weeks depending on how often that page gets crawled. Submitting the page through Search Console after adding schema can speed up that recrawl.
Structured data gives AI systems a cleaner, more reliable source of facts to extract, though it is one factor among many rather than a guarantee of AI citation. Content accuracy and third-party coverage still carry more weight than markup alone in most AI search visibility research.