Structured Extract — Title, Metadata, JSON-LD & Contact Data from Any URL

Point this Actor at any URL and get clean, typed JSON back — no LLM, no browser, no API key. It fetches the page with a single HTTP request and pulls out the title, description, image, JSON-LD, headings, links, emails and prices with a dozen lines of regex instead of a token-burning model call.

What you get

• Ten fields per URL — title, description, image, siteName, canonical, jsonLd, headings, links, emails, prices — pick a subset via fields, or leave it empty to get all of them.
• jsonLd — every <script type="application/ld+json"> block on the page, parsed.
• emails — mailto: links and plain-text emails found anywhere on the page.
• prices — currency-formatted amounts ($12.99, €10, £5…) pulled straight from the text.
• links — every unique absolute href on the page, resolved from relative paths.
• Deterministic, not a model call. Regex over raw HTML — zero LLM cost, zero API key, same result every time.
• Runs on Apify: schedule it, monitor it, call it from the API, export to JSON/CSV/Excel or push straight into your own pipeline.

Who is this for

• AI agents and pipelines that need "here's a URL" turned into structured data without burning tokens on a model call
• Growth & content teams pulling titles, JSON-LD or contact emails off a list of pages in bulk
• Developers who need a quick metadata/link/email scrape without standing up their own fetch-and-regex service

Why it matters

AI agents and pipelines constantly need to turn "here's a URL" into structured data. Doing that with an LLM call burns tokens and money on something a dozen lines of regex already solve deterministically — same input, same output, every time, at compute price instead of token price.

How to run it

1. Click Try for free — no card needed on the free plan.
2. Paste your URLs into URLs, one per line. Optionally list specific field names in Fields to extract to skip the rest.
3. Press Start. Results land in the dataset — read them in the UI, pull them from the API, or have a webhook push them onward.

Pricing

Pay-per-event: $0.005 per run start + $0.002 per result. No monthly seat, no minimum. 100 URLs cost about $0.21; 1,000 URLs about $2.01.

A URL that could not be reached — a private IP, localhost, or a dead domain — is still returned, with found: false and the reason, and it is not charged for. You pay for answers, not for attempts.

简体中文说明

输入任意网址，此 Actor 只用一次 HTTP 请求抓取页面，再用固定的正则表达式提取出干净的结构化 JSON——标题 title、描述 description、图片 image、站点名 siteName、canonical 链接、页面上所有 JSON-LD 结构化数据块、标题标签 headings、页面全部链接 links、页面上出现的邮箱地址 emails，以及页面文本中出现的带币种价格 prices。全程不调用大模型、不加载浏览器、不需要任何密钥——同样的输入永远得到同样的输出，成本是计算成本，不是大模型 token 成本。

可以用 fields 只保留需要的字段，其余字段直接跳过不计算。这不是什么：不渲染 JavaScript，不跟随分页，也不会像大模型那样理解页面含义——只依赖纯 HTML 抓取，靠客户端渲染才出现的内容不会被提取到，多页列表也不会自动翻页汇总。

计费为按事件付费：每次运行 $0.005，每条成功提取的结果 $0.002。100 个网址约 $0.21，1000 个约 $2.01；无法访问的网址（私有 IP、localhost、域名失效等）会以 found: false 返回原因，不计费——只为拿到答案付费，不为尝试付费。

Input

Field	Required	What it does
urls	yes	URLs to extract from. Up to 100 per run.
fields	no	Subset to return: title, description, image, siteName, canonical, jsonLd, headings, links, emails, prices. Empty = all of them.
maxConcurrency	no	How many to process in parallel, 1–30 (default 10).

{
    "urls": ["https://example.com", "https://www.iana.org/help/example-domains"],
    "fields": [],
    "maxConcurrency": 10
}

Output

One row per URL. This is a real row from a real run; links is trimmed to 5 of the 26 it actually returns:

