HTML Meta & JSON-LD Extractor

Fetch public pages and extract their HTML meta tags, OpenGraph tags, Twitter card tags, and JSON-LD @type lists in one structured pass. Built for SEO audits, content audits, and competitor research where you need a clean per-URL structured view of a page's metadata — without pulling the whole rendered DOM.

What it does

• Pulls a list of public HTTP(S) URLs and returns one dataset row per URL.
• Extracts the standard meta block: title, description, keywords, robots, canonical, viewport, charset.
• Extracts all og:* OpenGraph properties (object).
• Extracts all twitter:* Twitter card properties (object).
• Walks the page for <script type="application/ld+json"> blocks and returns the list of @type values plus the count.
• Records the final URL after redirects, the HTTP status, and a truncated flag if the body was cut at maxBytes.
• Pure data utility. Public pages only — no auth, no anti-bot bypass, no JS rendering.

Who it is for

• SEO / content teams running quick content audits on a list of URLs.
• Competitive intelligence — pull meta + OG + Twitter + JSON-LD from a list of competitor pages.
• Migration / launch QA — verify meta tags are set correctly on a new build before going live.
• RAG / knowledge-base curators who need a quick structured view of what each page declares about itself.
• Web researchers building a dataset of declared metadata across many pages.

Quick start

{
  "urls": [
    "https://apify.com",
    "https://docs.apify.com"
  ]
}

Each row in the dataset looks like:

{
  "url": "https://apify.com",
  "_kind": "meta",
  "finalUrl": "https://apify.com/",
  "status": 200,
  "truncated": false,
  "title": "Apify — Full-stack web scraping and data extraction platform",
  "description": "Apify is a full-stack platform for web scraping ...",
  "keywords": "web scraping, data extraction, automation",
  "robots": "index, follow",
  "canonical": "https://apify.com",
  "viewport": "width=device-width, initial-scale=1",
  "charset": "utf-8",
  "og": { "og:title": "...", "og:image": "...", "og:type": "website" },
  "twitter": { "twitter:card": "summary_large_image", "twitter:site": "@apify" },
  "jsonLdTypes": ["Organization", "WebSite"],
  "jsonLdCount": 2
}

Full input

Field	Type	Default	Notes
urls	string[] (required)	—	Public HTTP(S) page URLs. HTML only — JS-rendered pages are not supported.
maxBytes	int	2000000	Truncate the page body at this many bytes.
timeoutSec	int	15	Per-request HTTP timeout in seconds.
followRedirects	bool	true	Follow HTTP redirects.

Output

Dataset row kinds:

• meta — successful extract. Carries all HTML meta + OG + Twitter + JSON-LD.
• error — failed fetch. Carries status and error message.

SUMMARY key in key-value store: { urls, summaries: [{ url, ok, status, jsonLdCount, ogFields, twitterFields }, ...] }.

Pricing

This Actor is Pay Per Event on the Apify Store:

• apify-actor-start — flat per run.
• page_processed — charged once per URL successfully processed.

For local tests, Actor.charge is a no-op (no usage billed, no payout).

Limits

• Designed for public HTML pages. Login-walled content, paywalls, and JS-rendered SPAs are out of scope.
• The Actor does not execute JavaScript — only what the server-side HTML contains.
• maxBytes truncates the body before parsing; very large pages may be missing trailing meta tags.

FAQ

Q: Does this run JavaScript on the page? A: No. It only parses server-rendered HTML. For JS-rendered pages use a headless-browser Actor.

Q: My page returns 0 OG tags. Why? A: The page's HTML probably doesn't have any og:* properties. Confirm by viewing page source — if you don't see them there, this Actor won't find them.

Q: How does this differ from og-meta-validator? A: html-meta-extractor is a broad pull of all meta/OG/Twitter/JSON-LD. og-meta-validator focuses on validating a single OpenGraph spec (required fields, image dimensions, type allow-list) and is best used as a QA check on a small number of pages.

Q: Can I use it on a private/intranet site? A: Only if the Actor host can reach it without auth and over plain HTTP(S). The Actor does not handle cookies, headers, login, or anti-bot challenges.

Q: Does it support sitemap batch input? A: Not directly. Pipe in the URL list you get from sitemap-delta-monitor (public) or sitemap-news-sitemap-extractor.

Related Actors

• og-meta-validator — strict OpenGraph spec validation with required-field and image-dimension checks.
• jsonld-extractor-validator — extract and validate JSON-LD blocks per URL.
• html-link-classifier — classify anchor links on a page (internal / external / nofollow / sponsored / ugc).
• sitemap-delta-monitor — discover URLs to feed into this Actor.
• schema-product-delta-monitor — monitor product page schema changes.

Support

Open an issue on the Actor's Apify Store page (Report an issue link on the right rail) or contact the developer through the Store profile.

License

MIT — see Apify Store page for the canonical text.