Schema.org for Marketers
Structured data without an engineering team. Common types, examples, validation steps.
What this is
An eight-page guide to implementing structured data (Schema.org) without needing a developer. Covers the schema types that actually impact search visibility, with copy-paste JSON-LD examples and step-by-step validation instructions.
Written for marketers and content managers who know structured data matters but haven’t implemented it because the documentation feels like it was written for engineers (because it was).
Why structured data matters
Structured data is how you tell Google what your content is, not just what it says. It’s the difference between Google guessing that your page is a recipe and Google knowing it — and displaying star ratings, cook time, and calorie count directly in search results.
Pages with rich results get 20–30% higher click-through rates on average. That’s free traffic for 30 minutes of markup work.
The schema types that matter
1. LocalBusiness / ProfessionalService
Use when: You have a physical location or serve a specific area
{
"@context": "https://schema.org",
"@type": "ProfessionalService",
"name": "Your Business Name",
"telephone": "+91-XXXXXXXXXX",
"address": {
"@type": "PostalAddress",
"streetAddress": "Your Street",
"addressLocality": "Mumbai",
"addressRegion": "Maharashtra",
"postalCode": "400001",
"addressCountry": "IN"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "19.0760",
"longitude": "72.8777"
},
"openingHoursSpecification": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "10:00",
"closes": "18:00"
}
}
Rich result: Knowledge panel, Google Maps listing, opening hours in search.
2. Article / BlogPosting
Use when: You publish blog posts, articles, or news
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Your Article Title",
"description": "A short description",
"author": {
"@type": "Person",
"name": "Author Name"
},
"datePublished": "2026-06-01",
"image": "https://yoursite.com/image.jpg"
}
Rich result: Article carousel, author attribution, date in SERP snippet.
3. FAQPage
Use when: Your page has a clear Q&A structure
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What does your service cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Our services start at ₹X per month."
}
}
]
}
Rich result: Expandable FAQ snippets directly in search results (extra SERP real estate).
4. Product / Offer
Use when: You sell products or services with clear pricing
Rich result: Price, availability, and review stars in search.
5. HowTo
Use when: Your content is a step-by-step guide
Rich result: Step numbers and images in search results.
6. BreadcrumbList
Use when: Always — every site benefits from breadcrumb markup
Rich result: Breadcrumb trail replaces the raw URL in search snippets.
7. Person
Use when: Personal brands, authors, speakers
Rich result: Knowledge panel, author association with articles.
How to implement (without a developer)
Method 1: Paste into your CMS
Most CMS platforms (WordPress, Webflow, Shopify) let you add custom code to the <head> section. Paste your JSON-LD there.
Method 2: Use Google Tag Manager
Create a Custom HTML tag with your JSON-LD wrapped in <script type="application/ld+json"> tags. Fire on the relevant pages.
Method 3: Use a WordPress plugin
Rank Math and Yoast both generate schema automatically. But verify the output — plugins often miss fields or use incorrect types.
Validation workflow
- Write your JSON-LD using the templates above
- Test with Google’s Rich Results Test — paste your URL or code snippet
- Check for errors and warnings — errors must be fixed; warnings are optional but recommended
- Deploy to production
- Monitor in Search Console — Enhancements > [Schema type] shows detection status and errors
- Wait 2–4 weeks for Google to recrawl and start showing rich results
Common mistakes
- Using schema types Google doesn’t support for rich results. Schema.org has hundreds of types; Google only renders rich results for ~30 of them. This guide only covers the ones that produce visible SERP changes.
- Self-serving reviews. Don’t add
AggregateRatingmarkup from your own testimonials page — Google may issue a manual action. Use third-party review platforms. - Invisible content. The content in your schema must also appear visibly on the page. Markup-only content (not visible to users) violates Google’s guidelines.
- Wrong @type. Using
Articlewhen you meanBlogPosting, orLocalBusinesswhenProfessionalServiceis more accurate. Be specific.
Version history
| Version | Date | Notes |
|---|---|---|
| 2.0 | May 2026 | Updated for latest Google rich result support, added HowTo and Person |
| 1.0 | October 2025 | Initial release |