Page with no share tags
- Platform guesses a title from page text
- Random, badly cropped image or none at all
- Card looks accidental and gets scrolled past
Page with Open Graph tags
- Share title written to be read in a feed
- 1200×630 image with one short headline
- Canonical og:url so every share counts once
- Checked in a post inspector before posting
Every time someone pastes your link into LinkedIn, Slack, WhatsApp or X, the platform builds a preview from your page’s meta tags. With no tags, you get a bare URL or a random image cropped badly. With good tags, you get a clear card with a headline and image: free distribution that looks deliberate.
Why it works
Feeds are crowded and people decide in a moment whether to tap. A card with a clear headline and a readable image gives them something to decide on, while a bare URL gives them nothing. The card also travels with every reshare, so your message stays intact as the link moves between people you will never reach directly.
The platform builds the card from your tags. You set them once per page and every future share benefits.
How to do it
- Write a share title (
og:title) that makes sense out of context. It can differ from your SEO title; it is read in a feed, not a results page. - Write a one-sentence description (
og:description) that says what the reader gets. - Make a 1200×630 px share image (
og:image) with a short headline in large type. Many people will only see the card at thumbnail size. - Add
og:urlwith the canonical address so shares of variant URLs count as the same page. - Add
twitter:card=summary_large_imageso X shows the big-image layout. - Test before you post. Paste the link into a private chat or a platform’s post inspector and check the card renders as expected.
Example
A founder publishes a pricing-change announcement. Without tags, LinkedIn shows the site logo and the first sentence of the cookie banner. After adding a share title (“We just made our free plan bigger”), a one-line description and a simple branded image, every repost of the link carries that message, including reposts the founder never sees.
Metrics to track
- Sessions from social referrals to tagged pages, compared with the weeks before the change.
- Click-through rate on your own posts that carry the link, where the platform reports it.
- Share of key pages with valid tags, checked with a crawler or the platforms’ debuggers.
- Bounce rate from social referrals. It should not rise. If it does, the card may promise something the page does not deliver.
When it backfires
- Cached old previews. Platforms cache cards; after changing tags, refresh the cache with the platform’s debugger or the old card keeps showing.
- Text-heavy images. Paragraphs on a share image are unreadable at feed size. One short line, large.
- Clickbait cards. A share title that over-promises gets clicks and immediate bounces. Match the card to the page.
Growth Marketing Academy
Learn the framework behind this tactic
These lessons explain the math and the mental model, so you can adapt the tactic instead of copying it.
- Track 2 · Acquisition Growth Loops: Build Acquisition That Compounds Funnels describe how users leak. Loops describe how users create more users. Learn to map, quantify and choose the loop that fits your product.
- Track 2 · Acquisition Content and SEO Loops: Pages That Keep Bringing Users Build content, UGC and programmatic SEO loops, organise them into topic clusters, and measure throughput from page published to customer won.
Questions people ask
Why does my link show the wrong image when shared?
Usually the page has no og:image tag, so the platform guesses, or the platform cached an older version. Add the tag, then use the platform's post inspector or debugger to refresh the cache.
Do I need separate Twitter Card tags?
X falls back to Open Graph tags for most fields, but adding twitter:card set to summary_large_image makes sure links show the large image layout.
Does every page need its own share image?
Your most shared pages, such as the homepage, pricing, launch posts and popular articles, should have one. For the rest, a default branded image set in the page template is a reasonable fallback.