Schema
Schema (often implemented as JSON-LD) is structured data that helps search engines understand your page content—products, articles, organizations, events, and more.
- Search engines use schema to show rich results (e.g. stars, FAQs, breadcrumbs) in search results.
- Valid JSON-LD in
<script type="application/ld+json">is the recommended way to add structured data. - Missing or invalid schema can mean no rich results and weaker topical signals.
- This tool checks multiple URLs for the presence of JSON-LD, reported types, and parse errors.
What is Schema / JSON-LD?
Schema.org structured data is a standardized vocabulary that helps search engines understand the meaning of the content on your webpages. Instead of relying only on visible text, structured data explicitly describes the entities on a page - such as products, articles, organizations, recipes, events, reviews, people, and businesses—in a machine-readable format.
JSON-LD (JavaScript Object Notation for Linked Data) is the most widely adopted format for implementing Schema.org markup and is recommended by Google for adding structured data to webpages. Unlike Microdata or RDFa, JSON-LD keeps the structured data separate from the HTML content, making it easier to implement, maintain, and debug.
JSON-LD is typically embedded inside a <script type="application/ld+json"> tag placed within the page's
For example, instead of simply seeing a webpage containing a product description, Schema markup tells search engines that the page represents a Product, along with its name, price, availability, brand, and reviews. This additional context helps search engines interpret the page more accurately and, when eligible, display enhanced search features such as rich snippets.
Given below is an example implementation of Schema code using JSON LD:
<script type="application/ld+json">
{ "@context": "https://schema.org", "@type": "Organization", "name": "Example", "url": "https://example.com" }
</script>
How Search Engines Read Schema
When search engines crawl a webpage, they look for structured data embedded within the HTML. If JSON-LD schema is present, the crawler parses the structured data to identify entities such as products, organizations, articles, authors, reviews, events, and more.
This additional layer of information helps search engines understand the meaning and context of your content instead of relying solely on the visible text. When the structured data is valid and follows Google's guidelines, the page may become eligible for enhanced search features known as Rich Results.
The process typically works like this:
- Search engines crawl the webpage and look for structured data embedded in the HTML.
- JSON-LD is parsed to identify entities such as products, articles, organizations, events, reviews, recipes, and people.
- The relationships between entities are understood, allowing search engines to interpret the page more accurately.
- The structured data is validated to ensure it follows Schema.org vocabulary and Google's implementation guidelines.
- Eligible pages may qualify for Rich Results, such as review stars, product information, breadcrumbs, FAQs, event listings, and other enhanced search features.
Search engines are becoming increasingly focused on understanding the meaning behind web content rather than simply matching keywords. Schema markup provides explicit information about the entities, attributes, and relationships on a page, making it easier for search engines to interpret your content accurately.
While structured data is not a direct ranking factor, it can improve how your pages are presented in search results by making them eligible for rich results such as review stars, product information, FAQs, event listings, and breadcrumbs. Implementing valid schema also improves data consistency across your website, helping search engines process your content more reliably and efficiently.
- Rich results: Valid schema can unlock rich snippets, FAQs, and other enhanced SERP features.
- Clarity for crawlers: Search engines use it to understand entities, types, and relationships on the page.
- Consistency: Bulk testing helps ensure every important URL has correct, parseable structured data.
Common Schema Types Used by Websites
Schema.org provides hundreds of structured data types, but only a handful are commonly used across most websites. Choosing the appropriate schema type helps search engines better understand your content and determine whether it qualifies for rich search features.
| Schema Type | Common Usage |
|---|---|
Organization |
Company websites and brands |
Article |
Blog posts and news articles |
BreadcrumbList |
Website navigation |
Product |
Ecommerce product pages |
FAQPage |
Frequently Asked Questions |
LocalBusiness |
Physical businesses and stores |
Person |
Author and profile pages |
Event |
Conferences, webinars and live events |
Recipe |
Cooking and food websites |
VideoObject |
Video content |
Common Schema Implementation Mistakes
Simply adding structured data is not enough. Invalid or misleading schema markup can prevent search engines from understanding your content and may stop your pages from becoming eligible for rich results.
- Missing required properties for a schema type.
- Invalid JSON syntax or malformed JSON-LD.
- Using the wrong
@typefor the page. - Missing the required
@contextproperty. - Structured data that does not match the visible page content.
- Duplicating the same entity across multiple conflicting schema blocks.
- Using outdated Schema.org properties.
- Publishing fake reviews or misleading structured data.
Schema Best Practices
Implementing structured data correctly is just as important as implementing it at all. Well-structured, accurate, and up-to-date schema markup helps search engines understand your content more effectively and increases your chances of becoming eligible for rich results. Following established best practices also makes your structured data easier to maintain, reduces implementation errors, and ensures it continues to reflect the content visible on your webpages.
- Use JSON-LD whenever possible.
- Ensure structured data accurately reflects the visible page content.
- Include all recommended properties for your chosen schema type.
- Validate structured data after every website deployment.
- Keep structured data updated whenever page content changes.
- Use one primary entity per page whenever possible.
- Regularly audit important pages for schema errors.
- Test your structured data before publishing new pages.
Do's and Don'ts
Do's
- Use valid JSON inside
application/ld+jsonscript tags. - Include
@contextand@typeas required by schema.org. - Test pages after adding or changing structured data.
- Prefer JSON-LD over Microdata or RDFa for easier maintenance.
Don'ts
- Don't inject invalid JSON (syntax errors, trailing commas, or HTML inside the script).
- Don't duplicate the same entity in conflicting ways across multiple blocks.
- Don't leave critical pages without any structured data when it could apply.
FAQs
This tool fetches each URL, detects JSON-LD script tags, parses the structured data, identifies the schema types present (such as Organization, Article, Product, FAQPage, BreadcrumbList, etc.), reports any parsing errors, and returns an overall pass or fail result for every URL.
A URL may fail if no JSON-LD is found, the structured data contains invalid JSON syntax, required properties such as type are missing, the page returns a non-200 HTTP status code, or the structured data cannot be parsed successfully.
This tool verifies the presence of JSON-LD, parses the structured data, and reports the schema types detected. It does not perform full Schema.org validation of required or recommended properties. For complete validation, use Google's Rich Results Test or the Schema Markup Validator.
Schema markup is not a direct Google ranking factor. However, it helps search engines better understand your content and may make your pages eligible for rich results, which can improve visibility and click-through rates.
Schema.org is the vocabulary that defines entities and properties such as Product, Article, Organization, and Event. JSON-LD is one of the formats used to implement that vocabulary on a webpage. Google recommends using JSON-LD because it is easier to implement and maintain.
JSON-LD is commonly placed inside the HTML head section, although Google also supports placing it within the page body. Regardless of its location, the structured data should accurately describe the visible content on the page.
Yes. A webpage can contain multiple structured data entities, such as Organization, BreadcrumbList, Article, FAQPage, Product, or VideoObject, provided each one accurately represents the content on the page.
If your JSON-LD contains syntax errors or invalid Schema.org markup, search engines may ignore the structured data entirely. This can prevent your page from becoming eligible for rich results or other enhanced search features.
No. Search engines can crawl and index webpages without structured data. However, Schema provides additional context that helps search engines understand your content more accurately and may improve how your pages appear in search results.
Structured data should be tested whenever new pages are published, existing templates are modified, or website deployments are made. Regular audits help identify broken markup, outdated properties, and implementation issues before they affect your search appearance.