OpenGraph.ioOpenGraph.io
Log inStart Free
Preview & Metadata

URL Metadata API

Turn any URL into structured website metadata. Extract titles, descriptions, images, favicons, canonical URLs, Open Graph tags, Twitter Cards, and more through one API.

Start Free View Docs
GETapi.opengraph.io/api/1.1/site
?site=https://example.com/article
Normalized metadata
title“How to Build Better Link Previews”
description“Extract structured metadata from any URL...”
image“https://example.com/og-image.jpg”
favicon“https://example.com/favicon.ico”
site_name“Example”
canonical“https://example.com/article”
url“https://example.com/article”
1B+URLs processed
1,000sof developers

Powering link previews, metadata extraction, and URL intelligence workflows at scale.

Structured response

Turn any URL into structured metadata

Websites expose useful information across Open Graph tags, Twitter Cards, HTML meta tags, and other page markup. OpenGraph.io collects that information and returns it through a consistent API response.

Title

The best available page title from Open Graph, Twitter Cards, or HTML.

Description

A short summary pulled from social tags or the standard meta description.

Image

The primary preview image with the most reliable source available.

Favicon

The site favicon URL for source context in your application.

Site name

Publisher or site name when available from page metadata.

Canonical URL

The canonical page URL when the page publishes one.

Page URL

The resolved URL after redirects and normalization.

Open Graph metadata

Full Open Graph tag set returned alongside normalized fields.

Twitter Card metadata

Twitter Card fields for platforms that rely on that tag format.

Normalized output

One request, normalized response

OpenGraph.io returns both source-specific metadata and a normalized hybridGraph object. Use the shape that matches your job.

  • Use normalized metadata when you want the best available value. OpenGraph.io combines available metadata sources and fallback information into one predictable object.
  • Use raw Open Graph data when you need to inspect exactly what the page published. Source-specific fields remain available alongside the normalized response.
hybridGraph
title“Best available title”
description“Best available description”
image“https://.../image.jpg”
url“https://example.com/article”
openGraph
og:title“Exact published OG title”
og:image“https://.../og.jpg”
Beyond Open Graph

Get the best available metadata, not just one tag format

Websites do not consistently publish one perfect metadata standard. Depending on the page, useful information may come from several sources.

Open Graph

Social preview tags published for Facebook, LinkedIn, Slack, and similar platforms.

Twitter Cards

X/Twitter metadata that often fills gaps when Open Graph tags are incomplete.

HTML metadata

Standard page title, meta description, canonical link, and favicon markup.

Inferred fallbacks

Best-available values when a page does not publish a complete metadata set.

Production extraction

Metadata from difficult websites

Parsing a well-tagged webpage is simple. Reliably extracting useful metadata from arbitrary URLs at production scale is the harder problem.

JavaScript-rendered websites

Some metadata only appears after client-side rendering. auto_render handles those pages without a separate browser stack.

Blocking and bot protection

auto_proxy helps reach sites that block naive scrapers or return different content to bots.

Retries and escalation

Failed fetches retry with smarter proxy and render behavior so extraction stays reliable.

Caching

Repeated lookups for the same URL can use cached metadata instead of hitting the origin every time.

Language controls

Request metadata in a preferred language when the target site supports it.

Production concurrency

Scale metadata extraction across user-submitted URLs with plans built for real traffic.

Use cases

Where teams use URL metadata

Developers use the URL Metadata API when URLs flow through a product and need to become structured records — not just preview cards.

Content aggregationBookmark managersCommunity platformsSocial productsKnowledge basesAI pipelinesURL enrichment

Content aggregation

Convert URLs into structured content records with titles, descriptions, images, domains, and canonical information.

Bookmarking and saved-link products

Automatically populate useful metadata whenever a user saves a URL.

Social and community platforms

Understand URLs submitted inside feeds, messages, communities, and user-generated content.

AI and content pipelines

Attach structured source information to URLs before storing, indexing, or processing them.

Integration

One API call to extract website metadata

Send a URL. Receive normalized metadata. Full parameters and edge-case guidance live in the Site API docs.

curlGET /api/1.1/site
curl "https://opengraph.io/api/1.1/site/https%3A%2F%2Fexample.com%2Farticle?app_id=YOUR_API_KEY"
Trimmed response
hybridGraph.title“How to Build Better Link Previews”
hybridGraph.description“Extract structured metadata...”
hybridGraph.image“https://example.com/og-image.jpg”
hybridGraph.favicon“https://example.com/favicon.ico”
hybridGraph.url“https://example.com/article”
View full API parameters
API comparison

Choose the right API for your job

These APIs solve closely related URL metadata problems. The right choice depends on what you want to do with the response.

URL Metadata API

This page

Best for understanding a page.

Use when:

You need structured information about a URL for enrichment, storage, or analysis.

View API Docs

Link Preview API

Best for displaying a page.

Use when:

You want title, description, image, domain, and fallback data ready for a UI.

Learn more

Open Graph API

Best for working directly with published Open Graph metadata.

Use when:

You want the social tags a page actually publishes, rather than normalized best-available metadata.

Learn more
How it works

From URL to structured metadata in seconds

01

Send a URL

Make a GET request with your URL and API key. That is the entire integration for most applications.

02

OpenGraph.io collects metadata

The platform reads Open Graph tags, Twitter Cards, HTML metadata, and fallback values from the live page.

03

Receive normalized JSON

Get a consistent response with hybridGraph for best-available values, plus source-specific data when you need it.

Simple API access

Start with an API key and a GET request. No SDK required.

Playground available

Test any URL before writing integration code.

Docs when you need them

Full Site API reference with response shapes and edge cases.

Preview & Metadata tools

Part of OpenGraph.io’s Preview & Metadata tools

The URL Metadata API sits in the Preview family alongside link preview generation, Open Graph inspection, and meta tag tools.

Preview & Metadata familyLink Preview APIOpen Graph CheckerFree Link Preview ToolSite API docsScreenshot API

FAQ

A URL Metadata API takes a webpage URL and returns structured metadata — such as title, description, images, favicon, and canonical URL — so your application can understand and store information about that page without scraping it yourself.
OpenGraph.io returns titles, descriptions, images, favicons, site names, canonical URLs, page URLs, Open Graph metadata, and Twitter Card metadata. The response also includes hybridGraph, a normalized object with the best available value for each field.
Use the URL Metadata API when you need structured information about a URL for enrichment, storage, or analysis. Use the Link Preview API when you are building preview cards for feeds, chat, or unfurling. Both are powered by OpenGraph.io's Site API — the difference is what you build with the response.
Open Graph metadata is one tag format used for social previews. URL metadata is broader: it combines Open Graph tags, Twitter Cards, HTML metadata, and fallback values into structured webpage information you can use beyond social cards.
Yes. OpenGraph.io supports automatic rendering for pages where metadata is not available from a simple HTML request. Rendering, proxy selection, and retries can be configured through the Site API.
Yes. OpenGraph.io fetches the target URL on your behalf, so your application does not need to operate an arbitrary-target scraper. This is a common pattern for communities, bookmark products, and content platforms.
Yes. Caching is supported so repeated lookups for the same URL do not always require a fresh origin fetch. See the Site API docs for cache controls and defaults.

Turn any URL into structured metadata

Start extracting titles, descriptions, images, Open Graph data, and more with one API request.

Start FreeView API Docs

Free tier included. No credit card required to start.