Metascraper Metadata Extractor

Metascraper Metadata Extractor turns a known list of public page URLs into one structured dataset record per page. It returns normalized title, description, author, publication date, image, logo, publisher, language, and URL alongside Open Graph, Twitter card, canonical, favicon, JSON-LD, and raw head-tag provenance for teams building preview, content, and SEO workflows.

Best fit and focused standalone workflow

Choose this Actor when you already have page URLs and want page-authored metadata in a compact, API-ready dataset. It works as a focused standalone workflow for link-preview QA, known-URL content enrichment, and canonical-field reviews. Start with a specific page list, then pass the returned source URL, canonical URL, title, publisher, and metadata image into your CMS, QA sheet, or content pipeline for the next enrichment or review step.

Workflow story: from URLs to a preview-ready record

A content operations team starts with a spreadsheet of article URLs. Next, it supplies those URLs to this Actor and receives one normalized record per page with the author, date, canonical URL, metadata image, and source-tag provenance. The team then compares the returned fields, feeds clean rows into its publishing workflow, and schedules a later run when it wants a fresh collection.

Input

Pass urls as a plain array or startUrls in the Apify request-list format. The Actor accepts up to 100 distinct HTTP(S) URLs and processes 25 by default. includeRawMetaTags preserves grouped page-head metadata; includeJsonLd keeps valid JSON-LD blocks for structured-data context.

{
  "urls": ["https://example.com"],
  "includeRawMetaTags": true,
  "includeJsonLd": true,
  "maxResults": 25
}

Output

Each page produces one dataset item. metadata contains the normalized Metascraper result, while openGraph, twitterCard, and rawMetaTags retain page-authored provenance.

Field	Meaning
metadata.title	Normalized page title selected by Metascraper rule bundles.
canonicalUrl	Declared canonical link resolved against the final page URL.
openGraph	Page-authored og:* tags, including repeat values where present.
twitterCard	Page-authored twitter:* tags for preview debugging.
jsonLd	Valid page JSON-LD blocks, capped at 20 per page.
warnings	Page-level provenance notes, such as malformed JSON-LD blocks.

{
  "sourceUrl": "https://example.com/",
  "finalUrl": "https://example.com/",
  "statusCode": 200,
  "metadata": {
    "title": "Example Domain",
    "description": null,
    "author": null,
    "publishedAt": null,
    "image": null,
    "logo": null,
    "publisher": null,
    "language": "en",
    "url": "https://example.com/"
  },
  "canonicalUrl": null,
  "openGraph": {},
  "twitterCard": {},
  "warnings": []
}

Pricing

The Actor uses Pay per Event plus platform usage. The metadata-extracted event is $0.004 for each successful persisted metadata record and Actor start is $0.00005. A 25-page collection has an event-cost cap of $0.10005 before platform usage. Review the live Pricing tab before a production workflow because it is the current source of truth for event and platform-usage charges.

Run through the API

export APIFY_TOKEN="your-apify-token"
curl "https://api.apify.com/v2/acts/khadinakbar~metascraper-metadata-extractor/run-sync-get-dataset-items?token=${APIFY_TOKEN}" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://example.com"],"includeRawMetaTags":true,"includeJsonLd":true,"maxResults":1}'

AI agent prompt

Use Metascraper Metadata Extractor for these supplied public page URLs. Return the title, canonical URL, normalized image, publisher, Open Graph tags, JSON-LD, and warnings. Read the dataset results after completion, retain source URL provenance, report the terminal outcome, and keep the collection within the stated per-record cost and page scope.

The terminal OUTPUT and RUN_SUMMARY records provide outcome and dataset-readback context. A supplied page list is the full scope of a run, so agents can control collection size and event cost with maxResults.

Best-results guidance

Provide canonical public pages with complete HTML head sections and use the final URL, status code, warnings, and source-tag groups together when reviewing a record. For recurring checks, schedule the same bounded URL list and compare the fresh dataset against the prior collection in your own workflow.

Builder's note

I built this Actor around Metascraper’s official, composable rule bundles because a normalized result alone can hide the field source that a QA or ingestion team needs to inspect. My design keeps both layers: a concise normalized record for downstream use and raw tag provenance for an informed follow-up decision.

Responsible use

Use this Actor for public pages your organization is authorized to access, with applicable laws, site terms, and internal data policies guiding each collection.