URL Metadata Extractor — OpenGraph, JSON-LD & SEO Tags

Extract SEO tags, OpenGraph, Twitter Cards, JSON-LD, titles and article metadata in one JSON per URL. Batch up to 100 URLs with optional clean text. Power link previews, SEO inventories and ETL. Launch price: $0.50/1,000 URL reports.

Turn URL lists into link-preview data and technical SEO metadata in one request. Optional cleaned text lets the same result feed content workflows.

When to use it

• Link previews from OpenGraph and Twitter/X tags.
• Canonical, robots and hreflang inventories for SEO checks.
• Observed article metadata and static text for ETL.

Start with this input

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

Click Start, then read the Output table or download JSON/CSV. Single and batch targets are supported. Duplicate targets are removed before network work.

What you get

HTTP status/final URL/redirects; title, description, canonical, language, favicon, OpenGraph, Twitter/X, JSON-LD, schema types, robots meta, hreflang, H1, word count and explicit author/dates.

One record per unique processed target, including observedAt, status and warnings. Missing data, unsupported sources, lookup failures, timeouts and invalid input are distinct states. Partial results remain usable. Dataset views show focused fields; the complete JSON record remains available through the dataset API.

{
  "schemaVersion": 1,
  "coreVersion": "0.1.0",
  "product": "url-metadata",
  "normalizedInput": "http://example.com/",
  "observedAt": "2026-09-18T19:56:58.106Z",
  "status": "success",
  "warnings": [],
  "metadata": {
    "title": {
      "status": "found",
      "value": "Example Domain"
    },
    "description": {
      "status": "not_found"
    },
    "canonical": {
      "status": "not_found"
    },
    "author": {
      "status": "not_found"
    },
    "publishedDate": {
      "status": "not_found"
    },
    "modifiedDate": {
      "status": "not_found"
    },
    "wordCount": {
      "status": "found",
      "value": 19
    }
  }
}

Price and spending control

$0.0005 per URL report ($0.50/1,000), plus $0.0005 per run at the default 256 MB. Platform usage is included. No separate per-page or automatic dataset-item charge.

Targets	Maximum event price
1	$0.001000
10	$0.005500
100	$0.050500

Valid attempted diagnostics are charged, including HTTP errors, missing fields and DNS/TLS/timeout failures. Invalid input, whole-target private-address rejection and targets not started at the run-time cap receive no result event; a run-start event can still apply. A started inspection reaching a body/request/time cap is a charged diagnostic.

Set Maximum cost per run in Console or maxTotalChargeUsd in the API. The runtime reserves affordable targets before lookup and records omitted targets in METRICS. maxItems adds an independent item cap. Actor-start is per GB of memory with a minimum of one event; larger memory can increase it.

Call from your workflow

JavaScript:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('gertner-data/url-metadata').call(
  {"urls":["https://example.com","https://www.iana.org/help/example-domains"]}, { maxTotalChargeUsd: 0.001500 }
);
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python:

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('gertner-data/url-metadata').call(run_input={"urls":["https://example.com","https://www.iana.org/help/example-domains"]}, max_total_charge_usd=0.02)
rows = list(client.dataset(run['defaultDatasetId']).iterate_items())

HTTP: POST JSON input to https://api.apify.com/v2/acts/gertner-data~url-metadata/runs?maxTotalChargeUsd=0.02 with your bearer token in the Authorization header. Wait for completion and GET /v2/datasets/{defaultDatasetId}/items. Use asynchronous runs for larger batches.

For recurring checks, save your own task and attach an Apify schedule. For downstream integrations, consume defaultDatasetId after RUN.SUCCEEDED and route each item's structured status.

API coverage and run settings

Reads source-published tags, author/date fields and favicon links directly from HTML. Canonical and hreflang values form a page-level inventory ready for downstream SEO processing.

Public HTTP(S) on ports 80/443; private/reserved addresses and unsafe redirects are blocked. Processes public static content over HTTP(S). Per-page, aggregate-body, request and total-time limits keep costs bounded; limit codes remain visible. UTF-8 expected. Maximum 100 unique targets per run. Inspect only sources you are authorized to access.

Support: Evgeny Gertner.