← denizkasap.net

Used for canonical link and og:url. Determines the domain shown in previews.

Shown as the clickable headline in Google and the card title on social platforms.

Shown below the title in Google (up to ~160 chars / ~920 px) and in social card bodies.

Recommended size: 1200 x 630 px. Used by Twitter, Facebook, LinkedIn, and iMessage.

Google Search Result
example.com › my-page
Your page title
A short description of your page will appear here.
Twitter / X — Summary Large Image
No image URL provided
example.com
Your page title
A short description of your page.
Facebook Link Preview
No image URL provided
EXAMPLE.COM
Your page title
A short description of your page.
LinkedIn Post Preview
No image URL provided
Your page title
example.com
iMessage / Apple Link Preview
Check this out 👀
Generated HTML

Why do meta tags matter?

When someone shares your URL on social media or messaging apps, those platforms fetch the page and read its Open Graph and Twitter meta tags to generate a rich link preview. The image, title, and description that appear before anyone clicks.

A missing or poorly configured og:image means your link shows up as a bare URL with no visual context. On platforms like Slack and Discord, it often means no preview at all.

Which tags does this tool cover?

The generated code includes:

These cover Google, Twitter/X, Facebook, LinkedIn, iMessage, Slack, Discord, and most other platforms that generate link previews.

Image size guidelines

Recommended dimensions per platform:

A single 1200 x 630 px (1.91:1) image covers all platforms without cropping issues. Keep the file under 5 MB and prefer PNG or JPEG. WebP is supported by all major social platforms but may not render correctly in feed readers, note-taking apps, or other tools that consume OG data.

Title and description length

Google truncates titles based on pixel width, not character count. The cutoff is roughly 600 px on desktop, which works out to around 50-60 characters for average mixed-case Latin text. Wide characters (W, M, uppercase runs) hit the limit earlier; narrow characters (i, l, t, 1) later. The counters in this tool use 60 characters as a practical heuristic, but the real limit is inherently fuzzy. On mobile, the pixel budget is narrower, so a title that fits on desktop may still truncate on mobile.

Google also rewrites titles it considers keyword-stuffed, misleading, or not representative of the page content regardless of length. Staying under 60 characters doesn't guarantee your title displays as written.

If you use a Title | Brand pattern, only the left portion reliably fits within the visible cutoff. The brand segment may be truncated or dropped entirely. Whether to count the brand suffix toward your character budget depends on how much you care about it showing consistently.

Descriptions follow the same pixel-width logic as titles. Google's cutoff is roughly 920 px on desktop, which works out to around 155-160 characters for average mixed-case Latin text — but wide characters will hit it earlier. On mobile the budget is narrower, closer to 120 characters.

Do these previews perfectly match every platform?

These are close approximations. Each platform applies its own fonts, colours, cropping logic, and fallback behaviour, and they can change without notice. For verification after publishing: the Twitter Card Validator no longer exists, so the only way to test is to post a tweet with the URL. The Facebook Sharing Debugger requires a Facebook login. LinkedIn Post Inspector works without one.

est. 2024