Schema Markup
Schema markup describes page content in a structured format. Supported types can help establish eligibility for search features.
Ludwig Makhyan · Founder, WebsiteCoach ·
Jump to section
Executive Overview
Use accurate JSON-LD that matches visible content, then validate syntax and the properties of the intended type.
Business Impact
Structured data does not guarantee rich results or AI citations. Google does not require special schema for inclusion in its AI features.
Source: WebsiteCoach parses JSON-LD, Microdata, and RDFa from your homepage HTML.
Schema Types Explained
- JSON-LD, Microdata & RDFa detection
- Identify structured-data formats in the page. Inspect the parsed values as well as the presence of a script or attribute.
- Schema types identified
- Choose types that match visible content. A detected type does not automatically have a supported Google rich-result feature.
- Required properties validated per type
- Check syntax and the properties required for the intended feature. Validate against its current documentation.
- Missing recommended types flagged
- A suggested type is an opportunity only when it describes actual page content; it is not a mandatory ranking requirement.
- Organization schema check
- Describe the real organization with a consistent name and URL. Avoid invented identities, credentials, or reviews.
- WebSite & BreadcrumbList check
- WebSite identifies the site; BreadcrumbList describes page hierarchy. Use working canonical URLs and accurate labels.
Role-Specific Action Plan
- →Audit existing schema using WebsiteCoach or Google's Rich Results Test
- →Implement Organization and WebSite schema on the homepage in JSON-LD format
- →Add BreadcrumbList to all category and product pages
- →Use accurate JSON-LD that matches visible content, then validate syntax and the properties of the intended type.
- →Inject JSON-LD in a <script type='application/ld+json'> tag in the <head>
- →Validate schema with Google's Rich Results Test after deployment
- →Avoid Microdata or RDFa for new implementations — JSON-LD is Google's preference
- →Write useful visible questions and answers; keep any structured data consistent with them
- →Ensure article publish dates are accurate and included in Article schema
- →Structured data does not guarantee rich results or AI citations. Google does not require special schema for inclusion in its AI features.
- →Monitor Google Search Console for rich result eligibility reports
How to implement JSON-LD
- Choose a type that describes the visible page. Use an Article for an article, not a Product simply to seek a different search appearance.
- Provide truthful page-specific values and absolute URLs. Keep the title, dates, author, and images consistent with what readers see.
- Add the JSON-LD script to the page and check both the source and rendered HTML for conflicting duplicates.
- Run the Schema Markup Validator for vocabulary checks and Google's Rich Results Test for Google-supported features. Test the live URL after deployment.
Example: Article structured data
This fictional example demonstrates the structure. Replace every example value with real information that is visible on your page; it is not a statement that this article or organization exists.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to validate HTML",
"mainEntityOfPage": "https://example.com/guides/html-validation",
"datePublished": "2026-09-01",
"dateModified": "2026-09-07",
"author": { "@type": "Organization", "name": "Example Publishing", "url": "https://example.com/about" },
"image": ["https://example.com/images/html-validation.jpg"]
}
</script>Why valid markup may not produce a rich result
Structured data is not required for inclusion in Google's AI features and does not guarantee citations or a ranking improvement. Keep useful questions and answers visible for readers without promising FAQ or HowTo search enhancements.
| Check | What to do |
|---|---|
| Invalid JSON | Remove trailing commas and use double quotes. Validate syntax before examining individual properties. |
| Missing or inappropriate properties | Read the documentation for the selected type and supported Google feature. |
| Markup differs from visible content | Correct the underlying content and structured data together. Never add invented reviews or authors. |
| Page is not indexable | Check its HTTP status, robots directives, canonical, and Search Console URL Inspection. |
| No enhanced search appearance | Eligibility does not guarantee display. Not every Schema.org type has a Google rich-result feature. |
Frequently asked questions
What is Schema Markup?
Schema markup describes page content in a structured format. Supported types can help establish eligibility for search features.
Why does Schema Markup matter?
Structured data does not guarantee rich results or AI citations. Google does not require special schema for inclusion in its AI features.
Official references
Related topics