Open Graph Checker for Social Meta Tags and Twitter Cards
Free individual check · without registration
Read open graph and Twitter card details of a URL. Compare social title, description, image address, and destination URL and check for hints of missing or duplicate meta tags.
- Uses Absolute URLs in og:image, og:url, Twitter:image.
- Settling og:title & og:description explicitly – not only as a fallback
<title>. - If you have many redirects: Check final_url, Canonical and og:url on consistency.
- Server fetch incl. Redirect sequence
- Basics: Title, Meta Description, Robots, Canonical
- Open Graph: og:* Meta Tags
- Twitter: * Meta Tags
- Issues: missing mandatory fields, relative URLs, multiple tags, noindex
| Key | Value |
|---|---|
| No data yet. | |
| Key | Value |
|---|---|
| No data yet. | |
| Key | Value |
|---|---|
| No data yet. | |
| Key | Value |
|---|---|
| No data yet. | |
Check Open Graph and Twitter Cards for Shared Links
Which social meta tags are evaluated?
The check retrieves the HTML of the URL and reads og:* and twitter:* information. In addition, Title, Meta Description, Robots and Canonical. The check reports selected missing fields, relative URLs and multiple data. It is a technical inventory of the delivered tags; it does not render a binding preview for Facebook, LinkedIn, WhatsApp or X.
og:image present, but no preview image visible
First, check the image address: Is it absolute, publicly accessible and the intended subject? The checker reads the image URL from the markup, but does not itself check the retrieval and dimensions of the image file. Login, bot protection or an outdated platform preview can prevent the display. Open the image address separately and compare the behavior of the respective service.
Clean up duplicate tags and different URLs
CMS, SEO plugin and theme can simultaneously generate social tags. Set a responsible output and remove conflicting duplicates. og:url is intended to denote the intended public side; compare it with the actual goal and the canonical. A suitable image description via og:image:alt or twitter:image:alt complements the markup.
Social preview and Google snippet differ
Open Graph and Twitter Cards are aimed at supporting platforms when sharing a link. The Google title link and the search nipple are a different presentation. A correct og:image is not proof of better Google rankings. For title and meta description in the search preview, use the SERP Snippet Generator; for social cards, you also control the result directly at the platform.
Why a shared picture is missing
Practical example · for illustration
Starting position
Check the published URL whose link preview appears incorrect.
Classify the findings
og:image may exist while the image URL redirects to a login or error.
Specific amendment
Use absolute, publicly accessible image URLs and remove conflicting OG tags in the CMS.
Control and border
Retrieve the image separately and re-check the page. Platform caches can keep an old preview; a correct social meta tag is not a direct Google ranking proof.
Questions about use and boundaries
Can I use it to check my WhatsApp or LinkedIn preview?
You can examine the delivered social tags as a technical basis. Whether and how a service uses them depends, among other things, on its retrieval, cache and presentation.
Does the checker check the picture himself?
No. He determines the image address and hints from the meta tags. Accessibility, image dimensions, subject and blank must be checked separately.
Why does the old picture still appear after a change?
Platforms can cache older previews. First check the currently delivered tags and then the possibilities of the respective service to retrieve the URL.
Do I need twitter:* tags even after renaming to X?
The technical metadata is still called twitter:card, twitter:title and other twitter:* fields. A renaming of the prefix to x: is not provided for this purpose.