SEO Meta Tag Previewer & Generator

Aim for roughly 50-60 characters, but Google truncates by pixel width, not character count: around 580-600 pixels on desktop. Wide characters like "W" and "M" eat up more pixels than narrow ones like "i" or "l", so two titles with the same character count can wrap differently. Keep your primary keyword and brand name within the first 55 characters to be safe. Use a live preview tool (like the one above) rather than a character counter alone, since it renders against the actual pixel constraint.

Target 140-155 characters. Google's cutoff is pixel-based too: about 920 pixels on desktop and roughly 680 pixels on mobile. The effective character limit shifts depending on which letters you use. Google also frequently rewrites or truncates descriptions it thinks don't match the search query, sometimes pulling a different snippet straight from your page content instead of your meta description. Write for both the searcher and the algorithm rather than treating the description as a fixed ranking lever.

Google cuts the string at the nearest whole word (not mid-word) once it exceeds the pixel budget, then appends an ellipsis ("..."). This means your brand name or call-to-action at the end can silently disappear from search results even though the HTML is unchanged. Front-load the most important keywords and value proposition in the first 50-55 characters of both the title and description so the message survives truncation on any device.

The HTML <title> tag is the traditional SEO signal: browsers show it in the tab, and Google uses it as the default headline in organic search results. og:title is an Open Graph property that social platforms (Facebook, LinkedIn, Discord, Slack) read to build link-preview cards. It can be worded more conversationally or clickably, since it targets a social feed rather than a search query. Google has also started using og:title as a fallback signal for the search title link in some cases, so keep the two reasonably consistent to avoid an unexpected title in search results.

Facebook, LinkedIn, and other platforms cache the Open Graph data from the first time a URL is shared, so updating your meta tags doesn't retroactively update old previews. Facebook caches for about 30 days and requires you to run the URL through the Sharing Debugger (developers.facebook.com/tools/debug) and click "Scrape Again" (sometimes two or three times) to force a re-crawl. LinkedIn holds its cache for up to 7 days and needs a manual refresh via the Post Inspector (linkedin.com/post-inspector). X/Twitter re-crawls more frequently but you can force it by appending a dummy query parameter (e.g. "?v=2") to bust the cache while testing.

1200×630px (a 1.91:1 aspect ratio) is the universal default that renders cleanly across Facebook, LinkedIn, Discord, Slack, WhatsApp, and X's summary_large_image card. Facebook's hard minimum is 600×315px; it rejects images under roughly 200×200px outright. Keep the file under 1MB (8MB hard cap on Facebook), use JPG, PNG, or WEBP, and keep any text or logo inside the center ~1080×600 "safe zone" since some platforms crop the edges differently when rendering the card.

X's crawler checks for twitter:* tags first and falls back to the equivalent og:* values (og:title, og:description, og:image) when they're missing. In practice, if your Open Graph tags are already correct, the only tag you need to add is <meta name="twitter:card" content="summary_large_image">, since X won't render a large-image card unless you declare an explicit card type. Adding the full set of twitter:title, twitter:description, and twitter:image tags is still good practice if you want copy that reads differently on X than it does on Facebook or LinkedIn.