Free · Fast · Privacy-first

Social Media Meta Tags Generator

When your content gets shared on Facebook, X, LinkedIn, WhatsApp, Slack, Discord, or any of the dozens of other platforms that support link previews, social meta tags are the only thing standing between a polished, click-worthy card and an awkward bare URL that nobody bothers to tap.

⚡

Open Graph tags for Facebook, LinkedIn, WhatsApp

🔒

Twitter Card tags for X (Twitter)

✨

Social preview simulation

⚡

No sign-up required

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Meta Tags to your website

Drop the Meta Tags into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/seo-tools/meta-tags?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Meta Tags by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/seo-tools/meta-tags?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Meta Tags by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Social Meta Tags by Platform: Which Tags Each Network Uses and Why

The Open Graph protocol originally introduced by Facebook in 2010 now serves as the universal social sharing standard, supported natively by Facebook, LinkedIn, WhatsApp, Slack, Discord, iMessage, Telegram, Pinterest, Reddit, and dozens of other platforms that adopted the protocol to render link previews consistently. When none of the twitter prefixed or platform-specific tags are present on a page, all these platforms fall back to og:title, og:description, og:image, and og:url, which means a single solid Open Graph implementation covers ninety-five percent of social sharing destinations across the modern web. X, formerly known as Twitter, is the only major platform with its own complementary namespace using the twitter prefix, and even X falls back to OG tags when twitter tags are absent on a given page. The practical implication for most sites is that implementing a thorough Open Graph tag set covers the vast majority of social platforms with a single, maintainable implementation, while Twitter Card tags add optional customisation for X-specific features like the Summary Large Image card that dominates the timeline.

Platform-specific image rendering varies enough to matter for high-traffic content where small differences in preview quality compound across thousands of shares. Facebook renders OG images at a recommended twelve hundred by six hundred thirty pixels in a 1.91 to 1 aspect ratio, and images below four hundred by two hundred nine pixels display as small thumbnails rather than the prominent large card that drives the most engagement. LinkedIn's recommended image is twelve hundred by six hundred twenty seven pixels, rendered at approximately five hundred twenty pixels wide in the feed where it competes with native LinkedIn posts for attention. X uses twelve hundred by six hundred seventy five pixels in a 16 to 9 ratio for Summary Large Image cards, slightly taller than the OG standard. WhatsApp and iMessage typically use the og:image as-is at whatever dimensions you provide, although both prefer images with file sizes under five megabytes to load quickly on mobile networks. For most implementations, the twelve hundred by six hundred thirty pixel standard provides the best cross-platform compatibility without requiring multiple image versions per page.

Open Graph tag caching is a frequently misunderstood issue that catches teams off-guard during campaign launches, and understanding the cache behaviour of each platform is essential for any time-sensitive social rollout. Facebook caches OG data for up to thirty days, meaning a shared link may show outdated content for the full cache period after you update your source tags. Force a cache refresh by pasting the URL into the Facebook Sharing Debugger at developers.facebook.com/tools/debug/ and clicking Scrape Again, which forces an immediate fresh fetch and propagates the new preview to Facebook, Instagram, and WhatsApp. LinkedIn's cache typically clears within twenty-four hours but you can force an immediate refresh using LinkedIn's Post Inspector. X and Slack typically reflect updated tags within a few hours of the change going live. Plan all OG tag updates at least twenty-four to forty-eight hours in advance of any campaign to avoid cache-related preview issues at the worst possible moment.

The most overlooked dimension of social meta tag quality is matching the copy style to the platform context rather than reusing the SEO title and description verbatim across both search and social. SEO descriptions are written for active searchers who already know what they want and need to be convinced your page answers their specific query, while social descriptions are written for passive scrollers in discovery mode who need to be persuaded that the link is worth interrupting their feed to investigate. The same one hundred fifty character string rarely performs optimally in both contexts. For high-priority pages, write a distinct og:description that leans more emotive, curiosity-triggering, and benefit-led than the parallel SEO description. Use og:title to test more conversational or pattern-breaking phrasings without affecting your search rankings. The small effort of writing two versions consistently outperforms reusing a single version everywhere on every measurable engagement metric.

