How to use it
- 1Enter the page you want to share and press Fetch tags. We read the page's
<head>and fill in the fields. - 2Look at the four previews. Missing images and truncated titles are obvious at a glance; the checks list explains each problem.
- 3Edit any field to test a fix — the previews update as you type. Starting from scratch works too: skip the fetch and fill the fields in.
- 4Switch to HTML and copy the tags into your page's
<head>, or into your framework's metadata settings.
Examples
The missing image
A landing page has a good title and description but no og:image. Google looks fine; X, LinkedIn and Slack show a bare grey card that people scroll past. The checks flag it as an error — add a 1200 × 630 image and all three previews fill in.
A title that gets cut off
“Acme — The AI-Powered Invoice Automation Platform for Growing Finance Teams” is 75 characters. Google's preview ends mid-phrase; the counter above the field turns the problem into a number. “Acme: AI invoices in 30 seconds” says more in 31.
Relative image paths
og:image set to /images/share.png works in some apps and silently fails in others. The fetch resolves it to a full URL for the preview and the checks warn you to put the absolute https:// address in the tag itself.
What we fetch and how previews are drawn
When you press Fetch tags, our server requests the page once with a normal browser-like request, follows up to three redirects, reads at most 768 KB and stops as soon as </head> arrives. It reads <title>, the canonical link, the favicon and every og:*, twitter:* and description meta tag, resolving relative URLs against the final address. Results are cached for ten minutes and never saved.
The previews are drawn in your browser from the fields, using each platform's typical layout and truncation: about 60 characters for a Google title and 155–160 for its description, a 1.91:1 image for X large cards, LinkedIn and Slack. Your structured data is a separate layer — generate it with the schema markup generator.
Limitations
- infoPreviews approximate each platform's current design; the platforms change their layouts and truncation rules without notice.
- infoGoogle often rewrites titles and descriptions in results. The preview shows what you asked for, not a guarantee of what Google displays.
- infoPages that build their meta tags with JavaScript after load, or that block bots, may show fewer tags here than a platform's own crawler sees.
- infoFor safety, only public http(s) pages on ports 80 and 443 can be fetched, and each visitor can run about 20 checks every 10 minutes.
Questions people ask
What size should an og:image be?
add
1200 × 630 pixels (a 1.91:1 ratio) works on every major platform. Keep the important text and logo away from the edges, because some apps crop to a square or a narrower rectangle, and keep the file under 5 MB.
Why does my link still show the old preview after I fixed the tags?
add
Social platforms cache previews. X and LinkedIn refresh after some time or when you re-inspect the URL in LinkedIn's Post Inspector; Facebook has a Sharing Debugger with a “Scrape Again” button; Slack and messaging apps keep their own caches for a while. Adding a harmless query string such as ?v=2 to the shared link forces a fresh fetch.
Do I need both Open Graph and Twitter tags?
add
X falls back to Open Graph tags when twitter:title, twitter:description and twitter:image are missing, but it does need twitter:card to choose the large-image layout. The generated HTML includes both sets so every platform gets exactly what you intend.
Does og:title affect Google rankings?
add
No — Google uses the <title> element and the page content. Open Graph only controls how links look when shared. It's common, and fine, to use a slightly punchier og:title than the SEO title.
Why can't the tool fetch my page?
add
The page may block unknown bots, require a login, respond too slowly (we wait six seconds), or return something other than HTML. Pages on private networks, localhost or non-standard ports are refused on purpose. You can still paste your tags into the fields and preview them.