Quick answer
The og:image tag tells social platforms which image to use when your page is shared. It does not control Google Discover, but it should still point to a strong, large, clean asset so your social preview and article presentation stay aligned.
Why this matters
Traffic systems rarely live in one channel. A post may earn clicks from Discover, direct sharing, messaging apps, and social previews in the same week. When the social metadata points to a weak or stale image, brand consistency and click confidence both suffer.
That is why the featured image guide and the Discover pillar guide should influence your og:image implementation too.
How to implement og:image safely
The goal is not just to set the tag, but to keep it accurate per article and resilient during template changes. Modern frameworks make this easier because you can generate per-page metadata from the same content registry that powers the blog itself.
- Store a clear featured image reference in your post data model.
- Set the Open Graph image in page metadata so every slug gets the right preview asset.
- Use canonical absolute URLs and predictable image dimensions for share reliability.
- Regenerate or replace stale social images when article framing changes materially.
Common mistakes
Open Graph issues are often invisible until someone shares the article. That delay makes small metadata bugs surprisingly expensive.
- Leaving a site-wide default image on every post instead of the actual featured asset.
- Serving an og:image that is technically valid but visually weak or outdated.
- Using a relative or broken image URL that some share scrapers cannot resolve reliably.
- Treating social preview metadata as separate from the editorial image strategy.
Practical implementation note
DiscoverImg can simplify this because the same optimized image that passes size and preview checks for the article can also feed your Open Graph metadata. That lowers the chance of channel mismatch later.
After your metadata is wired, revisit the featured image guide and then publish with the final asset from DiscoverImg Optimizer.
Frequently asked questions
Does og:image affect Google Discover directly?
No. Discover relies on other signals, but a strong og:image still improves the broader sharing experience around the same article.
Should my og:image match my featured image?
Usually yes. Using the same strong editorial asset keeps branding and messaging more consistent across channels.
Do I need absolute URLs for og:image?
Absolute URLs are the safer default because they are easier for social scrapers and preview tools to resolve consistently.
What image size is best for og:image?
A large, clear image with stable aspect ratio is ideal. Many teams reuse a 16:9 or nearby large asset for both article headers and Open Graph metadata.
How do I test og:image after publishing?
Use live page inspection and share debuggers where available, then verify the correct image appears when the URL is shared.
