Social Preview Validator - Open Graph and Twitter Cards
Pricing
from $0.64 / 1,000 results
Social Preview Validator - Open Graph and Twitter Cards
Social Preview QA and Regression Monitor preserving Open Graph/Twitter validation while adding platform readiness, preview fingerprints, drift and release gating. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API workflows.
Pricing
from $0.64 / 1,000 results
Rating
0.0
(0)
Developer
Rafael Barreto Haddad
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 days ago
Last modified
Categories
Features
Share
Social Preview QA and Regression Monitor preserving Open Graph/Twitter validation while adding platform readiness, preview fingerprints, drift and release gating. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API workflows.
Why use this Actor
Publishing and ecommerce teams need bulk QA for social-preview metadata and image reachability before links are shared publicly.
Key features
- Buyer-native inputs aligned to open graph.
- Predictable structured output in the default Apify Dataset.
- Pay Per Event pricing tied to measurable result rows or reports.
- Optional MCP connector delivery for downstream automation and AI agents.
Quick start
Start with this working example and replace the target values with your own:
{"urls": ["https://www.python.org"],"verifyImages": true,"concurrency": 5}
The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.
Input
urls— URLs: Public HTTP/HTTPS URLs to validate. Duplicate targets are processed once. Entries must be non-empty strings.verifyImages— Verify preview images: Check whether og:image resolves to a reachable image response.concurrency— Concurrency: Parallel URL checks.previous_results— Previous preview snapshots: Optional map keyed by URL. Enables Open Graph/Twitter/canonical drift and platform-readiness regression detection.
All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.
Output
The Dataset exposes predictable machine-readable output. Representative fields include results.
Pricing
This Actor uses Pay Per Event. The current factory base price is $0.000750 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.
Use cases
- Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
- Use the Actor from API or schedules for recurring collection, comparison or monitoring.
- Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
- Compare repeat runs when the product supports snapshots or previous-run inputs.
Automation and AI
Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.
Limitations
- Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
- Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
- Analytical outputs depend on the quality and coverage of the supplied or collected source data.
- Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.
Detailed documentation
Check how public web pages are prepared for social sharing before broken titles, missing descriptions, or dead preview images reach production. The Actor validates Open Graph, Twitter/X card metadata, canonical links, and preview-image reachability, then returns structured issues and a 0-100 score.
Why use this Actor
Manual preview checks do not scale across product catalogs, editorial archives, landing pages, or client sites. This Actor gives teams a repeatable QA layer with explicit failure reasons instead of a vague pass/fail result.
Key features
- Extracts Open Graph title, description, image, URL, type, and site name.
- Extracts Twitter/X card, title, description, image, and site metadata.
- Checks canonical-link presence.
- Optionally verifies whether the Open Graph image is reachable and served as an image.
- Flags missing fields, cross-domain
og:url, unreachable images, and unusually long social text. - Returns page title, meta description, HTTP status, issue count, and 0-100 score.
- Supports up to 100 public URLs per run with controlled concurrency.
Input
{"urls": ["https://www.python.org"],"verifyImages": true,"concurrency": 5}
Output
Each URL produces a structured record containing final URL, HTTP status, page metadata, Open Graph data, Twitter/X card data, canonical URL, optional image validation, issue list, issue count, and score.
Example
{"ok": true,"score": 82,"openGraph": {"title": "Example", "image": "https://example.com/preview.png"},"twitter": {"card": "summary_large_image"},"issues": ["canonical_missing"]}
Use cases
- Editorial and publishing QA
- E-commerce product-page checks
- Landing-page launch validation
- Social-sharing regression monitoring
- Agency audits across client websites
- CI-style metadata checks before releases
Pricing
Pay per result. The current price is $0.00075 per checked URL, equivalent to $0.75 per 1,000 results.
Limitations
- The score is a QA heuristic, not a guarantee of how every social platform will render a page.
- Some platforms cache previews independently; this Actor checks the current public page metadata.
- JavaScript-generated metadata may not be visible to a lightweight HTML request.
- WAFs, authentication, CAPTCHAs, or blocked image requests can affect validation.
Responsible use
Only public HTTP/HTTPS pages are checked. Private-network destinations and unsafe redirects are blocked.
Input reliability update — 24 October 2026
Target arrays accept non-empty strings. Identical targets are processed once per run to avoid duplicate requests and result charges. Whitespace around targets is removed. Baseline maps must be JSON objects. Existing result fields, pricing and target limits are preserved.
Buyer-first quick start (November 2026)
This workflow is designed for one practical buyer question, with a small, reproducible first run and auditable Dataset output.
Example input
{"urls": ["https://www.python.org"],"verifyImages": true,"concurrency": 5}
Source and limitations
The first run uses a public-source request or user-provided authorized URLs/documents. Upstream websites can block or throttle requests; not every result is assured to be available. Verify source URLs and timestamps before acting. If the source is inaccessible, a failed or limited result is not evidence of zero market demand.
Repeatable workflow
Use the default test to understand the output, verify record identifiers and field coverage, then schedule a Task with a bounded input. Compare real earlier snapshots only when available. Check the current Apify Store Pay Per Event rate and set Apify run charge limits for recurring use. Source evidence does not establish paying customers, successful outbound sales, or revenue.