Loading…
Fill in six fields, get a complete copy-paste <head> block — title, description, canonical, Open Graph, and Twitter cards — with a live preview of how your link will look when shared.
<title>Acme Analytics — Privacy-first analytics</title> <meta name="description" content="Understand your users without cookies. Set up in 5 minutes, GDPR-compliant out of the box."> <link rel="canonical" href="https://example.com/analytics"> <!-- Open Graph --> <meta property="og:type" content="website"> <meta property="og:title" content="Acme Analytics — Privacy-first analytics"> <meta property="og:description" content="Understand your users without cookies. Set up in 5 minutes, GDPR-compliant out of the box."> <meta property="og:url" content="https://example.com/analytics"> <meta property="og:site_name" content="Acme"> <!-- Twitter / X --> <meta name="twitter:card" content="summary"> <meta name="twitter:title" content="Acme Analytics — Privacy-first analytics"> <meta name="twitter:description" content="Understand your users without cookies. Set up in 5 minutes, GDPR-compliant out of the box.">
It generates every tag a modern page head needs, correctly escaped and in one block: the <title>, meta description, canonical link, the core Open Graph set (og:title, og:description, og:url, og:site_name, og:image with dimensions), and Twitter card tags — choosing summary_large_image automatically when you provide an image. The two preview cards approximate how X and generic OG consumers (Slack, LinkedIn, iMessage) will render your link, loading your actual image URL.
Everything runs in your browser. If a field is empty, its tags are simply omitted rather than emitted blank.
For a SaaS product, links get shared in Slack workspaces, DMs, and social feeds constantly — and each share either renders as a rich card that looks like a real product, or as a bare gray URL that looks abandoned. The difference is a dozen lines of markup. Meanwhile the title and description you ship are the copy Google shows (and rewrites less when they're well-formed and the right length).
Meta tags handle how your page looks when shared; structured data handles how it looks in search. They complement each other: check your title and description lengths in the SERP snippet preview, then add JSON-LD with the schema generator — including the AggregateRating markup that earns review stars.
<head> (or your framework's metadata config) and re-share the link to refresh platform caches.Open Graph (og:) tags control how your page appears when shared — the image, title, and description in link previews on Slack, LinkedIn, Facebook, iMessage, WhatsApp, and most chat apps. Without them, platforms guess, often badly.
1200×630 pixels (1.91:1 ratio) is the safe standard: full-width large cards on Twitter/X and correct rendering on LinkedIn, Facebook, and Slack. Keep important content away from the edges — some platforms crop.
Mostly yes. X falls back to OG tags for content, but twitter:card is what requests the large image layout (summary_large_image), and twitter:site attributes your handle. The generator emits both sets so every platform gets what it looks for.
It tells search engines which URL is the definitive version of the page, consolidating signals when the same content is reachable at multiple URLs (tracking parameters, http/https, trailing slashes). Every indexable page should declare one.
The description doesn't directly, but the title tag is a ranking signal and both drive click-through rate. Social tags don't affect rankings at all — they affect whether people click your link when it's shared, which is where much SaaS traffic actually comes from.
TWR adds AggregateRating schema to your public review page automatically — free. Collect verified reviews inside your app and let us handle the structured data.