Structured Data & Social Preview Validator

A fast, no-browser check of the tags that control how your pages appear in Google's rich results and in social link previews. Point it at one or more URLs and get back JSON-LD/schema.org validation, Open Graph tags, and Twitter Card tags -- plus a letter grade, a 0-100 score, a severity tag, and a plain-English issue list.

What you get, per URL

• A letter grade (A+ to F) and 0-100 score summarizing rich-result and social-preview readiness at a glance
• A one-line executive summary ("4 issue(s) found -- review recommended")
• A severity tag -- critical (page unreachable, missing <title>, or broken JSON-LD), warning (missing OG/Twitter tags or other issues), or ok -- for instant triage
• JSON-LD structured data -- every @type found on the page (Article, Product, Organization, and more), flagged if the JSON is malformed, and checked against the fields Google's rich-result docs recommend for common types
• Open Graph tags -- og:title, og:description, og:image, og:type, which control how the page previews on Facebook, LinkedIn, and Slack
• Twitter Card tag -- whether twitter:card is present, which controls the preview on X/Twitter
• Basic on-page SEO -- <title> and meta description presence
• Pages are checked in parallel (configurable, up to 20 at once), so a batch of 50 URLs finishes in a fraction of the time a one-by-one check would take

Why this instead of checking manually

	Manual spot-checks	Structured Data & Social Preview Validator
Coverage	Whatever page you remember to test	Every URL you list, automatically
Speed	One page at a time in a social debugger tool	Seconds, via parallel checking
Triage	You read raw JSON-LD and meta tags yourself	Pre-classified severity + letter grade
Repeatability	Forgotten after the next CMS template change	One click, or schedule it
Output	Screenshots of a preview tool	Structured dataset, exportable to CSV/JSON/BI tools

Who this is for

• Developers and marketers shipping a new page or blog post who want to confirm it will preview correctly when shared
• SEO teams auditing structured data across a site for rich-result eligibility
• Agencies doing a pre-launch checklist across a client's key pages
• Anyone who's shared a link and been embarrassed by a missing preview image

How to use it

1. Add one or more URLs to check.
2. Tune concurrency (default 5) to trade speed for gentleness on slow servers.
3. Run it once for a snapshot, or put it on an Apify Schedule to catch a dropped meta tag after a CMS or template change.

Example output (one item)

{
  "url": "https://example.com/blog/post",
  "statusCode": 200,
  "score": 60,
  "grade": "D",
  "severity": "warning",
  "summary": "4 issue(s) found -- review recommended.",
  "issueCount": 4,
  "issues": [
    "No JSON-LD structured data found on this page.",
    "Missing og:image -- shared links will show no preview image.",
    "No Twitter Card tag found -- X/Twitter will fall back to Open Graph tags or show no preview.",
    "Missing meta description tag."
  ],
  "structuredDataFound": false,
  "structuredDataTypes": [],
  "hasOpenGraph": true,
  "ogTitle": "Example Blog Post",
  "ogImage": null,
  "hasTwitterCard": false,
  "checkedAt": "2026-08-22T00:00:00.000Z"
}

Pricing

This Actor uses pay-per-event pricing:

• Page validated -- charged once per URL processed.

Parallel checking doesn't cost more -- it just finishes faster.

FAQ

Does this render JavaScript-injected tags? No. It reads the raw HTML response, the same way search engine and social media crawlers typically do for meta tags. If your tags are injected client-side by JavaScript after page load, they won't be seen here -- which is itself a useful signal, since many crawlers behave the same way.

Which schema.org types does it validate fields for? Article/NewsArticle/BlogPosting, Product, Organization, LocalBusiness, Recipe, Event, BreadcrumbList, and FAQPage, based on Google's commonly documented required/recommended properties. Other types are still detected and listed, just not field-checked.

What makes something "critical" vs. a "warning"? critical covers page-breaking problems: the page couldn't be fetched, has no <title> tag, or has JSON-LD that fails to parse. warning covers everything else that lowers the score, most commonly missing Open Graph or Twitter Card tags -- worth fixing, but the page still loads and functions.

Will higher concurrency get me rate-limited? It can, on servers with aggressive rate limiting. Start at the default (5) and lower it if you see timeouts spike for a particular site.

Does this send any data anywhere besides your own Apify account? No. It only fetches the URLs you provide and returns what it finds -- no login, no third-party analytics calls.