SchemaPaid

Content-Type Schemas

Validates that your schema markup matches your actual content type and checks for completeness of type-specific required fields.

Why It Matters for AI Visibility

Different content types demand different schema markup. A recipe page needs Recipe schema with ingredients and cook times. A product page needs Product schema with pricing and availability. A tutorial needs HowTo schema with step-by-step instructions. When you use the wrong schema -- or none at all -- AI engines cannot properly classify your content for the right queries. ChatGPT and Perplexity handle content types differently at the response level. A how-to query returns step-by-step results. A product query returns pricing comparisons. A recipe query returns ingredient lists and cooking times. Google AI Overviews use schema type to determine which rich format to display. If your tutorial page lacks HowTo schema, it competes as generic content instead of being served as a structured, extractable tutorial. This factor goes beyond basic Article, FAQ, and Organization schemas (which have their own dedicated factors) to cover six specialized content types that most sites overlook entirely: HowTo, Product, Review, Event, Recipe, and VideoObject.

How We Score It

The analyzer scans your page for signals matching six content types. Tutorial language like "step-by-step" or "how to" triggers HowTo detection. Pricing and "add to cart" triggers Product detection. Only content types with detected signals are scored -- if your page has no recipe signals, Recipe schema is not expected. For each relevant content type, required field completeness earns up to 1.5 points and optional fields earn up to 1 point. A 2-point penalty applies for each content type that is detected in your content but has no matching schema at all. If no specialized content types are detected on the page, you receive a neutral score of 5. The total is normalized to a 0-10 scale. Scores of 7 or higher pass, 4-6 are partial, and 0-3 fail.
See how your site scores on this factorAnalyze My Site

How to Improve

  • 1

    Add HowTo schema for tutorial and guide content

    If your page contains step-by-step instructions, add HowTo schema with `name` and `step` fields (an array of HowToStep objects). Include optional fields like `totalTime` and `tool` for a stronger score. This makes your tutorial directly extractable by ChatGPT and Perplexity when users ask "how to" questions.

  • 2

    Add Product schema for e-commerce pages

    Any page with pricing, "add to cart" buttons, or product descriptions needs Product schema. Include the required `name` field plus `offers` (with price and availability), `image`, and `aggregateRating`. Without this, AI engines see product signals but cannot extract structured product data.

  • 3

    Add Recipe schema for food content

    Pages with ingredient lists and cooking instructions should have Recipe schema with `name` and `recipeIngredient` as required fields. Add `cookTime`, `prepTime`, and `recipeInstructions` for full coverage. Google AI Overviews use Recipe schema to populate rich recipe cards directly in search results.

  • 4

    Add VideoObject schema for embedded video

    If your page embeds YouTube, Vimeo, or native `<video>` elements, add VideoObject schema with `name`, `uploadDate`, and `thumbnailUrl`. Include a `transcript` field for maximum AI extractability -- transcripts let AI engines index and quote your video content as text.

  • 5

    Audit page content against existing schema types

    The analyzer detects content signals and checks for matching schema. If your page has product signals but no Product schema, you receive a 2-point penalty per missing type. Run your page through the analyzer, check which content types were detected, and ensure every detected type has corresponding structured data.

Before & After

Before
Page titled "How to Set Up Docker" with step-by-step instructions.
No HowTo schema present. Content signals detected, schema missing.
Score: penalty applied for detected but unmatched content type.
After
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Set Up Docker",
  "step": [
    {"@type": "HowToStep", "text": "Install Docker Desktop from docker.com"},
    {"@type": "HowToStep", "text": "Run docker --version to verify installation"},
    {"@type": "HowToStep", "text": "Pull your first image with docker pull nginx"}
  ],
  "totalTime": "PT15M"
}
Before
Page shows "$29.99/month", "Add to Cart" button, product features.
No Product schema. Analyzer detects product signals, applies penalty.
After
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Pro Plan",
  "description": "Professional project management for teams",
  "image": "https://example.com/product.jpg",
  "offers": {
    "@type": "Offer",
    "price": "29.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

Code Examples

HowTo schema template

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Set Up Docker",
  "step": [
    {"@type": "HowToStep", "text": "Install Docker Desktop"},
    {"@type": "HowToStep", "text": "Verify installation"},
    {"@type": "HowToStep", "text": "Pull your first image"}
  ]
}

Recipe schema template

{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Classic Banana Bread",
  "recipeIngredient": ["3 bananas", "1/3 cup butter", "1 cup sugar"],
  "recipeInstructions": "Preheat oven to 350F. Mash bananas...",
  "cookTime": "PT60M",
  "recipeYield": "1 loaf"
}

Frequently Asked Questions

What if my page does not match any of the 6 content types?

You receive a neutral score of 5. This factor only applies when content signals are detected -- product pricing, recipe ingredients, tutorial steps, and so on. Pages without these signals are not penalized.

How is this different from the Schema Validation factor?

Schema Validation checks that your existing schemas have correct fields (required and recommended). Content-Type Schemas checks whether the right schema types exist for your content. Validation catches errors in what you have; this factor catches gaps in what is missing.

Does the analyzer detect custom schema types?

No. It checks for six specific types: HowTo, Product, Review, Event, Recipe, and VideoObject. Base types like Article, FAQ, Organization, and BreadcrumbList are checked by their own dedicated factors.

Related Factors

Check Your GEO Score

Run a free analysis on your website and see how you score across all 52 factors.

Analyze My Site