Schema.org for Marketers

What this is

An eight-page guide to adding structured data (Schema.org) without a developer. It covers the schema types that affect how you show up in search, with copy-paste JSON-LD examples and step-by-step validation instructions.

I wrote it for marketers and content managers who know structured data matters but haven’t added it, because the documentation reads like it was written for engineers (it was).

Why structured data matters

Structured data tells Google what your content is, on top of what it says. Without it, Google has to guess that your page is a recipe. With it, Google knows, and can show star ratings, cook time and calorie count right in the search results.

Pages with rich results get 20–30% higher click-through rates on average, which is free traffic for about 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. Check what they output, though, because plugins often miss fields or use the wrong types.

Validation workflow

1. Write your JSON-LD using the templates above.
2. Test it with Google’s Rich Results Test by pasting in your URL or code snippet.
3. Check for errors and warnings. Errors must be fixed; warnings are optional, but I’d fix them too.
4. Deploy to production.
5. Monitor it in Search Console, where Enhancements > [Schema type] shows detection status and errors.
6. 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, and Google only renders rich results for ~30 of them. This guide covers only the ones that change what people see in search.
• Self-serving reviews. Don’t add AggregateRating markup from your own testimonials page, because Google may issue a manual action. Use third-party review platforms.
• Invisible content. Anything in your schema must also be visible on the page. Markup-only content that users can’t see violates Google’s guidelines.
• Wrong @type. Using Article when you mean BlogPosting, or LocalBusiness when ProfessionalService is 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