Schema Markup Extractor & Validator - JSON-LD, Open Graph

Extract all structured data and metadata from a list of pages in one pass: JSON-LD (including @graph), Microdata, Open Graph, Twitter Card, title, meta description/robots, canonical, lang and hreflang. Each page also gets a rich-result readiness check: for common schema.org types (Product, Offer, Article, LocalBusiness, Event, FAQPage, Recipe, JobPosting, VideoObject...) we list missing recommended fields and give a 0-100 score.

$0.00097 per page (1,000 pages = $0.97), no start fee. Pages that fail are free.

Why this one

• Everything in one pass per page: JSON-LD (including @graph), microdata, Open Graph, Twitter Card, meta tags, canonical, lang and hreflang, instead of running several tools.
• Tells you what to fix, not just what exists. Each page gets a check per schema.org type (Product, Offer, Article, FAQ, LocalBusiness, Event and more) that lists the missing recommended fields, plus a richResultScore.
• Built for whole sites: feed it a URL list (for example from a sitemap) and get one row per page with issues[], so template problems show up across hundreds of pages at once.
• Failed pages are free; no start fee.

Quick start: example input, output and cost

Bulk extract JSON-LD, microdata, Open Graph and Twitter Cards with rich-result readiness checks per schema.org type. Pay per page, failed pages free.

Example input

{
  "urls": [
    "https://blog.apify.com/"
  ]
}

Cost example: 1,000 pages x $0.00097 = $0.97.

Use cases

• SEO audits of product or article templates before a release.
• Competitor research: which schema types and fields do they use?
• Link-preview QA (og:title / og:image present?).
• Feed a URL list from our Sitemap URL Extractor to audit a whole site.

Output (one item per page)

url, finalUrl, title, canonical, lang, meta, openGraph, twitterCard, hreflang, schemaTypes, jsonLd, microdata, issues[], richResultScore.

The checks are our own pragmatic reading of schema.org and public rich-result guidelines. They do not guarantee rich results; search engines decide.

Limits

• It reads the HTML the server sends (no browser), so text, links or markup added later by JavaScript are not seen.
• It reports what is on the page and flags broken JSON-LD. It is not Google's Rich Results Test and cannot promise rich results.

Privacy and responsible use

Person nodes (authors, reviewers) are reduced to {"@type": "Person"}, and emails and phone numbers are redacted by default. Social networks and profile sites are not processed. We follow robots.txt (RFC 9309), make about one request per second per site, use an honest User-Agent (SchemaReader/1.0), and never log in or bypass bot protection.

Event	Price
Page extracted	$0.00097

Maintained by DigiVibeTech. Questions or bugs: use the Issues tab; we reply within 2–5 business days.