Bulk Metadata, Open Graph & JSON-LD Extractor — SEO Tags
Pricing
from $0.60 / 1,000 results
Bulk Metadata, Open Graph & JSON-LD Extractor — SEO Tags
Extract on-page metadata from thousands of URLs at once: title, meta description, Open Graph & Twitter Card tags, canonical, favicon, hreflang, RSS feed and schema.org JSON-LD structured data. Fast, keyless bulk SEO metadata and structured-data extractor.
Pricing
from $0.60 / 1,000 results
Rating
0.0
(0)
Developer
Haketa
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 hours ago
Last modified
Categories
Share
Bulk Metadata, Open Graph & JSON-LD Extractor — SEO Tags at Scale
Extract on‑page metadata from thousands of URLs at once. Paste a list and get, for each page: title, meta description, canonical, Open Graph & Twitter Card tags, favicon, hreflang, RSS feed and schema.org JSON‑LD structured data.
Fast, keyless and built for scale — the metadata layer you need for SEO audits, link previews, structured‑data checks and content intelligence.
Why this Actor?
Every page's <head> is packed with signals — how it appears in search, how it unfurls on social, what language versions exist and what structured data it exposes. Reading all of that by hand, page by page, is painful. This Actor pulls it in bulk and returns a clean, comparable table:
- SEO tags — title, description, canonical, robots, viewport, keywords, author.
- Open Graph & Twitter Card — everything that controls how a link looks when shared.
- Icons & feeds — favicon, apple‑touch‑icon, web manifest, RSS/Atom feed.
- Internationalisation — every
hreflangalternate. - Structured data — all schema.org JSON‑LD blocks and the exact types they declare.
One run turns a URL list into a full metadata + structured‑data inventory.
What you can do with it
- SEO audits — check titles, descriptions, canonicals and structured data across a whole site or list.
- Link previews / unfurling — build rich cards from OG/Twitter tags for chat, CMS and social tools.
- Structured‑data checks — see which pages expose schema.org (Product, Article, FAQ, Recipe…) and which don't.
- CMS & site migrations — snapshot metadata before/after to catch regressions.
- Content & competitor intelligence — map how pages describe themselves and what schema they use.
- Data enrichment — add title, description, image and site name to any list of URLs.
What you get — output fields
One record per URL:
| Field | Description |
|---|---|
url / finalUrl | Input URL and URL after redirects |
statusCode | HTTP status |
title | Page title |
metaDescription | Meta description |
canonical | Canonical URL |
lang / charset | Language and charset |
robots / viewport / themeColor | Common meta tags |
author / keywords | Author and keywords meta |
ogTitle … ogLocale | Open Graph: title, description, image, type, site name, url, locale |
twitterCard … twitterCreator | Twitter Card: card, title, description, image, site, creator |
favicon / appleTouchIcon / manifestUrl | Icons and web manifest |
feedUrl | RSS/Atom feed |
hreflang | All hreflang language alternates |
schemaTypes | schema.org types found (e.g. Product, BreadcrumbList) |
jsonLdCount | Number of JSON‑LD blocks |
structuredData | Raw JSON‑LD (when enabled) |
error | Populated if the page couldn't be read |
scrapedAt | ISO timestamp |
All URLs are absolute (favicon, images and canonical are resolved against the page).
Example output
{"url": "https://www.theverge.com","statusCode": "200","title": "The Verge","metaDescription": "The Verge is about technology and how it makes us feel.","canonical": "https://www.theverge.com/","lang": "en-US","ogTitle": "The Verge","ogType": "website","ogSiteName": "The Verge","ogImage": "https://.../verge-social.png","twitterCard": "summary_large_image","favicon": "https://www.theverge.com/favicon.ico","feedUrl": "https://www.theverge.com/rss/index.xml","hreflang": "","schemaTypes": "NewsMediaOrganization, WebSite","jsonLdCount": "2","scrapedAt": "2026-07-10T14:00:00.000Z"}
Input
| Field | Type | Default | Description |
|---|---|---|---|
urls | array | — | Required. Page URLs to read. |
includeJsonLd | boolean | true | Include raw JSON‑LD in structuredData. |
maxConcurrency | integer | 20 | URLs processed in parallel. |
proxyConfiguration | object | off | Apify Proxy, if some targets block direct requests. |
Basic run
{"urls": ["https://www.theverge.com", "https://github.com", "https://stripe.com"]}
Types only (smaller output)
{"urls": ["https://example.com/page-1", "https://example.com/page-2"],"includeJsonLd": false}
URLs without a scheme are accepted (example.com becomes https://example.com).
Use cases in detail
1. Site‑wide SEO audit
Feed every URL from your sitemap and get titles, descriptions, canonicals and robots directives in one table — instantly see missing or duplicate tags.
2. Structured‑data coverage
schemaTypes shows exactly which pages expose Product, Article, FAQPage, Recipe, BreadcrumbList and more — find pages missing the schema they should have for rich results.
3. Link previews and unfurling
Use the OG and Twitter fields (ogTitle, ogImage, twitterCard…) to render rich link cards in your app, CMS or chat integration.
4. Migration QA
Snapshot metadata before a migration and again after, then diff the two exports to catch dropped titles, canonicals or structured data.
5. Competitive & content intelligence
See how competitors write their titles/descriptions and which schema types they invest in across their key pages.
6. Enrich a URL list
Turn a plain list of URLs into records with title, description, image and site name — ready for a CRM, spreadsheet or dataset.
How to use it
- Click Try for free.
- Paste your URLs.
- (Optional) Turn off
includeJsonLdor adjust concurrency. - Click Start.
- Export as JSON, CSV, Excel or HTML table, or via the Apify API.
Calling from the API
curl -X POST "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs?token=YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{ "urls": ["https://www.theverge.com", "https://stripe.com"] }'
Fetch the results (JSON or CSV):
$curl "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs/last/dataset/items?token=YOUR_APIFY_TOKEN&format=csv"
What it reads
- Standard meta — title, description, keywords, author, robots, viewport, theme‑color, charset, html lang.
- Canonical & alternates —
rel=canonicaland everyhreflangalternate. - Open Graph — all
og:*properties (title, description, image, type, site_name, url, locale). - Twitter Card — all
twitter:*tags. - Icons & app — favicon, apple‑touch‑icon, web app manifest.
- Feeds — RSS/Atom
linktags. - Structured data — every
application/ld+jsonblock, with all schema.org@types (including nested@graph).
Tips for the best results
- Feed a sitemap's URLs for a full‑site audit in one run.
- Filter
schemaTypesis empty to find pages missing structured data. - Compare
titlevsogTitleandmetaDescriptionvsogDescriptionto catch inconsistencies. - Turn off
includeJsonLdwhen you only need tags and types — the output gets much smaller. - Enable proxy if a set of targets rate‑limits direct requests.
Frequently asked questions
Does it render JavaScript? It reads the served HTML (which is where metadata, OG/Twitter tags and JSON‑LD almost always live). This keeps it fast and cheap; SPA content injected purely client‑side into the body isn't required for metadata.
Does it get all JSON‑LD types?
Yes — it parses every JSON‑LD block and collects all @types, including those nested in @graph.
Can I pass URLs without https://?
Yes — a bare domain or path is upgraded to https:// automatically.
How large can the structured data be?
Very large blocks are captured (capped per record to keep exports manageable). Turn includeJsonLd off if you only need the types.
How many URLs can it handle? From a handful to millions, processed in parallel.
In which format can I export? JSON, CSV, Excel, HTML table, or via the Apify API.
Do I need an API key? No. Just paste your URLs and run.
Notes
This Actor reads publicly available HTML metadata from the URLs you provide. Use it on pages you have a legitimate reason to read and in line with each site's terms.
Support
Need extra signals (e.g. microdata/RDFa, full meta dump, per‑image details)? Open an issue from the Actor's page and describe what you need.