Google schema requirements define exactly how structured data must be implemented to qualify for rich results in search. Following these structured data rules is essential because violating them can result in manual actions that remove your rich results entirely. This guide explains every guideline Google publishes, from technical format requirements to quality policies that govern content accuracy.
Google Search Central documentation (updated January 2026) establishes two categories of guidelines: technical requirements that validation tools can check automatically, and quality guidelines that require human judgment. Understanding both is critical because syntactically correct structured data can still be rejected if it violates quality policies. This comprehensive guide covers the official Google Structured Data Guidelines, helping you implement schema markup that meets all requirements and remains eligible for enhanced search appearances.
Google Schema Requirements
Understanding the Google Schema Requirements is essential for achieving rich results and ensuring compliance with Google’s structured data guidelines.
Table of Contents
What Are Google’s Structured Data Guidelines?
Google Schema Requirements define how structured data must be implemented to qualify for rich results and enhanced search visibility. They include both technical rules and quality guidelines to ensure your markup is accurate, relevant, and compliant with Google’s standards.
Structured Data Rules for Enhanced Visibility
Google’s structured data guidelines are the official rules published in Google Search Central documentation that govern how schema markup must be implemented to qualify for rich results. These guidelines establish both technical requirements (format, syntax, property completeness) and quality requirements (content accuracy, user relevance, policy compliance).
The guidelines exist at two levels. General structured data guidelines apply to all schema types and cover universal rules like format requirements, accessibility to Googlebot, and content representation accuracy. Feature-specific guidelines apply to individual schema types (Product, Article, FAQ, Recipe, etc.) and define which properties are required, recommended, or optional for each type, plus any content policies unique to that feature.
Google explicitly states that meeting these guidelines ensures eligibility under Google Schema Requirements, but does not guarantee rich result display. Google’s algorithm decides visibility based on relevance, user experience, and competition while violations can prevent rich results and may trigger manual actions.
What Are the Technical Format Requirements?
Google supports three structured data formats: JSON-LD (recommended), Microdata, and RDFa. All three are technically valid for rich results, but Google explicitly recommends JSON-LD because it is easier to implement, less prone to errors, and simpler to maintain at scale.
JSON-LD (Recommended)
JSON-LD (JavaScript Object Notation for Linked Data) is a script-based format that can be placed anywhere in the HTML document, typically in the <head> or <body>. It is separate from the visible HTML content, making it easier to add without modifying page templates. Google recommends JSON-LD as the easiest solution for website owners to implement and maintain.
Microdata
Microdata uses HTML attributes (itemscope, itemtype, itemprop) embedded directly within page content. Because it is interleaved with visible HTML, changes to page structure can accidentally break the markup. Microdata remains supported but is more error-prone than JSON-LD.
RDFa
RDFa (Resource Description Framework in Attributes) is similar to Microdata in that it uses HTML attributes. It is fully supported but less commonly used than JSON-LD or Microdata for SEO purposes.
Critical technical requirement: Pages containing structured data must be accessible to Googlebot. Do not block structured data pages using robots.txt, noindex tags, or login requirements. If Google cannot crawl the page, it cannot process the structured data.
What Properties Are Required vs. Recommended?
Each schema type has properties classified as required, recommended, or optional. Required properties must be present for the structured data to be eligible for rich results; missing required properties disqualify the markup entirely.
Required Properties
Items missing required properties are not eligible for rich results under Google Schema Requirements. For example, Product schema requires a name, Event requires name, startDate, and location, and Recipe requires name and image these requirements vary by schema type and are defined in Google Search Central.
Recommended Properties
Recommended properties are not strictly required but improve the quality and likelihood of rich result display under Google Schema Requirements. Google states that providing more recommended properties enhances result quality for example, job postings with salaries or recipes with reviews and ratings are more compelling to users.
Optional Properties
Optional properties provide additional context but have minimal impact on rich result eligibility or display. Include them when they add value to users, but do not prioritize them over required and recommended properties. Some schema types (like Article and Organization) have no strictly required properties; instead, Google recommends adding as many relevant properties as apply to your content.
What Quality Guidelines Must Structured Data Follow?
Quality guidelines govern the accuracy and relevance of structured data content. Unlike technical requirements, these cannot be fully tested by automated tools and require human judgment. Violating quality guidelines can prevent rich results even when markup is syntactically correct.
Structured Data Must Represent Visible Content
The most fundamental quality rule: structured data must describe content that is actually visible on the page. Do not create blank or empty pages just to hold structured data. Do not add structured data about information that is not visible to users, even if the information is accurate. Structured data should be a true representation of the page content.
Content Must Be Relevant to the Schema Type
Google provides examples of irrelevant schema usage: a sports streaming site labeling broadcasts as local events, or a woodworking site labeling instructions as recipes. The schema type must accurately match the content type. Using incorrect schema types to try to trigger rich results is considered spam.
Data Must Be Complete and Current
If a page displays multiple reviews, the structured data should include all reviews visible to users not just selected positive ones in line with Google Schema Requirements. Marking up only favorable reviews or using outdated pricing, availability, or dates can mislead users and violate quality policies.
Use the Most Specific Applicable Types
When multiple schema types could apply, use the most specific type defined by Schema.org. For example, use NewsArticle rather than Article for news content. Use LocalBusiness subtypes (Restaurant, Dentist, AutoRepair) rather than the generic LocalBusiness when applicable.
What Content Policies Apply to Structured Data?
Structured data must comply with Google’s Content policies, spam policies, and overall Google Schema Requirements. Content in structured data is subject to the same rules as regular page content.
- General Content Policies: Structured data must not be deceptive, harmful, illegal, or misleading, and should follow all content quality and safety standards.
- Feature-Specific Policies: Different schema types (like JobPosting or Review) have specific rules such as requiring real user-generated reviews and accurate job information.
- Spam Policies: Manipulative structured data (fake reviews, misleading info, or hidden content) can trigger manual actions affecting both visibility and rankings.
- Search Essentials: All implementations must follow Google’s Search Essentials to remain eligible for search features.
Tip: Always ensure your structured data matches visible page content and regularly audit it to stay compliant with evolving Google Schema Requirements.
What Causes Structured Data Manual Actions?
Manual actions are penalties applied by human reviewers when structured data violates Google Schema Requirements. A structured data manual action removes rich result eligibility for affected pages. According to Google, this typically does not affect how the page ranks in standard web search results, though broader spam violations can trigger ranking penalties.
Common Manual Action Triggers
Marking up hidden content: Adding structured data for content that is not visible to users. This includes hiding aggregate reviews or star ratings in the markup while not displaying them on the page violating Google Schema Requirements.
Irrelevant or misleading markup: Using schema types that do not match the actual page content. Labeling non-recipe content as recipes, non-events as events, or adding Product schema to pages without purchasable products.
Fake or manipulated reviews: Marking up fake reviews, ratings not from actual users, or selectively marking up only positive reviews to inflate apparent ratings.
Schema not matching content: JobPosting markup on pages without actual job postings, ClaimReview on pages without fact-checks, or any schema where the markup data contradicts what users see under Google Schema Requirements.
Recovery process: To resolve a manual action, fix all violations, then submit a reconsideration request through Google Search Console. Google will review and revoke the action if the site is compliant. Check the Manual Actions report in Search Console to identify specific issues.
How Do You Validate Compliance with Google’s Rules?
Google provides official tools to test technical compliance with Google Schema Requirements. These tools catch syntax errors and missing required properties but cannot evaluate quality guideline compliance.
Rich Results Test
The Rich Results Test validates structured data and shows which rich results the page is eligible for. It identifies errors (which prevent eligibility) and warnings (which may reduce quality). The tool also provides previews of how rich results might appear. Use this before deployment to catch technical issues.
URL Inspection Tool
Available in Google Search Console, the URL Inspection tool shows how Google actually sees a specific URL, helping you stay aligned with Google Schema Requirements. It includes detected structured data, reveals whether Googlebot can access the page, and identifies any rendering or crawling issues that might prevent structured data from being processed.
Search Console Enhancements Reports
After deployment, monitor the Enhancements section in Google Search Console to stay aligned with Google Schema Requirements. Reports for each structured data type (Product, FAQ, Recipe, etc.) show valid items, items with errors, and items with warnings across your entire site. These reports update as Google recrawls pages and are the definitive source for ongoing structured data health.
Schema Markup Validator
The Schema.org validator tests against Schema.org specifications rather than Google-specific requirements. Use it to verify vocabulary correctness, but rely on Google’s Rich Results Test for Google Search eligibility.
What Are the Image and URL Requirements?
Images specified in structured data must be crawlable and indexable by Google. All image URLs must be accessible to Googlebot without authentication or blocking.
Image Accessibility
All image URLs specified in structured data must be crawlable and indexable. Otherwise, Google Search cannot find and display them on the search results page. Use the URL Inspection tool to verify that Google can access your image URLs. Images blocked by robots.txt or requiring authentication will not appear in rich results.
Image Relevance
When specifying an image as a structured data property, ensure the image is relevant to the page content and aligns with Google Schema Requirements. For example, if you define the image property of a NewsArticle, the image must directly relate to that article using stock or unrelated images violates quality guidelines.
URL Requirements
URLs in structured data (for images, pages, or canonical references) must be fully qualified (including https://). Relative URLs may not be processed correctly. For duplicate pages showing the same content, Google recommends placing the same structured data on all page duplicates, not just the canonical page.
How Should Multiple Schema Types Be Handled?
You can include multiple structured data objects on a page as long as they describe user-visible content and align with Google Schema Requirements. This is common for pages with multiple content types or nested information, ensuring each schema accurately represents what users see.
Multiple Items of Different Types
A page can contain different schema types simultaneously as long as they follow Google Schema Requirements. Each schema object—such as Recipe, BreadcrumbList, or Organization should represent distinct visible content, and Google evaluates each type independently for rich result eligibility.
Multiple Items of the Same Type
Pages listing multiple items (like a category page with multiple products) can include multiple schema objects of the same type. Google recommends that when marking up multiple items on a single page, all items should be of the same type when possible. For list pages, consider using ItemList schema to structure the collection.
Nested Structured Data
Complex pages often require nested schema. A Recipe might include nested AggregateRating, VideoObject, and NutritionInformation. A Product might nest Offer, Review, and Organization. Nesting follows Schema.org vocabulary rules, with child objects referenced by the appropriate property of the parent object. Google’s documentation includes examples of correct nesting for each schema type.
What Schema Types Has Google Deprecated?
Google periodically retires structured data types that are underused or no longer valuable. Starting January 2026, several schema types will no longer be supported in Search Console or trigger rich results.
Deprecated as of January 2026:
- Practice Problem: Educational problem-solving markup is no longer supported for rich results.
- Dataset: Now only serves Dataset Search, not general Google Search rich results.
- Sitelinks Search Box: Being integrated into core search functionality.
- SpecialAnnouncement: COVID-specific markup no longer needed.
- Q&A: Limited adoption and overlap with other types led to deprecation.
John Mueller of Google clarified that these changes align with evolving Google Schema Requirements, focusing on improving how structured data is displayed rather than impacting rankings. Sites using deprecated schema types won’t face penalties, but should update their markup to stay compliant and eligible for rich results.
Tip: Regularly review supported schema types and update outdated markup to maintain visibility and performance.
Why Doesn’t Valid Schema Always Show Rich Results?
Google explicitly states that even when your markup follows all Google Schema Requirements, it does not guarantee that structured data will appear in search results. Having valid structured data enables eligibility, but display is still determined by Google’s algorithm.
Reasons Rich Results May Not Appear
- Algorithm determines appropriateness: Google’s algorithm tailors search results based on search history, location, device type, and query context. For some queries, text results may be deemed more appropriate than rich results.
- Structured data not representative of main content: If the schema describes secondary content rather than the page’s primary purpose, Google may not display rich results.
- Potentially misleading content: Even technically valid schema can be rejected if Google’s systems detect that it could mislead users.
- Errors not caught by validation tools: Some issues, particularly quality guideline violations, cannot be detected by the Rich Results Test but still prevent display.
- Content hidden from users: If the structured data references content that users cannot see (behind paywalls without proper markup, in collapsed sections, or hidden by CSS), rich results may not appear.
Frequently Asked Questions (FAQ)
Does structured data affect search rankings?
Structured data is not a direct ranking factor. It enables rich results (a display feature) but does not boost rankings. However, rich results can improve click-through rates, which indirectly benefits traffic.
What happens if my structured data has errors?
Errors typically prevent rich result eligibility rather than causing ranking penalties. Missing required properties mean the markup is ignored for rich results. Spammy or manipulative structured data can trigger manual actions.
Which structured data format does Google recommend?
Google recommends JSON-LD. It is easier to implement, less error-prone, and simpler to maintain than Microdata or RDFa. All three formats are supported, but JSON-LD is preferred.
Can I add Schema for content behind a paywall?
Yes, but you must use subscription and paywalled content structured data to identify paywalled sections. This prevents the markup from being considered cloaking (showing different content to Google than to users).
How long does it take for rich results to appear after adding schema?
It depends on how quickly Google recrawls your pages. This can range from days to weeks. You can request indexing through Search Console to expedite the process, but display is not guaranteed even after crawling.
Do I need to add structured data to every page?
No. Add structured data only to pages where it is relevant and accurate. Focus on pages where rich results would benefit users and drive meaningful traffic, such as product pages, articles, events, and recipes.
What is the difference between Schema.org documentation and Google’s documentation?
Schema.org defines the vocabulary (types and properties), while Google’s documentation outlines how these should be implemented under Google Schema Requirements for rich results. Always rely on Google Search Central as the definitive source for how structured data behaves in Google Search.
How do I recover from a structured data manual action?
Fix all violations identified in the Manual Actions report in Search Console, then submit a reconsideration request. Google will review and revoke the action if the site is compliant. Recovery time varies but typically takes days to weeks.
Key Takeaways
Google’s structured data guidelines include both technical requirements (format, syntax, required properties) and quality requirements (content accuracy, relevance, policy compliance). These Google Schema Requirements must be met for rich result eligibility.
JSON-LD is Google’s recommended format. It is easier to implement, less prone to errors, and simpler to maintain than Microdata or RDFa.
Structured data must accurately represent visible page content. Marking up hidden content, using irrelevant schema types, or manipulating reviews triggers manual actions.
Required properties must be present for rich result eligibility. Recommended properties improve quality and display likelihood. Always check feature-specific documentation for property requirements.
Valid structured data does not guarantee rich results. Google’s algorithm determines display based on query relevance, user experience, and SERP competition.
Use Google’s Rich Results Test before deployment and Search Console Enhancements reports for ongoing monitoring to stay aligned with Google Schema Requirements. Quality guideline violations are not detectable by automated tools.
Google deprecates schema types over time. Starting January 2026, Practice Problem, Dataset (for general search), Sitelinks Search Box, SpecialAnnouncement, and Q&A are no longer supported for rich results.
