Schema Markup Validator: Structured Data & Rich Results Checker (Bulk)

Check the structured data on hundreds of pages in one run. Paste page URLs or a sitemap and get one row per page with every JSON-LD, Microdata and RDFa item found, the rich results each page is eligible for, the errors and warnings to fix, duplicate items, broken JSON-LD blocks, and Open Graph and Twitter/X card problems. A final summary row adds it all up across the site.

Rules follow the required and recommended properties documented in Google Search Central's structured data guides and the official schema.org vocabulary. This is not Google's official tool and it does not call any Google service. Use Google's Rich Results Test to confirm individual pages.

What does this schema markup validator do?

• Extracts all three syntaxes: JSON-LD (including @graph, nodes merged by @id across blocks), Microdata (itemscope, itemprop, itemref) and RDFa Lite (vocab, typeof, property).
• Checks rich-result requirements for Product (product snippets and merchant listings), Offer and AggregateOffer, Review, AggregateRating, Article / NewsArticle / BlogPosting, BreadcrumbList, FAQPage, HowTo, LocalBusiness and its subtypes, Organization, Event, Recipe, JobPosting and VideoObject.
• Checks values, not just presence: ISO 8601 dates and durations, prices without currency symbols, 3-letter currency codes, schema.org availability and event status values, rating ranges, expired job postings, past events, breadcrumb positions, time zones.
• Checks the schema.org vocabulary: unknown types and properties (with "did you mean" suggestions), properties used on the wrong type, superseded properties, missing @context, retired data-vocabulary.org markup.
• Finds duplicates: the same item marked up twice (for example in JSON-LD and Microdata), or two items with the same name and different content.
• Reports parse errors: invalid JSON-LD with the HTML line number and the JSON error position; blocks with trailing commas are still read and flagged.
• Checks link previews: Open Graph (og:title, og:type, og:image, og:url, absolute URLs, og:url vs canonical) and Twitter/X cards (card type, title, image, player and app tags).
• Adds one summary record with rich-result counts, pages with errors, the most common errors and warnings, and pages that could not be checked.

Who uses it?

• SEO agencies and consultants auditing a client's schema markup across a whole site, not one URL at a time.
• E-commerce teams checking product, offer and review markup before and after a theme or platform change.
• Publishers checking Article, Video and Breadcrumb markup on new templates.
• Developers and QA running a scheduled check so a release does not silently break structured data.

How to use it

1. Click Try for free (or Start).
2. Paste Page URLs, or a Sitemap URL (sitemap indexes and .xml.gz work), and set Maximum pages.
3. Run it. Open the Overview table, sort by Schema errors, or download JSON, CSV or Excel.
4. Read the last row (recordType: "summary") for the site-wide picture. The same summary is saved as the key-value store record SUMMARY.

Input example

{
  "urls": [
    "https://www.bbcgoodfood.com/recipes/easy-pancakes",
    "https://en.wikipedia.org/wiki/Schema.org"
  ],
  "sitemapUrl": "https://www.example.com/sitemap.xml",
  "maxPages": 200,
  "checkSocialTags": true,
  "includeExtractedData": false,
  "onlyPagesWithIssues": false
}

Field	Description
urls	Pages to check
sitemapUrl	Optional XML/text sitemap or sitemap index; its pages are added up to maxPages
maxPages	Total page limit (default 100)
checkSocialTags	Open Graph and Twitter/X card checks (default on)
includeExtractedData	Add the full extracted items as JSON to each row
onlyPagesWithIssues	Save only pages with errors or warnings (others are not charged)
maxConcurrency	Pages at once, 1-10 (default 5)

Output example

One page row (shortened):

{
  "recordType": "page",
  "url": "https://www.bbcgoodfood.com/recipes/easy-pancakes",
  "httpStatus": 200,
  "title": "Easy pancakes recipe | Good Food",
  "hasStructuredData": true,
  "syntaxes": { "jsonLd": 3, "microdata": 0, "rdfa": 0 },
  "types": ["VideoObject", "Recipe", "BreadcrumbList"],
  "eligibleRichResults": ["Breadcrumb", "Recipe", "Video"],
  "invalidRichResults": [],
  "structuredDataErrorCount": 0,
  "structuredDataWarningCount": 3,
  "errors": [],
  "warnings": [
    "[schema.org] VideoObject \"How to make perfect pancakes\" (JSON-LD): \"customPosterUrl\" is not a schema.org property (on VideoObject)",
    "[Video] VideoObject \"How to make perfect pancakes\" (JSON-LD): Missing recommended field (\"description\")",
    "[Recipe] Recipe \"Easy pancakes\" (JSON-LD): Missing recommended field (\"video\")",
    "[Twitter card] Should be an @username, got \"Good Food\" (\"twitter:site\")"
  ],
  "richResults": [
    { "feature": "Recipe", "itemType": "Recipe", "name": "Easy pancakes", "syntax": "JSON-LD", "valid": true, "errors": [], "warnings": ["Missing recommended field (\"video\")"] }
  ],
  "duplicates": [],
  "parseErrors": [],
  "openGraph": { "present": true, "errors": [], "warnings": [] },
  "twitterCard": { "present": true, "card": "summary_large_image", "errors": [], "warnings": ["Should be an @username, got \"Good Food\" (\"twitter:site\")"] }
}

