# Web Metadata Extractor — Open Graph, JSON-LD as JSON (`skilled_glee/web-metadata-extractor`) Actor

Extract machine-useful metadata from web pages as JSON: title, description, Open Graph, Twitter Card, JSON-LD structured data, canonical URL, language, H1 headings. Plain HTTP fetch, no AI, no browser. One failed page never kills the batch.

- **URL**: https://apify.com/skilled_glee/web-metadata-extractor.md
- **Developed by:** [EchoEmpire Machine Foundry (EchoEmpire LLC)](https://apify.com/skilled_glee) (community)
- **Categories:** Developer tools, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 page processeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Web Metadata Extractor

Extract machine-useful metadata from web pages as structured JSON: page title, meta description,
Open Graph tags, Twitter Card tags, other meta tags, JSON-LD structured data, canonical URL, declared
language, and up to 10 H1 headings. Plain HTTP fetch + parsing — no AI, no browser, no JavaScript rendering.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `pageUrls` | string\[] | yes | Web page URLs to extract metadata from (min 1). |
| `useResidentialProxy` | boolean | no | Route fetches through residential proxies for bot-walled targets. Default `false`. |

### Output

One dataset item per input URL. Successful items carry `url`, `finalUrl` (after redirects),
`status: "ok"`, and extracted fields: `title`, `description`, `language` (from `<html lang>` or
`og:locale`), `canonicalUrl`, `openGraph`, `twitterCard`, `meta` (other named meta tags), `jsonLd`,
`jsonLdTypes`, and `h1` (list of up to 10 H1 heading texts; H2–H6 are not extracted). Failed URLs
produce an explicit error record (`url`, `status: "error"`, `error` message) — one bad URL never
kills the batch.

The key-value store record `run-summary` holds `requested`, `succeeded`, `failed`,
`billable_units`, `ppe_event`, and `useResidentialProxy`.

If `pageUrls` is empty the Actor falls back to `https://www.example.com` and charges for it
normally, so always pass the URLs you want.

### Pricing

Pay Per Event: one `page-processed` event per page that is fetched and parsed successfully, at
**$0.001/page**. The charge fires after the `status: "ok"` record is pushed to the dataset, even if the
page has few or no metadata tags. Failed pages (HTTP error, network error, invalid URL) are not billed.
Apify platform usage, including residential proxy when you enable it, is included in the event price
and is not billed to you separately.

### Limitations

- Plain HTTP fetch only: pages that require JavaScript rendering return whatever the raw HTML contains.
- No paywall bypass, no login, no CAPTCHA solving.
- Only the first 2 MB of each page's HTML is read; transient HTTP errors (429/5xx) and network errors are retried up to 3 times.
- Bot-walled sites may need `useResidentialProxy: true` (included in the event price).
- Pricing is provisional pending an actor-specific measured P95 cost benchmark.

### Example (Apify API)

```bash
curl -X POST "https://api.apify.com/v2/acts/skilled_glee~web-metadata-extractor/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"pageUrls": ["https://example.com", "https://www.iana.org"]}'
```

### Version

0.3 — current Store build line (0.3.x). Output fields are exactly those listed above.

# Actor input Schema

## `pageUrls` (type: `array`):

Web page URLs to extract metadata from.

## `useResidentialProxy` (type: `boolean`):

Route fetches through residential proxies for bot-walled targets.

## Actor input object example

```json
{
  "pageUrls": [
    "https://www.example.com"
  ],
  "useResidentialProxy": false
}
```

# Actor output Schema

## `canonicalUrl` (type: `string`):

No description

## `description` (type: `string`):

No description

## `error` (type: `string`):

No description

## `finalUrl` (type: `string`):

No description

## `h1` (type: `string`):

No description

## `jsonLd` (type: `string`):

No description

## `jsonLdTypes` (type: `string`):

No description

## `language` (type: `string`):

No description

## `meta` (type: `string`):

No description

## `openGraph` (type: `string`):

No description

## `status` (type: `string`):

No description

## `title` (type: `string`):

No description

## `twitterCard` (type: `string`):

No description

## `url` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "pageUrls": [
        "https://www.example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("skilled_glee/web-metadata-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "pageUrls": ["https://www.example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("skilled_glee/web-metadata-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "pageUrls": [
    "https://www.example.com"
  ]
}' |
apify call skilled_glee/web-metadata-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,skilled_glee/web-metadata-extractor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BaeBofwGyrJdmMfWB/builds/dmQBYAFK2j8YE4foc/openapi.json