Open Graph Protocol: Official Documentation Facebook Sharing Debugger: Force Cache Refresh

How to use this tool

💡

Enter your page title, description, image URL, and URL to generate a complete social meta tag set for all major platforms.

How It Works

Step-by-step guide to social media meta tags generator:

1
Enter your page URL and title
Add the canonical URL of the page exactly as you want it indexed and shared, using the HTTPS production address rather than any staging or localhost URL, and enter the title you want displayed across every social platform when the page is shared. The og:title can differ from your SEO title if a more social-friendly phrasing would perform better in feed contexts, but the canonical URL must match the live production address that the page actually resolves to in the browser.
2
Write your social description
Write a one to two sentence description optimised specifically for social sharing rather than reusing the SEO meta description verbatim. Social copy can be more emotive, more curiosity-driven, and more explicitly call-to-action focused than search copy because the audience is in a scrolling discovery mindset rather than active search mode. Aim for around one hundred fifty to two hundred characters, ending on a phrase that motivates the click without crossing into clickbait territory.
3
Add your social image
Upload or enter the absolute HTTPS URL of a twelve hundred by six hundred thirty pixel image that will be used by Facebook, LinkedIn, WhatsApp, Slack, Discord, and most other platforms via the og:image property. The image should be hosted on a fast, reliable URL that returns a 200 status without redirects or authentication requirements. For high-priority content also planning a strong push on X, prepare a separate twelve hundred by six hundred seventy five pixel image and assign it as twitter:image to avoid cropping.
4
Generate and deploy all tags
Generate the complete Open Graph plus Twitter Card tag set, copy the resulting HTML block, and paste it directly into the head section of your page near the top before any large script tags. After deployment, test each major platform using their respective preview tools, Facebook Sharing Debugger, LinkedIn Post Inspector, and the X Card Validator, forcing a fresh scrape on any platform where you previously had different tags so the corrected preview propagates immediately rather than waiting on natural cache expiry.

Real-world examples

Common situations where this approach makes a real difference:

Viral content preparation

A digital marketing team preparing an industry report for a coordinated social release generates a complete social meta tag set ahead of launch and commissions a custom twelve hundred by six hundred thirty pixel OG image that visually summarises the report headline finding. The team adds a separate twelve hundred by six hundred seventy five Twitter image so the card renders edge to edge on X, writes a distinct og:description that hooks scrollers with a curiosity gap rather than reusing the SEO description, and validates everything in the Facebook Sharing Debugger forty-eight hours before launch. Every share by the company executives, partners, and analyst network now generates a polished preview that visibly outperforms the bare-URL drops typical of competitor research releases.

WhatsApp link preview fix

A property agency notices their listing pages show no image and only a bare URL when shared in WhatsApp group chats, where most of their inbound buyer leads originate during peak weekend browsing hours. The developer adds Open Graph tags with the primary property photo as og:image, the listing headline as og:title, and a concise feature summary as og:description, then validates the result on a test phone. The fix takes under thirty minutes per template change and immediately transforms every WhatsApp share into a visual preview that drives measurably higher click-through, with the agency reporting a noticeable lift in qualified enquiries within the first week of the fix.

Slack channel sharing optimisation

A SaaS company's customer success team shares documentation links inside customer Slack channels dozens of times per day, and the engineering team notices the links unfurl with no preview because the docs site was launched without Open Graph tags. Adding a templated OG tag set across every documentation page, including a generic but on-brand og:image and a description pulled from the article excerpt, ensures every shared link now unfurls with the article title, description, and a relevant image. The change makes the support team's answers more skimmable inside Slack, and customers click through more readily because the preview signals that the link is helpful documentation rather than a random URL.

When to use this guide

Use this when preparing content for a social media campaign, launching a new page that will be shared widely, or fixing broken social sharing previews across platforms.

Pro tips

Get better results with these expert suggestions:

Refresh OG cache before every major campaign

