Updated 3 min read3 tools
Open Graph & Twitter Meta Tags: A Practical Guide
Write title, description, and image tags that look right when links are shared on social apps, Slack, and iMessage — with preview and UTM pairing tips.
- open graph tags
- twitter card meta tags
- meta tag generator
- og:image
Open Graph and Twitter Card meta tags control how your link looks when shared — title, description, and image — which often matters more for click-through than on-page SEO alone because chat and social previews are the first impression.
Image and URL requirements
og:image must be an absolute HTTPS URL reachable without authentication. Login-walled or redirect-chained images break previews silently in some apps.
Keep important text away from image edges — circular crops on some clients clip corners. File size under a few megabytes loads faster in Slack and mobile share sheets.
- Use HTTPS absolute URLs for og:image and og:url.
- Host images on your CDN or static bucket, not a dev localhost.
- Test after deploy — staging URLs do not help production shares.
- Compress marketing images before using them as og:image assets.
Generate and preview on BrowserTools.tech
Draft tags in Meta Tag Preview, copy the snippet into your layout or CMS head partial, deploy, then share the production URL in a private Slack channel to confirm the unfurl.
Pair campaign links with UTM Builder so attributed traffic still unfurls correctly — UTMs change the query string, not your OG tags, when configured on the same canonical page.
Slugs and permanence
Stable URLs make OG investments durable. Generate clean permalinks with Slug Generator before launch — lowercase, hyphenated, keyword-forward — and avoid changing slugs after publishing without redirects.
When you must migrate URLs, update og:url and set HTTP redirects so old shares eventually land on the new canonical page with updated tags.
Common debugging mistakes
Platforms cache previews aggressively. After fixing tags, use each platform’s debug or refresh tool if available, or append a benign query param during testing only.
Duplicate conflicting tags — one from CMS, one from plugin — produce unpredictable picks. View rendered HTML source, not just your template file, to see what actually ships.
3 min · 3 tools
All guides