Website Meta & Social Tags Extractor avatar

Website Meta & Social Tags Extractor

Pricing

$3.00 / 1,000 results

Go to Apify Store
Website Meta & Social Tags Extractor

Website Meta & Social Tags Extractor

Extract the title, meta description, canonical URL, Open Graph and Twitter Card tags, and H1 heading from one web page (optionally a few same-site pages). Built for quick SEO and social-sharing checks: paste a URL, get a clean dataset item per page.

Pricing

$3.00 / 1,000 results

Rating

0.0

(0)

Developer

Eichan Jolly

Eichan Jolly

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 days ago

Last modified

Categories

Features

Limited permissions

Share

Paste in a URL and get back the tags that decide how the page looks in search results and social shares - the title, meta description, canonical URL, Open Graph tags, Twitter Card tags, and the H1 heading - as clean, structured data. No scraping code, no browser, no setup.

What it does

For each page it visits, the Actor extracts:

  • title - the page <title>
  • description - the meta description
  • canonical - the canonical URL, if the page declares one
  • openGraph - og:title, og:description, og:image, og:type, og:url, og:site_name
  • twitterCard - twitter:card, twitter:title, twitter:description, twitter:image
  • h1 - the first H1 heading text (plus h1Count, how many H1s the page has)
  • statusCode and fetchedAt - the HTTP status, and when the page was fetched

Typical uses: checking that a new page has its social tags in place before launch, auditing a few key pages after a redesign, or feeding page metadata into a spreadsheet or report.

Input

FieldWhat it isDefault
Start URLThe full URL of the page to inspect, including https://https://example.com
Max pagesHow many pages to visit at most, following links on the same site only. 1 = just the start page1

Example input:

{
"startUrl": "https://example.com",
"maxPages": 1
}

Output example

One dataset item per page:

{
"url": "https://example.com/",
"statusCode": 200,
"title": "Example Domain",
"description": null,
"canonical": null,
"openGraph": {
"title": null,
"description": null,
"image": null,
"type": null,
"url": null,
"siteName": null
},
"twitterCard": {
"card": null,
"title": null,
"description": null,
"image": null
},
"h1": "Example Domain",
"h1Count": 1,
"fetchedAt": "2026-11-01T01:20:00.000000+00:00"
}

A null simply means that tag is not present on the page - which is often exactly what you wanted to find out.

Limits - please read

  • Small by design. At most 5 pages per run, all on the same site as the start URL. This is a checker for individual pages, not a site-wide crawler.
  • Static HTML only. Tags are read from the page's HTML as the server sends it. If a site builds its tags with JavaScript in the browser, they may not appear here.
  • Public pages only. No logins, no cookies, no paywalls.
  • If the start page cannot be loaded (wrong URL, site down, HTTP error), the run stops and the log says why, in plain words.

For developers

Standard-library-only Python, no SDK. On the Apify platform the Actor uses the run's own environment variables (APIFY_TOKEN, APIFY_DEFAULT_KEY_VALUE_STORE_ID, APIFY_DEFAULT_DATASET_ID) to read the input from the key-value store API and POST each item to the dataset API. Locally (python3 src/main.py) it falls back to files - input from key_value_stores/default/INPUT.json and items as JSON files in datasets/default/ inside APIFY_LOCAL_STORAGE_DIR - so the same code runs in both places.