Social platforms cache Open Graph data aggressively, sometimes for up to thirty days on Facebook, which means a shared link may show outdated content well after you have updated your source tags. Before any campaign launch, paste each key URL into the Facebook Sharing Debugger and LinkedIn Post Inspector and click the refresh or scrape again button to force an immediate fresh fetch. Do this at least twenty-four hours in advance so you have time to fix any issues found before the campaign actually goes live and the corrected preview has propagated across every platform.

Write social descriptions differently from SEO descriptions

Your og:description serves social audiences who are in a scrolling, discovery mindset, not in active search mode, so the persuasion mechanics that work on a SERP rarely translate directly to a feed environment. Write the og:description to be more emotive, benefit-led, and curiosity-triggering than your SEO meta description, which should remain query-aligned and factual. The same one hundred fifty character string rarely wins in both contexts, and the small effort of writing two versions consistently outperforms reusing a single version across both touch points across every measurable engagement metric.

Create platform-specific images for high-traffic content

For content that will be actively promoted on both Facebook and X, create two distinct images sized for each platform: a twelve hundred by six hundred thirty pixel image used as og:image and a twelve hundred by six hundred seventy five pixel image set as twitter:image. The small aspect ratio difference between the two platforms means your perfectly composed OG image may be slightly cropped at the top or bottom on X, hiding logo placements or headline text that depended on the full canvas. Two images add ten minutes to the design pipeline but eliminate the visible cropping that quietly depresses engagement.

Add og:locale for multilingual content

Setting og:locale to the correct language and region code, for example en_US, fr_FR, de_DE, or es_MX, helps social platforms distribute your content to users who actually read that language rather than algorithmically guessing based on geographic or behavioural signals. Without an explicit locale declaration, platforms may show your content to audiences who cannot read the page, depressing engagement and confusing the algorithmic distribution signal. For international sites with multiple language versions of the same content, also include og:locale:alternate tags for each additional supported language so platforms can route correctly.

Test previews on each target platform

Facebook, LinkedIn, and Twitter all render social cards slightly differently. Use each platform's developer tools (Facebook Debugger, LinkedIn Post Inspector, Twitter Card Validator) to confirm your tags look right on each.

Use platform-specific images where possible

