SEO Metadata & JSON-LD Change Audit API

Extract SEO metadata, canonicals, hreflang and JSON-LD with syntax warnings and repeatable hashes for change detection.

What you can do

Monitor important landing pages for title, canonical, indexing directive or structured-data changes.

Quick start

{
  "urls": [
    "https://books.toscrape.com/"
  ],
  "maxItems": 10
}

Run the Actor and download the default dataset as JSON, CSV or Excel. Inspect the OUTPUT key-value-store record before treating the run as complete. Live example sources can change or become unavailable.

Behavior and limitations

Extracts title, named/property meta tags, canonical links, hreflang and application/ld+json blocks from server-rendered UTF-8 HTML. Invalid JSON-LD blocks are identified by zero-based block index. Warnings cover missing title/description/canonical, multiple canonicals, noindex and invalid JSON syntax. This is not Schema.org semantic validation, Google rich-result eligibility, a search-ranking score or a full technical SEO audit. No browser rendering is used. Pass previousHashes keyed by the original input URL to label CURRENT, CHANGED or UNCHANGED. Hashes cover extracted metadata, not the entire HTML. Empty previousHashes means no baseline; a page missing from a run is never labeled deleted.

Every result preserves its source URL and an observedAt UTC timestamp. Network or parsing errors are listed by source in OUTPUT.errors; other successful sources still return results. OUTPUT.warnings, complete and status distinguish a full observation from partial output. If every requested source fails, the run fails rather than silently returning an empty success.

Pricing

USD 4 per 1,000 successful HTML page audit rows ($0.004 per row), plus a $0.005 Actor-start event for the default 256 MB run. No result event is charged for a failed source. The Actor-start event can still apply to a failed run. Higher memory can increase start-event quantity according to Apify's rules. This description must match the currently effective Store pricing; check the pricing tab before running. Apify charges only as configured there.

Resource and access limits

At most 1,000 output rows; public ports 80/443 only; five redirects; 2 MiB decoded body per request; approximately 100 seconds for fetching. Requests are sequential with no retries, CAPTCHA bypass, credentials, residential proxies or paid upstream APIs. robots.txt is respected; missing robots.txt (404/410) allows fetching, while blocked or unavailable policies produce errors. Public DNS addresses are validated and pinned for each connection. Use only sources you are permitted to access and respect source terms. Private networks and URLs with embedded credentials are rejected.

API and automation

Call POST https://api.apify.com/v2/actors/soilair~seo-metadata-jsonld-change-audit-api/runs with the example JSON and your own Apify authorization header. Poll the returned run ID, then fetch /v2/datasets/{defaultDatasetId}/items. Schedule subsequent runs in Apify Console; pass earlier keys/hashes explicitly where supported. The Actor never schedules jobs itself.

Data handling and support

Input and results remain in your Apify run's storage under the platform's retention settings. The Actor sends requests only to the input sources, their public redirects and robots.txt. No separate analytics or customer-data endpoint is used. Do not put secrets or private customer URLs in the input. Developed with AI assistance and tested with deterministic fixtures plus public-source smoke checks; this does not guarantee all storefronts or websites will work. For support, send the run ID, source URL and expected behavior via the Apify issue tab without credentials.