Schema.org Rich Result Audit: JSON-LD Structured Data Check
Pricing
from $1.40 / 1,000 page auditeds
Schema.org Rich Result Audit: JSON-LD Structured Data Check
Audit schema.org structured data on any list of pages: JSON-LD, Microdata and RDFa extracted and checked against Google rich result required and recommended properties. Eligible yes/no per type, errors, warnings, raw blocks, optional crawl.
Pricing
from $1.40 / 1,000 page auditeds
Rating
0.0
(0)
Developer
Detroit Web Agent - Open Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Features
Share
Schema Markup Validator
Give it page URLs, or let it crawl a site, and see for each page which Google rich results its schema.org markup is eligible for. It extracts JSON-LD, Microdata and RDFa, checks each item against the required and recommended properties in Google Search Central, and lists exact errors and warnings with the raw blocks. It uses plain HTTP: no browser and no login.
What data you get
- Verdict per page:
auditStatus(valid, valid-with-warnings, has-errors, no-rich-result-types, no-structured-data) and a 0-100auditScore - Per rich-result item: feature,
@type, name, source format, eligible yes/no, missing required and recommended properties, errors, warnings, notes - Types: every schema.org type found, which ones Google uses for rich results, eligible and ineligible lists
- Raw markup: JSON-LD blocks, Microdata items and RDFa items as JSON, plus JSON-LD syntax errors
- Fetch facts: final URL, HTTP status, response time, crawl depth, noindex flag
Use cases
- Audit a client's product, recipe, article and local business pages and hand over an exact fix list
- Re-run on a schedule after each release and catch templates that lose Product, Article or breadcrumb eligibility
- Inventory which schema.org types and formats competitors use across a crawl of their site
How it works
- Each URL is fetched over HTTPS with a desktop browser user agent, following up to 10 redirects. Non-HTML answers are skipped.
- JSON-LD (including
@graphand arrays), Microdata (itemscope,itemprop,itemref) and schema.org RDFa (typeof,property) are parsed into one model.@idreferences are resolved across blocks. - Each rich-result candidate (top-level items and nested ones such as
mainEntity, list items,aggregateRatingandreview) is checked with rules per Google feature: required properties, recommended properties, ISO 8601 dates and durations, schema.org enum values, absolute URLs, rating ranges and expiry dates. - Optional crawl: set
maxPagesPerSiteand the actor follows same-site links up tomaxCrawlDepth, honoring robots.txt.
Checked features: Product (and ProductGroup), Offer, AggregateRating, Review, Article / NewsArticle / BlogPosting, BreadcrumbList, FAQPage, HowTo, LocalBusiness and its subtypes (Restaurant, Store, Dentist, Hotel and 100+ more), Organization, Event, Recipe, JobPosting, VideoObject and SoftwareApplication (including MobileApplication and WebApplication).
Input
| Field | What it does | Default |
|---|---|---|
urls | Page URLs to audit, one per line (up to 5,000). | required |
maxPagesPerSite | 0 audits only the listed URLs. Above 0, also crawls same-site links up to this many pages per site (max 500). | 0 |
maxCrawlDepth | How many clicks away from a start URL the crawl may go (1-5). | 2 |
onlyWithStructuredData | Leave pages without any markup out of the results (they are not charged). | false |
maxUrls | Upper limit of pages audited in one run. | 1000 |
requestTimeoutSecs | Time limit per page (3-60 seconds). | 15 |
maxConcurrency | Pages fetched at the same time (1-25). | 10 |
includeRawBlocks | Keep raw JSON-LD, Microdata and RDFa in each row. Turn off for a flat CSV. | true |
proxyConfiguration | Optional Apify Proxy for sites that refuse cloud IPs. | off |
Example input
{"urls": ["https://www.bbcgoodfood.com/recipes/easy-pancakes", "https://www.allbirds.com/products/mens-tree-runners"],"maxPagesPerSite": 0,"requestTimeoutSecs": 15}
Output
One dataset row per audited page. The Audit view shows verdict, score and eligible types; Issues shows every error and warning; Fetch status shows status codes, crawl depth and what was charged. Export as JSON, CSV, Excel or HTML, or read through the API. A run summary (pages audited, eligible items by type, errors by code) is saved as the OUTPUT record.
Sample output
Trimmed row (raw blocks shortened):
{"url": "https://www.bbcgoodfood.com/recipes/easy-pancakes","statusCode": 200,"ok": true,"billed": true,"pageTitle": "Easy pancakes recipe | Good Food","auditStatus": "valid-with-warnings","auditScore": 98,"formats": ["json-ld"],"jsonLdBlockCount": 4,"typesFound": ["VideoObject", "Recipe", "ImageObject", "WebPage", "Person", "Organization", "NutritionInformation", "HowToStep", "BreadcrumbList", "ListItem", "AggregateRating"],"eligibleTypes": ["VideoObject", "Recipe", "BreadcrumbList", "AggregateRating"],"ineligibleTypes": [],"errorCount": 0,"warningCount": 3,"warnings": ["VideoObject \"How to make perfect pancakes\": Missing recommended property description", "Recipe \"Easy pancakes\": Missing recommended property aggregateRating", "..."],"richResults": [{"feature": "Recipe", "type": "Recipe", "source": "json-ld", "name": "Easy pancakes", "eligible": true, "errors": [], "missingRequired": [], "missingRecommended": ["aggregateRating", "video"]}],"summary": "11 type(s) in json-ld; 4 rich-result item(s): eligible VideoObject, Recipe, BreadcrumbList, AggregateRating; 0 error(s), 3 warning(s).","rawJsonLd": [{"@context": "https://schema.org", "@type": "VideoObject", "name": "How to make perfect pancakes"}],"fetchedAt": "2026-11-08T06:01:48.325Z"}
Typical errors it reports: Product needs at least one of offers, review or aggregateRating, Invalid offers.price "$19.99": use a plain number with a dot decimal, no currency symbol or thousands separator, Invalid date in startDate: "March 3" (use ISO 8601, e.g. 2026-03-01 or 2026-03-01T09:00:00-05:00), validThrough is in the past: the job has expired and should be removed or updated, Missing required property itemListElement (found "ItemListElement"; property names are case-sensitive).
Pricing
Pay per event, no monthly fee:
- Page audited: $0.0014 per page fetched and audited ($1.40 per 1,000 pages).
- Actor start: $0.00005 per run.
Pages that time out, answer 4xx/5xx, are not HTML, are blocked by robots.txt in crawl mode, or are skipped by onlyWithStructuredData are never charged. If no input URL is usable the run stops at once with a clear message. Set "Maximum cost per run" in run options to cap spend; the actor stops cleanly at that limit.
Call it from code
Python:
from apify_client import ApifyClientclient = ApifyClient("YOUR_APIFY_TOKEN")run = client.actor("transparent_meteorite/schema-org-rich-result-audit").call(run_input={"urls": ["https://www.bbcgoodfood.com/recipes/easy-pancakes"]})for row in client.dataset(run["defaultDatasetId"]).iterate_items():print(row["url"], row["auditStatus"], row["auditScore"])
cURL (starts a run and waits for the rows):
$curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~schema-org-rich-result-audit/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" -H "Content-Type: application/json" -d '{"urls": ["https://www.bbcgoodfood.com/recipes/easy-pancakes"]}'
The actor also works as a tool for AI agents through the Apify MCP server (https://mcp.apify.com), using the same input.
FAQ
Is this the same as Google's Rich Results Test? It applies the same published property rules, in bulk and with a crawl. Google also weighs site quality and policy, so eligible means the markup qualifies, not that Google will always show the result.
Why is HowTo never eligible? Google retired HowTo rich results. FAQ rich results are shown only for well-known government and health sites; the actor validates FAQPage and adds a note.
Does it run JavaScript? No. It reads the server HTML, as most crawlers do on first pass. Markup injected only by client-side scripts is not seen.
Why did a page return 403? Some sites refuse cloud IPs. Turn on Apify Proxy and retry. The actor does not bypass captchas or logins; those pages come back as errors and are not charged.
Limits
- Up to 5,000 pages per run, 500 per site in crawl mode; 2 MB of HTML per page.
- Only public http(s) URLs; localhost and private IP ranges are refused.
- RDFa is read for schema.org vocabulary only. Raw blocks are capped at 100 KB per row (
rawTruncatedtells you). - Rules follow Google Search Central documentation as of November 2026.
Related actors
- Technical SEO Page Audit: titles, headings, canonicals and indexability for the same pages.
- Sitemap Link Inventory: pull every URL from a site's sitemaps, then audit them here.
- Website Tech Stack Detector: see which CMS or e-commerce platform produced the markup.