If your page will be heavily shared on Twitter specifically, using a 1200x675px image (Twitter's preferred ratio) will look better than the 1200x630px standard OG image, which can appear slightly cropped.

Set og:locale for international content

If your page is in a language other than English, setting the og:locale tag (e.g., "fr_FR" for French) helps platforms serve the content to the right audience and improves engagement.

FAQ

Frequently asked questions

Facebook, Instagram, LinkedIn, WhatsApp, Slack, Discord, Pinterest, iMessage, Telegram, Reddit, Skype, and most other social and messaging platforms use Open Graph meta tags to generate link previews when a URL is pasted or shared inside their interface. X, formerly Twitter, has its own complementary Twitter Card namespace but falls back to Open Graph tags whenever Twitter-specific tags are absent on a given page. Email clients like Outlook and Gmail are also increasingly rendering OG previews inline when URLs appear in message bodies. The practical implication is that a single solid Open Graph implementation covers essentially every modern destination where your content might be shared, making OG the highest-leverage social metadata work you can do on any site.

Not directly, because social meta tags are not a confirmed Google ranking factor and do not influence the core ranking algorithm in any documented way. However, pages with compelling og:image and og:description values get shared significantly more on social media, and that increased sharing drives meaningful indirect SEO benefits across multiple dimensions. More shares produce more referral traffic, more brand-name searches over time, more inbound links from people who discover the content through social and decide to cite it from their own sites, and more brand recognition that lifts click-through on existing search rankings. Across a six to twelve month horizon, sites that invest in social metadata quality consistently outperform sites that ignore it on organic search performance, even though the mechanism is indirect.

Without Open Graph tags, social platforms attempt to extract preview content directly from the page body using heuristic scraping, and the results are almost universally poor. You typically get a random image picked from the page based on opaque platform logic, an awkward text excerpt as the description that may begin or end mid-sentence, and the raw HTML page title as the share title regardless of whether it suits the social context. The resulting preview looks unprofessional next to properly tagged competitor content in the same feed, generates measurably fewer clicks per impression, and signals to algorithmic distribution that the link is low-quality content that should be suppressed in subsequent feed ranking. Setting OG tags is genuinely table stakes for any page you expect to be shared.

Use the platform-specific developer tools that each major network provides for exactly this purpose. The Facebook Sharing Debugger at developers.facebook.com/tools/debug handles Facebook, Instagram, and WhatsApp previews and lets you force an immediate cache refresh. The LinkedIn Post Inspector at linkedin.com/post-inspector handles LinkedIn previews with similar refresh control. The X Card Validator shows how your link will render across X. Each tool displays a live preview of the link card alongside any errors or warnings the platform parser surfaced, making it easy to catch missing images, oversized titles, or incorrect aspect ratios before any audience actually sees the share. Run all three tools as part of every pre-launch validation pass.

GIFs are technically supported as og:image by most platforms including Facebook and X, which will display animated GIFs in some link preview contexts. However, animated GIFs are typically five to twenty times larger in file size than equivalent static images, which slows down link preview loading on mobile networks and can cause some platforms to fall back to a static frame or skip the image entirely if the file exceeds size limits. Using a high-quality static JPEG or PNG is generally better for cross-platform consistency, faster preview rendering, and predictable display behaviour. Reserve animated GIFs for cases where the motion itself communicates something the static image cannot, and always test the result across every target platform before relying on it for a campaign.

WhatsApp fetches OG images at the moment a link is shared and renders them inline inside the chat preview, so failures usually trace back to a small set of common issues. The image URL may return a non-200 HTTP status because of a 404, a redirect chain, or an authentication wall. The image may be served over HTTP rather than HTTPS, which WhatsApp blocks for security. The image server may explicitly block WhatsApp's user agent in robots.txt or a CDN rule. The image dimensions may be below the minimum threshold of roughly two hundred by two hundred pixels. Verify the image URL loads directly in a browser without any redirects, returns a 200 status over HTTPS, and meets the size requirements before troubleshooting further.

Facebook and WhatsApp cache Open Graph data for up to thirty days, which means a link shared shortly after your tag update may still display the previous version unless you force a refresh via the Facebook Sharing Debugger. LinkedIn typically refreshes within twenty-four hours automatically, and the Post Inspector forces an immediate refresh on demand. X and Slack usually reflect tag changes within a few hours of the source change going live. Plan all OG tag updates at least twenty-four to forty-eight hours in advance of any campaign launch so you have time to force refreshes and confirm the corrected previews are propagating across every target platform before the campaign actually begins distributing the link to your audience.

The og:image property is read by every Open Graph compatible platform including Facebook, LinkedIn, WhatsApp, Slack, and X when no Twitter-specific image is provided. The twitter:image property is read exclusively by X and overrides og:image for that platform. The two tags exist primarily because X uses a slightly different aspect ratio for its Summary Large Image cards, sixteen by nine compared with the OG standard of 1.91 to 1, which means a perfectly composed OG image may be cropped at the top or bottom on X. For high-traffic content that will be heavily promoted on both Facebook and X, set both tags with platform-appropriate dimensions. For most pages, og:image alone is sufficient because X falls back to it gracefully.

Every indexable page that could conceivably be shared should have a basic Open Graph tag set covering at minimum og:title, og:description, og:image, og:url, and og:type. The cost of adding tags template-wide is negligible because most CMS platforms and frameworks support dynamic OG tag injection through a single template change, while the cost of leaving tags off any page that later gets shared is permanently lost engagement. Higher-priority pages like homepage, key product pages, cornerstone content, and campaign landing pages deserve custom social copy and bespoke OG images, while lower-priority pages can rely on sensible template defaults. Either way, no page should be entirely missing OG tags.

Yes, increasingly. Email clients including Outlook, Apple Mail, and Gmail now render inline link previews using Open Graph metadata when URLs appear in message bodies, generating preview cards that look similar to social platform previews. Slack, Discord, and Microsoft Teams also generate inline link previews from OG data when URLs are pasted into messages, making OG metadata important well beyond traditional social platforms. The same tag set that powers Facebook and LinkedIn previews now powers email and team chat previews as well, which means good Open Graph implementation pays off across every channel where your content gets shared, not just public social media networks.