Errors on a broken product page look like this:

[Merchant listing] Product "Widget" (JSON-LD): Invalid price "$19.99": use a plain number such as 39.99 (no currency symbol or thousands separator) ("offers.price")
[Product snippet] Product "Widget" (JSON-LD): Either "ratingCount" or "reviewCount" should be specified ("aggregateRating")
[JSON-LD parse] block 3 (HTML line 13): Invalid JSON: Expecting property name enclosed in double quotes (line 1, column 60 of the block); the block cannot be read

The summary row has pagesChecked, pagesFailed and failedPages (with reasons), pagesWithStructuredData, pagesWithStructuredDataErrors, pagesWithParseErrors, pagesWithDuplicates, typePages, richResults (valid / invalid page counts per feature), topErrors, topWarnings and Open Graph / Twitter totals.

Errors vs warnings. An error is a missing required property or an invalid value that makes the item ineligible for that rich result. A warning is a missing recommended property or a value worth fixing that does not block eligibility.

How much does it cost?

You pay per page checked: $1.50 per 1,000 pages ($0.0015 per page), plus one result for the summary row. Pages that fail to load, are blocked by robots.txt or return an error are not charged; they are listed in the summary.

• 3 pages (the default run): about $0.006
• 500 pages from a sitemap: about $0.75
• 10,000 pages: about $15

Volume discounts on higher Apify plans. The prices above are for the Apify Free plan. On paid plans the per-result price drops automatically: about 15% lower on Bronze, 25% lower on Silver and 38% lower on Gold and above.

Use it via API, Make, Zapier, n8n or an AI agent

Apify API. Start a run and get the results back in one HTTP request (replace YOUR_API_TOKEN with the token from Apify Console > Settings > Integrations):

curl -X POST "https://api.apify.com/v2/acts/plotpointtech~schema-markup-validator/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["https://www.bbcgoodfood.com/recipes/easy-pancakes"]}'

For longer jobs, start the run asynchronously and read the dataset when it finishes. Official apify-client libraries exist for Python and JavaScript; the API tab on this page has ready-made code.

No-code automation. Connect the tool to Make, Zapier, n8n, Google Sheets, Slack, Airtable or any webhook with Apify integrations, and use Schedules in Apify Console to re-check your templates daily or weekly.

AI agents (MCP). Give Claude, ChatGPT, Cursor, VS Code or any MCP-compatible agent direct access to this tool through the hosted Apify MCP server. Add this server URL to your client:

https://mcp.apify.com?tools=plotpointtech/schema-markup-validator

FAQ

Is this Google's Rich Results Test? No. It applies the required and recommended properties that Google documents publicly, plus schema.org vocabulary checks. Google may apply extra quality and policy checks, and showing a rich result is always at Google's discretion. Confirm important pages with Google's own tools.

Does it run JavaScript? No. It reads the HTML the server returns, which is where most structured data lives. Markup injected only by JavaScript (for example by a tag manager) will not be seen; those pages show hasStructuredData: false.

Why is FAQ or How-to not counted as eligible? Google limited FAQ rich results to well-known government and health sites in 2023 and stopped showing How-to rich results. The markup is still checked and a note explains this.

Is it legal to use? It is meant for checking your own websites and your clients' websites. It reads ordinary public pages, obeys robots.txt (including Crawl-delay), identifies itself with a contact address, spaces out requests to each site, and does not log in or bypass blocking. You are responsible for having the right to check the URLs you submit.

Plot Point Technologies is not affiliated with Google, schema.org, the Open Graph protocol or X Corp.

Related tools from Plot Point Technologies

• SEO Audit Crawler - Titles, Meta, H1, Broken Pages & Links: on-page SEO check of every page in a website's sitemap.
• Website Tech Stack Detector: CMS, ecommerce, analytics, pixels and hosting of any website.
• Website Screenshot & PDF API: full-page PNG, JPEG or PDF captures of any web page.
• Website to Markdown Crawler: any website as clean Markdown for LLMs and RAG.

---

If this tool saved you time, we would be grateful for a short review on this page; it helps other people find it. If something did not work as expected, please open an issue on the Issues tab and we will look into it quickly.