Structured Data Extractor: JSON-LD, Open Graph, meta by URL

Structured data of any web page, up to 500 URLs a run: every JSON-LD block with its schema.org types, Open Graph and Twitter Card tags, title, meta description, canonical, robots meta, language, hreflang, feeds, favicon and published time, one row per URL. Robots-aware, no browser. Pay per page.

Why this scraper

• Only delivered results are charged. Inputs that fail come back as clear error records at no cost.
• One plain fetch per page, parsed with lxml, no browser. Measured on the platform: five pages (BBC News, Python.org, Wikipedia, GitHub, a BBC Good Food recipe) in 5 seconds for a tenth of a cent.
• Everything a page declares about itself in one row: every JSON-LD block as parsed JSON with its schema.org types (Recipe, Article, Product, FAQPage, BreadcrumbList, VideoObject and so on), Open Graph and Twitter Card tags, title, meta description, canonical, robots meta, keywords, language, hreflang alternates, RSS and Atom feeds, favicon, published and modified time. A @graph block is flattened to its objects; a list block likewise.
• Robots-aware: each host's robots.txt is read once per run and a closed path comes back as a free ROBOTS_DISALLOWED row (measured: Google's /search path).

Who this is for

Paste page URLs in urls (up to 500 per run). Leave includeRawJsonLd on to get the full JSON-LD objects; switch it off to keep rows small with only the types and count. Built for SEO audits of structured data and social tags across a site or a competitor's, for feeding recipe, product, article or event markup into a pipeline, and for checking canonicals, hreflang and feeds in bulk.

Who this is not for

No browser is used, so structured data that a page injects with JavaScript after loading is not seen; what the server sends is what you get. Microdata and RDFa attributes in the HTML body are not parsed, only JSON-LD, meta and link tags. A page with no structured data at all is still a valid, charged row with empty columns and hasStructuredData false (measured: GitHub's about page has Open Graph but no JSON-LD). article:author is dropped on purpose. Pages that answer 403 or 429 come back as a free BLOCKED row; 404 and other failures as a free FETCH_FAILED row.

Input example

{
    "urls": [
        "https://www.bbc.com/news",
        "https://github.com/about",
        "https://www.allrecipes.com/recipe/10813/best-chocolate-chip-cookies/"
    ],
    "includeRawJsonLd": true
}

Output example

• url
• finalUrl
• statusCode
• title
• metaDescription
• canonical
• language
• robotsMeta
• keywords
• publishedTime
• modifiedTime
• ogTitle
• ogDescription
• ogImage
• ogType
• ogSiteName
• ogUrl
• twitterCard
• twitterTitle
• twitterImage
• jsonLdTypes
• jsonLdCount
• jsonLd
• hreflang
• feeds
• favicon
• hasStructuredData

Error codes: INVALID_URL, ROBOTS_DISALLOWED, NOT_HTML, FETCH_FAILED, BLOCKED.

One delivered row looks like this:

{
  "url": "https://en.wikipedia.org/wiki/Web_scraping",
  "finalUrl": "https://en.wikipedia.org/wiki/Web_scraping",
  "statusCode": 200,
  "title": "Web scraping - Wikipedia",
  "metaDescription": null,
  "canonical": "https://en.wikipedia.org/wiki/Web_scraping",
  "language": "en",
  "robotsMeta": "max-image-preview:standard",
  "keywords": null,
  "publishedTime": null,
  "modifiedTime": null,
  "ogTitle": "Web scraping - Wikipedia",
  "ogDescription": null,
  "ogImage": null,
  "ogType": "website",
  "ogSiteName": null,
  "ogUrl": null,
  "twitterCard": null,
  "twitterTitle": null,
  "twitterImage": null,
  "jsonLdTypes": [
    "Article"
  ],
  "jsonLdCount": 1,
  "jsonLd": [],
  "hreflang": [],
  "feeds": [
    "https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&feed=atom"
  ],
  "favicon": "https://en.wikipedia.org/static/favicon/wikipedia.ico",
  "hasStructuredData": true,
  "status": "ok"
}

Related actors from steadydata

• webpage-to-markdown: the readable text of the same page
• page-links-extractor: every link on the page, internal and external
• technical-seo-audit: the technical issues of the same page, ranked

Pricing

Pay per event: one page-extracted event per delivered result. No charge for inputs that fail, no separate platform-usage surcharge.

Free Apify plan: this actor delivers up to 25 rows per run for accounts on the Apify free plan, and then stops with a message. That limit is set by us, not by Apify. It exists so the actor keeps paying for itself for the people who do pay. Any paid Apify plan runs it at full size, billed per delivered row, with failed rows never charged.

Reviews: if this actor saves you time, a short review on this page is the one thing that helps most. Ratings are what other buyers look at first, and we have no other way to ask.

FAQ

Is personal data collected? Nothing beyond what the page publishes about itself. The article:author tag is not delivered, and the actor reads only the URLs you give it.

Does it validate the JSON-LD? No. It parses whatever the page declares and passes it through as JSON; a block that is not valid JSON is skipped and does not count. Validation against schema.org is a separate step.

Why is canonical empty on some pages? Because the page has no canonical link tag (measured: python.org). The row still carries finalUrl, the address after redirects.

Can it read pages behind a login or a consent wall? No. It fetches as an anonymous visitor; what an anonymous visitor cannot see, it cannot see either.

What does a run cost when a URL fails? Nothing. ROBOTS_DISALLOWED, NOT_HTML, FETCH_FAILED, INVALID_URL and BLOCKED rows are free; only delivered pages are charged.

What happens when the source changes? Sources change from time to time; that is the nature of this work. The actor is monitored daily and fixed fast, and while it is broken you are not charged, because only delivered results cost anything.