What it checks
Open Graph + Twitter Card Checker fetches one public page and reports its title, description, Open Graph tags, Twitter Card tags, image URL, and preview warnings. It checks page markup, not a social platform's cached preview.
Open Graph + Twitter Card Checker
Use this social preview checker to verify share cards before launching a page, posting a campaign link, sending a newsletter, or handing off a URL for distribution.
Checks a public page
Live checker
Open Graph + Twitter Card checker
Status
Run a guarded HTML check to inspect share preview tags.
Final statusNot checked
No request is sent until you run the check.
Open GraphNot checked
Checks og:title, og:description, og:image, og:url, og:type, and og:site_name.
Twitter CardNot checked
Checks card, title, description, image, site, and creator tags.
Review notes
- Checks one public HTML URL. Local, private, reserved, non-http, and credentialed URLs are blocked.
Scope note
This checker reads the fetched HTML response only. It does not render JavaScript, upload images, validate image dimensions, or simulate each platform preview crop.
Data freshness
No live response has been fetched yet. Run the checker to record a point-in-time source timestamp.
Web QA reports are launch checks, not crawler verdicts. Search engines, social platforms, consent flows, JavaScript rendering, and cache timing can still change what users or bots see.
Check method
Social preview check method
Share preview report = guarded HTML fetch + redirect follow + title + meta description + Open Graph tags + Twitter Card tags + preview image checksThe checker fetches one public HTML URL, follows up to 5 redirects, and blocks local, private, reserved, credentialed, and non-http destinations before each request.
How to use
Steps
- Paste the exact public page URL you want to preview-check.
- Run the check to fetch the final HTML response and share metadata.
- Review title, meta description, Open Graph fields, Twitter Card fields, preview image URL, and warnings.
- Fix missing images, mismatched URLs, missing descriptions, or incomplete card tags before sharing the link.
Example
Sample check
Launch pageVerify og:image and social title before posting a new page
Newsletter linkCheck whether the shared URL has a readable title and description
Campaign QACapture final URL, Open Graph, and Twitter Card fields in one handoff
Checker use
Best for
- Checking launch, migration, campaign, or support URLs before requesting indexing or handing the page to another team.
- Capturing concrete page evidence such as redirects, headers, canonicals, robots directives, metadata, schema, headings, image alt text, or internal links.
Before relying on it
Check first
- Treating one fetched URL as proof that every page, device, locale, redirect, or logged-in state behaves the same way.
- Ignoring fetch guardrails, blocked private destinations, truncated bodies, JavaScript-rendered tags, or platform-specific preview caches.
- Submitting or promoting a page before checking the final URL, canonical target, noindex signals, status code, and source-specific warnings together.
Details
What to know before using the output
GuardrailsPublic http/https only
Localhost, private networks, reserved IPs, credentials, and non-http redirects are blocked to avoid internal-network fetches.
Fetch scopeOne HTML response
The checker reads the fetched HTML. It does not render JavaScript, upload images, or simulate every social network crop.
Image validationURL presence
The checker reports image URLs from tags. It does not download image dimensions or validate platform-specific safe areas.
Benchmarks
How to read the output
Open Graph: Title, description, image, URL.
These fields drive many link previews and are the minimum useful share-card check.
Twitter Card: summary_large_image.
Large-image cards usually need twitter:card plus title, description, and image fields.
Final response: 200-range HTML.
Share metadata checks are most useful after redirects resolve to a successful HTML response.
Method and limitations
Methodology and assumptions
Formula, inputs, limitations and review record
Check method
Share preview report = guarded HTML fetch + redirect follow + title + meta description + Open Graph tags + Twitter Card tags + preview image checks
Inputs used
Page URL, HTTP status, Final URL, Title, Meta description, Open Graph tags, Twitter Card tags, Preview image
Limitations
Web utility checkers use bounded public fetches and visible parsing rules. They do not replace a full crawl, Search Console URL inspection, authenticated testing, or platform-specific debugging tools.
Review record
Method and sources checked on July 12, 2026. The documented method, source timing, validity conditions, and reliance limits were checked on this date.
Method provenanceExternal data · toolkitshelf.social-preview-static-HTML.v1
- Maintained by
- Toolkit Shelf
- Calculation class
- External data
- Method version
- toolkitshelf.social-preview-static-HTML.v1
- Primary source
- User-provided public URL
- Source date
- At each run
- Source checked
- July 12, 2026
- Intended audience
- Site owners, developers, editors, and launch reviewers checking one public URL at a time.
- Valid when
- Preview tags must exist in the fetched static HTML. Platform caches, client rendering, authentication, blocking, and truncation can change real previews.
- Reliance boundary
- The report reads static Open Graph and card metadata; it cannot reproduce every platform cache, crop, scraper user agent, or JavaScript-rendered preview.
- Data freshness
- Each result is a point-in-time server request. Rerun the checker after the page, server, cache, or redirect behavior changes.
Cite this page
Toolkit Shelf. Open Graph + Twitter Card Checker. https://toolkitshelf.com/tools/social-preview-checker
FAQ
Common questions
Does this show the exact preview every platform will render?
No. It reads page metadata and flags missing fields. Platforms can cache old metadata, crop images differently, or apply their own fallback rules.
Does it validate image size?
No. It reports the image URLs found in Open Graph and Twitter tags. Check dimensions and crops in the target platform's preview tool before launch.
Why does the checker block private or localhost URLs?
A public metadata checker must not fetch internal network targets. Blocking local, private, reserved, credentialed, and non-http destinations reduces SSRF and proxy-abuse risk.
Leave passwords, account numbers, and private medical or tax information out of your report.