GUIDE

Split-Testing Your Social Preview Image: How Much Do Clicks Actually Change?

The OG image is the first visual signal someone sees before they click a shared link — often the only one. Here's what's actually worth A/B testing, and why raw click counts alone will mislead you.

August 9, 20264 min read

When someone scrolls past a shared link in Slack, X, LinkedIn, or iMessage, the preview image is usually the first thing their eyes land on, and in most feed layouts it's larger and more visually dominant than the headline text next to it. That makes it one of the highest-leverage things you can test on a link, arguably more consequential than the copy in the post itself. People decide whether to click in a fraction of a second, and they're deciding off the image before they've finished reading the title.

Why the image matters more than it seems

Headline copy gets iterated on constantly — most teams have run some version of an A/B test on subject lines or post copy. The image attached to a shared link gets far less attention, usually because generating variants used to mean exporting a few PNGs by hand and manually swapping them between campaigns. But the image is doing real work: it signals genre (is this a data-heavy report or a casual blog post?), it carries brand recognition, and it's the only element that reads instantly without any text processing at all. Two links with identical titles and descriptions can produce meaningfully different click-through rates purely because of what's in the frame.

What's actually worth testing

  • Photo vs. branded/illustrated card — a real photo can read as more authentic or human; a designed card with your logo and a clear headline can read as more professional and on-brand. Which wins depends entirely on your audience and channel.
  • Text-on-image vs. clean image — overlaying a headline directly on the image adds context at a glance but can look cluttered or generic; a clean image relies on the separate title field to carry the message.
  • High-contrast vs. subtle — a bold color block or high-contrast crop tends to stop the scroll faster in a busy feed; a muted, editorial-style image can perform better in contexts where subtlety reads as credibility.
  • Face/person vs. no face — images with a visible face often draw the eye first, but they're not universally better — it depends on whether a face is relevant to what you're sharing.

Why raw click counts lie to you

The most common mistake in this kind of testing is checking results after a day, seeing variant A ahead of variant B by a handful of clicks, and calling it done. At the traffic volumes most links actually see, that gap is well within the range you'd expect from pure chance — flip a coin forty times and you won't get an even 20/20 split either. A difference only means something once you've accumulated enough volume per variant that the gap is unlikely to have happened by chance alone. That's what a confidence measure gives you: a way to ask "how likely is it that this split happened randomly, if the two images were actually performing the same?" rather than just eyeballing which number is bigger.

Volume isn't the only variable, either. Traffic composition shifts by day of week and by the channel driving it — a link shared into a newsletter on Tuesday morning and one shared into a Slack community on Friday afternoon will pull different audiences with different click behavior. If your test window only covers one slice of that cycle, you're measuring the audience's schedule as much as the image itself.

How this works in practice

This is the exact gap useopengraph's sharing links are built to close: you can attach two or three OG image variants to a single trackable link, split incoming clicks across them automatically, and see a confidence read against an even split rather than just raw counts — so you know whether a lead is real or noise before you commit to a winner.

A checklist for running a fair test

  1. Hold the headline, description, and destination page constant — change only the image, or you won't know what caused the difference.
  2. Don't call a winner on day one. Let the test run through at least one full week so weekday and weekend traffic both get represented.
  3. Set a minimum sample size per variant before you start, and don't peek-and-stop the moment one image pulls ahead early — early leads regularly flip.
  4. Check for a confidence read against an even split, not just which variant has more raw clicks.
  5. Re-test winners occasionally — what works for one piece of content or one season doesn't automatically generalize to the next.

Stop paying per seat
for a usage-shaped problem.

Unlimited teammates, one usage pool. Start free with the scanner — no card required.