See how any link looks when it is shared on X, LinkedIn, Facebook, and Slack. Check the Open Graph and X card tags, the image size, and get a fix for every issue.
Each free tool covers one piece. A free SEO audit covers your technical setup, on-page content, links, and AI visibility together.
Get your free SEO auditSend your site and Furqan will personally review your backlinks, brand mentions, technical and on-page SEO, and AI visibility. You'll hear which service fits, or that you don't need one yet.
Prefer email?
furqan@chungdigital.comEnter any public URL. We fetch it the way crawlers and social bots do, then run every check.
Example result for a made-up page. Enter your URL to check your own.
Page score
Indexable74/100
32 passed · 9 warnings · 2 errors
example.com
Acme pricing
Uptime checks, alerts, and status pages for every API. Start free for 14 days.
Card type: not set (X may show a small card). Image: 800 x 418.
| Tag | Content |
|---|---|
| og:title | Acme pricing |
| og:description | Uptime checks, alerts, and status pages for every API. Start free for 14 days. |
| og:image | https://www.example.com/images/pricing-card.png |
| og:type | website |
| og:site_name | Acme |
Chung Digital AI
Get the issues from this scan ranked by impact, with what to do first. It reads the check results listed below, not your whole page, and is told not to invent facts.
What it reads
Ask for a fix plan for this page, in priority order.
A Twitter card is the preview box that appears when someone shares a link on X: an image, a headline, and the site name. X builds it from twitter: meta tags in the page's HTML, and falls back to Open Graph tags when those are missing.
The twitter:card tag picks the layout. summary shows a small square image next to the text, and summary_large_image shows a wide image above it. For blog posts, launches, and landing pages, summary_large_image is usually the one you want.
<meta name="twitter:card" content="summary_large_image"> <meta property="og:title" content="Your headline"> <meta property="og:description" content="One or two sentences."> <meta property="og:image" content="https://www.example.com/card.png"> <meta property="og:image:alt" content="What the image shows">
Open Graph (og:) tags were created by Facebook and are now read by LinkedIn, Slack, Discord, iMessage, WhatsApp, and most other apps that unfurl links. One good set of Open Graph tags covers almost every platform.
This tool works as an Open Graph debugger: it fetches your page the way these bots do, shows a preview for each platform, and checks that the image actually loads and is the right size.
When a card is wrong or missing, it is almost always one of these.
Social bots don't run JavaScript. If your framework adds meta tags in the browser, the bots never see them. Render them on the server or prerender the page.
A relative URL, a login wall, a firewall that blocks bots, or an image that is too large all stop the preview. This tool fetches the image to check.
Platforms cache previews. After you fix the tags, refresh the cache with LinkedIn's Post Inspector or Facebook's Sharing Debugger, or share the URL with a query string.
Our SaaS SEO services cover technical and on-page SEO across your whole site. Or request a free SEO audit and we will tell you which fixes matter most.
X no longer shows a preview in its own card validator, so you can only see the card by drafting a post. This tool fetches your page, reads the twitter: and Open Graph tags, and shows the card without posting anything.
Yes. When twitter:title, twitter:description, or twitter:image are missing, X uses og:title, og:description, and og:image instead. You still need twitter:card to choose the card layout.
1200 x 630 pixels (a 1.91:1 ratio) is the safe choice. It shows well on X, LinkedIn, Facebook, and Slack. Keep the file under 5 MB and the important content in the middle.
LinkedIn caches link previews. After you update your tags, paste the URL into LinkedIn's Post Inspector to fetch a fresh copy.
This checker reads the HTML your server sends, before any JavaScript runs. If your site adds tags or headings with JavaScript, they appear in your browser but not in the raw HTML. Google can render JavaScript, but social apps and many AI crawlers read only the raw HTML, so tags added later may never reach them.
Not directly. Google does not use them to rank pages. They decide how your links look when shared, which affects clicks from social posts, chats, and newsletters.
Yes. We save the URL you check, the results, and any error for 12 months, with your IP address and approximate location, so we can find what goes wrong and improve the checker. If you use the AI fix plan, the list of failed checks and the page's title, description, and H1 are sent to our AI provider to write the plan. See our privacy policy.