# OpenGraph & Social Preview Scraper (`andok/opengraph-inspector`) Actor

Extract OpenGraph tags and Twitter Cards to ensure your content looks perfect when shared on social media.

- **URL**: https://apify.com/andok/opengraph-inspector.md
- **Developed by:** [Andok](https://apify.com/andok) (community)
- **Categories:** SEO tools, Social media, Developer tools
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.47 / 1,000 url inspecteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## OpenGraph & Twitter Card Inspector

Inspect OpenGraph and Twitter Card meta tags across hundreds of URLs to QA your social sharing previews before they go live. A missing `og:image` or wrong `twitter:card` type means ugly link previews on Facebook, LinkedIn, Slack, and X -- and you only find out after someone shares the link. Bulk-check every page and get a clear report of what is present, what is missing, and what needs fixing.

### Features

- **OpenGraph extraction** — captures `og:title`, `og:description`, `og:image`, `og:url`, `og:type`, and all other OG tags
- **Twitter Card extraction** — reads `twitter:card`, `twitter:title`, `twitter:description`, `twitter:image`, and related tags
- **Basic meta tags** — also grabs the page `<title>` and `<meta name="description">` for comparison
- **Missing tag detection** — flags essential tags that are absent so you can prioritize fixes
- **Bulk processing** — scan hundreds of URLs in a single run with configurable concurrency
- **Structured output** — OG and Twitter tags are returned as separate objects for easy filtering
- **Pay-per-event billing** — you only pay for each URL inspected, with automatic charge-limit enforcement

### Input

| Field | Type | Required | Default | Description |
|-------|------|----------|---------|-------------|
| `urls` | `array` | Yes | — | List of page URLs to inspect for OpenGraph and Twitter Card meta tags. |
| `url` | `string` | No | — | Single URL to inspect (for backwards compatibility). Use `urls` for bulk processing. |
| `timeoutSeconds` | `integer` | No | `15` | Maximum seconds to wait for each page response before timing out. |
| `concurrency` | `integer` | No | `10` | Number of URLs to process in parallel. Increase for large batches, decrease if you hit rate limits. |

#### Input Example

```json
{
  "urls": [
    "https://crawlee.dev",
    "https://apify.com/store",
    "https://github.com/apify/crawlee"
  ]
}
```

### Output

Each URL produces one dataset item with separated OG tags, Twitter tags, and a list of missing essentials.

- `inputUrl` (`string`) — the URL you submitted
- `finalUrl` (`string`) — the URL after redirects
- `status` (`number`) — HTTP status code
- `pageTitle` (`string`) — content of the `<title>` tag
- `pageDescription` (`string`) — content of `<meta name="description">`
- `ogTags` (`object`) — all OpenGraph meta tags as key-value pairs (e.g., `og:title`, `og:image`)
- `twitterTags` (`object`) — all Twitter Card meta tags as key-value pairs (e.g., `twitter:card`, `twitter:image`)
- `missingEssential` (`string[]`) — list of essential tags that are missing (e.g., `og:title`, `og:image`, `twitter:card`)
- `error` (`string | null`) — error message if the URL could not be fetched
- `checkedAt` (`string`) — ISO 8601 timestamp of when the inspection was performed

#### Output Example

```json
{
  "inputUrl": "https://crawlee.dev",
  "finalUrl": "https://crawlee.dev/",
  "status": 200,
  "pageTitle": "Crawlee - Build reliable web scrapers",
  "pageDescription": "A web scraping and browser automation library for Node.js",
  "ogTags": {
    "og:title": "Crawlee - Build reliable web scrapers",
    "og:description": "A web scraping and browser automation library",
    "og:image": "https://crawlee.dev/img/og-image.png",
    "og:url": "https://crawlee.dev/",
    "og:type": "website"
  },
  "twitterTags": {
    "twitter:card": "summary_large_image",
    "twitter:title": "Crawlee",
    "twitter:description": "A web scraping and browser automation library"
  },
  "missingEssential": [],
  "error": null,
  "checkedAt": "2025-01-15T10:30:00.000Z"
}
```

### Pricing

| Event | Cost |
|-------|------|
| URL Inspected | Pay-per-event (see actor pricing page) |

The actor stops automatically when the per-run charge limit is reached, so you never overspend.

### Use Cases

- **Social media QA** — verify that every page renders a proper preview on Facebook, LinkedIn, Slack, and X before launch
- **Content migration validation** — confirm OG and Twitter tags survived a CMS migration or redesign intact
- **Agency reporting** — deliver social-readiness audits to clients with per-page pass/fail status
- **SEO auditing** — ensure meta descriptions and OG descriptions are consistent across your site
- **Marketing campaigns** — validate landing page previews before sharing URLs in ad campaigns or newsletters

### Related Actors

| Actor | What it adds |
|-------|-------------|
| [JSON-LD & Schema.org Extractor](https://apify.com/andok/jsonld-extractor) | Extracts structured data — combine with OG inspection for a complete metadata and schema audit |
| [Favicon & Brand Icon Extractor](https://apify.com/andok/favicon-extractor) | Grabs favicons and touch icons — pair with OG images for full brand asset collection |
| [Website Tech Stack Analyzer](https://apify.com/andok/tech-stack-analyzer) | Detects the CMS and framework — understand which platform generates the social preview tags |

# Actor input Schema

## `urls` (type: `array`):

List of page URLs to inspect for OpenGraph and Twitter Card meta tags. Each page is fetched and all OG/Twitter meta elements are extracted.

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

Single URL to inspect (for backwards compatibility). Use the URLs field above for bulk processing.

## `timeoutSeconds` (type: `integer`):

Maximum seconds to wait for each page response. Increase for slow or geographically distant sites.

## `concurrency` (type: `integer`):

Number of URLs to process in parallel. Higher values speed up large batches but may trigger rate limits on some hosts.

## Actor input object example

```json
{
  "urls": [
    "https://crawlee.dev"
  ],
  "timeoutSeconds": 15,
  "concurrency": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `resultsCsv` (type: `string`):

No description

## `run` (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 = {
    "urls": [
        "https://crawlee.dev"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("andok/opengraph-inspector").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 = { "urls": ["https://crawlee.dev"] }

# Run the Actor and wait for it to finish
run = client.actor("andok/opengraph-inspector").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 '{
  "urls": [
    "https://crawlee.dev"
  ]
}' |
apify call andok/opengraph-inspector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,andok/opengraph-inspector"
        }
    }
}
```

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/fSTmHcI8WmntbOsC9/builds/iC9Iv54vID7MrlIHa/openapi.json