Paste a URL and see the card X, LinkedIn, Facebook, Slack, Discord, and Google will each build from it, with the tag behind every line.
Free, no login, no email. Nothing stored beyond a 24 hour cache. Markdown copy · API and MCP
Paste any URL
We fetch that one page the way a browser would and read the tags in its head. No login and no email.
We apply each platform's own rules
Every platform reads a different set of tags in a different order. We follow each one's order separately, so you get six answers rather than one.
See the card, and the tag behind it
Each preview shows where its title, description, and image came from, where the text will be cut, and what that platform will do differently.
Most preview checkers answer one question: are the tags there. That is the wrong question, because no platform reads all of them and no two read them in the same order. X looks for twitter:title first and falls back to og:title. Slack takes og:image, then twitter:image. LinkedIn reads og:description and then the meta description. Facebook cuts a title at about 88 characters. Google cuts one at about 60.
So a page can carry a complete set of tags and still show six different things. The only useful answer is per platform: this is your headline on X, this is where it gets cut, and this is the tag it came from. That last part is what makes it fixable. Knowing your title is wrong helps less than knowing it came from twitter:title.
Here is the most common version of the problem. You add a good 1200 by 630 og:image. It looks right on LinkedIn and right in Slack. On X it renders as a small square thumbnail beside two lines of text, and it looks like an afterthought.
Nothing is broken. X decides the layout from twitter:card, not from your image. Without twitter:card set to summary_large_image, X uses the small card no matter how good the picture is. It is one line in your head tag, and it is invisible to any check that only asks whether an image tag exists.
The other half people miss is that Google does not use Open Graph for search snippets at all. It reads the title tag and the meta description. Teams that set og:title carefully and leave the title tag as whatever the CMS generated end up with a link that looks polished when shared and wrong in search results, which is where far more people will see it.
That is why a search result sits alongside the share cards here. They are different systems reading different tags, and checking one tells you nothing about the other.
Platforms cache what they scraped. Once a bad card is out, editing your tags does not fix the post that is already live. Facebook and LinkedIn will re-scrape a URL on request. X and Slack mostly will not. So the check that counts is the one you run before you hit post, not the one you run after somebody replies to say the image is missing.
Because each platform reads a different set of tags in a different order. X looks for twitter:title before og:title. Slack reads og:image and then falls back to twitter:image. Google reads neither and uses the title tag and the meta description. So the useful question is not whether your tags are present. It is what each platform will actually show, which is what this tool answers.
The same run this page does, as an HTTP endpoint and as the MCP tool check_social_preview. No account, no API key. Full reference.
curl -sS https://usesuperflow.ai/api/tools/social-preview \
-H 'Content-Type: application/json' \
-d '{"url":"example.com"}'Returns { ok, report: { previews[] per platform, tags, summary, findings[] }, cached, ageSeconds }. 10 runs per hour per IP. Allow up to 75 seconds.
claude mcp add --transport http superflow https://usesuperflow.ai/api/mcpThen ask your agent for check_social_preview. Setup for Claude Desktop, Cursor and VS Code is on the reference page.
No login, no email, no ads. Same as this one.
Superflow agents watch your live pages and tell you when a tag changes, an image stops loading, or a title quietly grows past the length a platform will show.