# Schema.org Extractor & Validator (`ib4ngz/schema-org-extractor-validator`) Actor Extract and validate Schema.org JSON-LD, Microdata, and RDFa from HTML pages. - **URL**: https://apify.com/ib4ngz/schema-org-extractor-validator.md - **Developed by:** [Iqbal R](https://apify.com/ib4ngz) (community) - **Categories:** Automation, Developer tools, SEO tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $3.50 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### What does Schema.org Extractor & Validator do? **Schema.org Extractor & Validator** finds and validates [Schema.org](https://schema.org/) structured data on public web pages. It supports JSON-LD, Microdata, and RDFa and returns clear, consistent results for every analyzed URL. Use it for technical SEO audits, catalog quality checks, website monitoring, and data enrichment. On Apify, results are available through the Console, API, schedules, integrations, and downloadable datasets. ### Why use Schema.org Extractor & Validator? - Audit structured data across a list of pages or a shallow site crawl. - Find malformed JSON-LD without losing valid blocks from the same page. - Detect misspelled or unknown Schema.org types and properties. - Normalize three markup formats into one API-friendly model. - Monitor structured-data changes through scheduled Apify runs. - Feed stable page-level results into analytics, QA, enrichment, or Website Intelligence APIs. ### How to use Schema.org Extractor & Validator 1. Open the Actor in Apify Console and select the **Input** tab. 2. Add one or more HTTP or HTTPS URLs. 3. Keep **Maximum crawl depth** at 0 to analyze only those URLs, or increase it to follow links. 4. Choose which structured-data formats and warning details to include. 5. Click **Start**. 6. Open the **Dataset** result to review page validity, formats, types, issues, and normalized items. ### Input The Input tab supports the following fields: | Field | Default | Description | | --------------------- | --------: | ----------------------------------------------------------------- | | `startUrls` | Apify.com | One or more public HTTP(S) URLs. | | `maxRequestsPerCrawl` | `100` | Total page limit; never lower than the number of supplied URLs. | | `maxCrawlDepth` | `0` | 0 = supplied URLs only; 1 = one discovered level; and so on. | | `sameDomainOnly` | `true` | Keep discovered links on the originating hostname. | | `proxyConfiguration` | Disabled | Configure Apify Proxy groups/country or custom proxy URLs. | | `includeJsonLd` | `true` | Extract `application/ld+json` scripts. | | `includeMicrodata` | `true` | Extract Schema.org `itemscope` / `itemprop` markup. | | `includeRdfa` | `true` | Extract common Schema.org RDFa markup. | | `includeRaw` | `false` | Include source snippets associated with detected structured data. | | `validate` | `true` | Check detected markup for Schema.org errors and warnings. | | `includeWarnings` | `true` | Include warning details in each result. | | `timeoutSecs` | `30` | Per-request HTTP timeout from 5 to 120 seconds. | Example input: ```json { "startUrls": [{ "url": "https://apify.com/" }], "maxCrawlDepth": 0, "proxyConfiguration": { "useApifyProxy": false }, "validate": true } ``` ### Output The Actor stores one result for each processed page. Every result shows the detected formats and types, validation status, issue counts, and extracted structured-data items. ```json { "url": "https://apify.com/", "finalUrl": "https://apify.com/", "statusCode": 200, "feature": "schema_org", "detected": true, "hasSchema": true, "valid": true, "formats": ["json-ld"], "types": ["Organization"], "summary": { "totalItems": 1, "jsonLdItems": 1, "microdataItems": 0, "rdfaItems": 0, "errors": 0, "warnings": 0, "valid": true }, "items": [ { "format": "json-ld", "type": ["Organization"], "id": null, "data": { "@context": "https://schema.org", "@type": "Organization", "name": "Apify" }, "valid": true, "errors": [], "warnings": [] } ], "errors": [], "warnings": [], "analyzedAt": "2026-08-21T00:00:00.000Z" } ``` You can download the dataset in various formats such as JSON, HTML, CSV, or Excel, or access it programmatically through the Apify API. ### Data table | Field | Meaning | | ------------------------ | ------------------------------------------------------- | | `url` | URL requested by the crawler. | | `finalUrl` | Final URL after redirects. | | `statusCode` | HTTP response status, or `null` when unavailable. | | `detected` / `hasSchema` | Whether at least one normalized item was found. | | `valid` | True when no generated issue has `error` severity. | | `formats` | Structured-data formats found on the page. | | `types` | Schema.org types found on the page. | | `summary` | Format counts and generated issue totals. | | `items` | Normalized entities with item-level validation details. | | `errors` / `warnings` | Page-level parsing, HTTP, or extraction issues. | | `analyzedAt` | ISO 8601 analysis timestamp. | ### How much does it cost to validate Schema.org markup? Cost depends mainly on the number and size of pages, website response times, and selected compute resources. Start with a small `maxRequestsPerCrawl`, review usage in Apify Console, and scale from that measurement. Small audits may fit within available free-platform credits; check your Apify account for current limits and pricing. ### Tips and advanced options - Keep `maxCrawlDepth: 0` for URL-list audits and predictable page counts. - All supplied Start URLs are processed. The request limit controls how many additional discovered pages can be analyzed. - Use depth 1 or 2 for targeted site discovery and keep `sameDomainOnly: true`. - Configure `proxyConfiguration` in the Input tab when targets require IP rotation; disable it for direct local requests. - Disable unused extractors to reduce parsing work on large runs. - Keep `includeRaw: false` for smaller datasets and faster downstream processing. - Set `includeWarnings: false` when downstream consumers only need blocking validation errors. Validation checks syntax and known Schema.org types and properties. Errors make an item invalid, while warnings highlight potential quality or compatibility issues for review. This is **not a Google Rich Results validator**. Google search features have separate, product-specific eligibility rules and recommended fields. A valid Schema.org Product can therefore be valid here even when it is not eligible for a particular Google result. ### FAQ, disclaimers, and support #### Does the Actor render JavaScript? **This Actor does not render JavaScript.** Structured data injected only after client-side JavaScript execution may not be detected. #### How does crawling work? Depth 0 processes only supplied URLs. Higher depths follow eligible page links up to the configured limit. Enable `sameDomainOnly` to keep discovery on the starting hostname. The Actor respects robots.txt directives. #### What are the limitations? The Actor focuses on common Schema.org patterns. Structured data added only after client-side JavaScript runs may not be visible. Blocked, inaccessible, or unsupported pages are reported as page-level errors so they can be reviewed in the dataset. Scrape only pages you are permitted to access and comply with applicable terms, robots policies, privacy requirements, and laws. If you find a bug or need another vocabulary rule or output integration, use the Actor's **Issues** tab. Custom extraction and Website Intelligence integrations are also available as tailored solutions. # Actor input Schema ## `startUrls` (type: `array`): One or more HTTP(S) pages to analyze. ## `maxRequestsPerCrawl` (type: `integer`): Maximum total pages processed during one run. All supplied Start URLs are always processed, even when their count is higher. ## `maxCrawlDepth` (type: `integer`): 0 analyzes only supplied URLs; higher values follow links by that many levels. ## `sameDomainOnly` (type: `boolean`): When following links, only enqueue URLs on the hostname of the originating start URL. ## `proxyConfiguration` (type: `object`): Configure Apify Proxy or provide custom proxy URLs. Apify Proxy access depends on your plan. ## `includeJsonLd` (type: `boolean`): Extract application/ld+json blocks. ## `includeMicrodata` (type: `boolean`): Extract Schema.org itemscope/itemprop markup. ## `includeRdfa` (type: `boolean`): Extract common Schema.org RDFa markup. ## `includeRaw` (type: `boolean`): Include bounded raw structured-data fragments. Full page HTML is never emitted. ## `validate` (type: `boolean`): Validate types, properties, inheritance, and conservative range hints. ## `includeWarnings` (type: `boolean`): Emit detailed warning arrays. Summary counts always include generated warnings. ## `timeoutSecs` (type: `integer`): Maximum time allowed for one HTTP request. ## Actor input object example ```json { "startUrls": [ { "url": "https://apify.com" } ], "maxRequestsPerCrawl": 100, "maxCrawlDepth": 0, "sameDomainOnly": true, "proxyConfiguration": { "useApifyProxy": false }, "includeJsonLd": true, "includeMicrodata": true, "includeRdfa": true, "includeRaw": false, "validate": true, "includeWarnings": true, "timeoutSecs": 30 } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://apify.com" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("ib4ngz/schema-org-extractor-validator").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://apify.com" }] } # Run the Actor and wait for it to finish run = client.actor("ib4ngz/schema-org-extractor-validator").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://apify.com" } ] }' | apify call ib4ngz/schema-org-extractor-validator --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,ib4ngz/schema-org-extractor-validator" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/nUqbJCoELIfcpo0qQ/builds/DRDPYcrn497s04645/openapi.json