Schema.org Validator API | JSON-LD + Microdata

Crawl and validate JSON-LD and Microdata structured data across multiple pages. Detect missing, malformed, or incomplete Schema.org markup at scale.

Store Quickstart

• Start with store-input.example.json to validate the score and error model on two public pages.
• If that matches your SEO workflow, switch to store-input.templates.json and pick one of:
• Quickstart (Dataset) for a fast first run
• Batch Validation for multi-page audits
• Webhook Alert for automated markup checks

The Store example uses two stable URLs so first-time users get a deterministic success before scaling out.

What does this actor do?

Fetches HTML pages, extracts JSON-LD (<script type="application/ld+json">) and Microdata (itemscope/itemtype) blocks, then validates them against Schema.org best practices. Each page gets a quality score (0-100) and grade (A-F).

Key Features

• 🔍 JSON-LD + Microdata extraction — Both formats supported
• 📊 Quality scoring — 0-100 with A-F grade per page
• ⚠️ Error detection — Missing @type, invalid JSON, missing @context
• 💡 Warnings — Sparse data, missing recommended properties
• 📋 Bulk processing — Check up to 200 URLs per run
• 🪝 Webhook delivery — Integrate into SEO monitoring workflows

Validation Rules

Check	Points	Description
JSON-LD present	40	At least one valid JSON-LD block
Microdata present	20	itemscope/itemtype found
No errors	20	No parse errors or missing @type
Schema.org context	10	Proper @context with schema.org
Rich data	10	5+ properties in JSON-LD

Input Example

{
  "urls": ["https://www.google.com", "https://github.com", "https://schema.org"],
  "concurrency": 3
}

Output Example

{
  "url": "https://www.google.com",
  "jsonLd": [
    { "type": "WebSite", "context": "https://schema.org", "name": "Google", "_keyCount": 7 }
  ],
  "microdata": [],
  "errors": [],
  "warnings": [],
  "score": { "total": 80, "grade": "A" }
}

A fuller ready-to-share payload is available in sample-output.example.json for Store and README proof.

Cost

Zero external costs. Simple HTTP page fetches — no API keys, no proxies, no browser. A run checking 50 URLs takes ~20 seconds.

Commercial Ops

Set up .env first:

$cp -n .env.example .env

Cloud Task/Schedule setup (idempotent):

$npm run apify:cloud:setup

Daily reliability checks:

npm run canary:check
npm run contract:test:live

OpenClaw cron commands:

• openclaw-cron-commands.md

Related actors

• sitemap-analyzer — find URLs and templates first, then validate schema at scale.
• robotstxt-ai-checker — compare crawl policy and schema hygiene in the same audit pass.
• ai-visibility-monitor-actor — measure whether schema improvements correlate with visibility changes.