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.

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

Need the rest of the picture?

These run on the same account, take the same shape of input and bill the same way, so they slot into an existing pipeline without new plumbing.

Actor	What it does
AI Crawler Access Checker	Check which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended & more) can access your website
B2B Lead Enricher	Turn a list of company websites into sales-qualified lead cards: detected tech stack, a rough revenue…
Clinical Trials Monitor	Watch conditions, drugs or sponsors for new and updated clinical trials
Company Hiring Radar	Pull every open role a company is hiring for from its public job board (Greenhouse, Lever, Ashby) and turn…
Company Profile Lookup	Turn a domain or company name into one unified company card: website tech stack (CMS, ecommerce, key tech)…

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.

---

Built by zinin. Questions? Telegram @timzinin.