MetaPeek
Open Graph and meta tag preview
That page is large, so only the first part was read. Meta tags normally sit in the head, so this rarely changes the result.
Why the preview differs from what you wrote
Search engines and social platforms do not simply print your tags. Google rewrites titles it judges unhelpful — often to the site name or an on-page heading — and ignores your meta description entirely when a passage from the page answers the query better. Facebook and LinkedIn cache the first version of a card they ever see, sometimes for weeks.
So treat this as what the platforms have been given, not a guarantee of what they will show. It is still the useful view, because everything they show is derived from it, and a missing tag is a decision handed to somebody else.
Which tags actually matter
og:image is the one worth checking before anything else. Without it, a
shared link is a line of grey text, and it will be scrolled past. The image should be
at least 1200×630 for a large card, and declaring og:image:width and
og:image:height lets a platform lay the card out before it has downloaded
the picture.
twitter:card decides between a small square thumbnail and a full-width
image on X; summary_large_image is almost always what you want. The
remaining Twitter tags are optional — X falls back to the Open Graph equivalents when
they are absent, which is why duplicating them all is usually wasted effort.
A canonical link tells search engines which address is the real one when
several show the same content. Getting it wrong is worse than omitting it: a canonical
pointing at the wrong page can remove the right one from search results.
Lengths, and where things get cut
Titles are truncated around 60 characters and descriptions around 160, though both are measured in pixels rather than characters, so a title full of capitals is cut sooner. Neither limit is a rule — a longer description is not penalised, it is simply trimmed with an ellipsis, and the part you cared about may be the part that vanished.
Put the important words first. That advice survives every algorithm change, because it holds whether the text is truncated by a search engine, a share card, a browser tab or a phone notification.
How the check is made
This is the only tool here that uses the server, because a browser is not permitted to read another site's HTML — the same-origin policy exists to prevent exactly that. The page is requested from this server, so the site you inspect sees a request from util.quest rather than from you.
Only public addresses on ports 80, 443 and 8080 are fetched, redirects are followed by hand and re-checked at every hop, and the response is capped in both time and size. The share image is passed through as well rather than loaded directly by your browser, so inspecting a page does not disclose your address to its image host.
This tool uses the util.quest server. It cannot run in your browser — the work is either impossible there or too heavy for it. What you submit is sent to this server, used to produce the result, and not stored afterwards. Requests are rate limited, and nothing about them is logged beyond what is needed to enforce that.
Check how a page will look when it is shared before you ship it. MetaPeek reads a URL's Open Graph and Twitter card tags and renders faithful previews, flagging fields that are missing or too long.
It's one of the free tools in the util.quest collection — nothing to install, and no account needed. Found a bug or want a feature? Reach out at [email protected].