{
    "url": "https://www.iana.org/help/example-domains",
    "found": true,
    "httpStatus": 200,
    "title": "Example Domains",
    "description": null,
    "image": null,
    "siteName": null,
    "canonical": null,
    "jsonLd": [],
    "headings": ["Example Domains", "Further Reading"],
    "links": [
        "https://www.iana.org/",
        "https://www.iana.org/domains",
        "https://www.iana.org/protocols",
        "https://www.iana.org/numbers",
        "https://www.iana.org/about",
        "…"
    ],
    "emails": [],
    "prices": [],
    "summary": "https://www.iana.org/help/example-domains — title: 'Example Domains', 0 JSON-LD blocks, 26 links, 0 emails.",
    "checkedAt": "2026-07-26T13:28:42.587Z"
}

Field	What it means
jsonLd	Every JSON-LD block on the page, already parsed
headings	First H1/H2 text on the page
links	Unique absolute hrefs
emails	mailto: links and plain-text emails found on the page
prices	Currency-formatted amounts found on the page
found	false means the URL was unreachable; the row says why and is not billed

API

Start a run with a bearer token and explicit JSON input:

curl -sS -X POST 'https://api.apify.com/v2/acts/zinin~structured-extract/runs?waitForFinish=60' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"urls":["https://example.com","https://www.iana.org/help/example-domains"],"fields":[],"maxConcurrency":10}'

Read Dataset rows using the returned defaultDatasetId:

curl -sS "https://api.apify.com/v2/datasets/$DEFAULT_DATASET_ID/items?clean=true&format=json" \
  -H "Authorization: Bearer $APIFY_TOKEN"

MCP

For an Apify MCP client exposing the standard call-actor tool, send this exact payload:

{
  "name": "call-actor",
  "arguments": {
    "actor": "zinin/structured-extract",
    "input": {
      "urls": [
        "https://example.com",
        "https://www.iana.org/help/example-domains"
      ],
      "fields": [],
      "maxConcurrency": 10
    }
  }
}

Related tools

Related tools for adjacent workflows in B2B lead generation and data enrichment, data pipelines for AI applications.

Actor	What it does
URL to Markdown Converter	Pair it in the data pipelines for AI applications workflow: Fetch any URL and convert it into clean, LLM-ready Markdown — headings, links, lists and emphasis...
Live Price Oracle	Pair it in the data pipelines for AI applications workflow: Current USD price for any token by contract address or ticker: 24h change, liquidity, volume, best DEX pair
Company Profile Lookup	Pair it in the B2B lead generation and data enrichment workflow: Turn a domain or company name into one unified company card: website tech stack (CMS, ecommerce, key tech)...
Company Registry Enricher	Pair it in the B2B lead generation and data enrichment workflow: Turn a company name, LEI or UK company number into an official registry card: legal name, status,...
Intent Signal Aggregator	Pair it in the B2B lead generation and data enrichment workflow: Is this company in-market right now? Combines public hiring activity (Greenhouse, Lever, Ashby) and recent...

FAQ

Does it need an API key or login? No.

Does it run JavaScript or render the page? No — pure HTML fetch plus regex. Content that only appears after client-side rendering won't be captured.

Can I get only some fields? Yes — list the ones you want in fields; the rest are skipped and not computed.

Can I call it from an AI agent? Yes — standard Apify Actor, callable from the Apify API, the SDK, or the Apify MCP server. That's the point.

What this is NOT. It does not render JavaScript, follow pagination, or understand page meaning the way an LLM does. It is a fast, deterministic extractor for the structured signals that already sit in a page's HTML.

Found a wrong result, or need a field we don't extract? Open an issue on this Actor's page.

Machine use

The Actor is callable through the Apify API, SDK, and Apify MCP server. The input and Dataset row are the machine-facing contract; every field is pulled from the page's own HTML via regex, not inferred by a model — a field with no public trace on the page comes back empty rather than guessed.

---

Built by zinin. Questions? Telegram @timzinin.