Google Preferred Image SEO: og:image vs Schema.org After the 2026 Update

01

Checklist

Google now explicitly documents two metadata routes for preferred image selection: schema.org image properties and og:image. Neither guarantees the thumbnail, but both give Google a stronger preferred-image signal than hoping the crawler guesses correctly.

Google clarified in March 2026 that it uses both schema.org image markup and the og:image meta tag as sources when determining preferred image previews in Google Search and Discover.

Google documents several ways to express the preference:

<meta property="og:image" content="https://example.com/image.jpg">

or schema.org properties such as:

primaryImageOfPage
image
ImageObject

This does not guarantee Google will use the image.

Google’s image selection remains automated.

The metadata tells Google which image you prefer.

Use these checks as the working list:

• Why this became a fresh SEO topic
• og:image: the simple option
• Schema.org option
• Should you use both?
• Discover image requirements
• Do not make the lead image a logo
• Avoid text-heavy lead art
• Cropping matters
• Image URL stability
• Image crawlability
• Image alt text is separate
• Build a template audit
• Search and Discover testing

Sources reviewed.

1. Image SEO best practices — Google Search Central; accessed 2026-08-06. ^[1]
2. Get on Discover — Google Search Central; accessed 2026-08-06. ^[2]
3. Latest Google Search documentation updates — Google Search Central; accessed 2026-08-06. ^[3]

Why this became a fresh SEO topic.

Before the March update, publishers often treated og:image as primarily social metadata.

Google’s documentation now explicitly names it as one source used when choosing Search and Discover thumbnails.

That makes a long-standing implementation detail much easier to standardize.

If your site publishes:

• news;
• reviews;
• ecommerce articles;
• guides;
• Discover-oriented content;

preferred-image metadata belongs in the template contract.

og:image: the simple option.

Example:

<meta property="og:image"
      content="https://example.com/media/google-ai-mode-guide.jpg">

Advantages:

• simple;
• widely supported by CMSs;
• already useful for social sharing;
• easy to inspect.

The image should be:

• relevant;
• representative;
• high resolution;
• not a generic logo;
• not text-heavy.

Google specifically advises against generic images such as site logos for preferred-image metadata.

Schema.org option.

Google documents primaryImageOfPage on a WebPage.

Example:

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "url": "https://example.com/guide",
  "primaryImageOfPage": {
    "@type": "ImageObject",
    "url": "https://example.com/media/guide.jpg"
  }
}

Article markup can also use the image property attached to the main entity.

This is useful when your page already has structured data.

Should you use both?

You can.

A practical template can emit:

og:image
Article.image
WebPage.primaryImageOfPage

pointing to the same intended lead asset where that matches the page.

The important rule is consistency.

Do not tell Google:

og:image → photo A
Article.image → diagram B
primaryImageOfPage → logo C

unless you have a deliberate reason.

Conflicting preferences create ambiguity.

Discover image requirements.

Google’s current Discover guidance recommends images that are:

• at least 1,200 pixels wide;
• more than 300,000 total pixels;
• approximately 16:9;
• high resolution;
• enabled for large previews using max-image-preview:large or AMP.

A 1600 × 900 image works well for this use case.

That is why RankBuilder’s media packages should standardize around a 16:9 original lead image unless a story needs another format.

Do not make the lead image a logo.

Google specifically advises against generic images such as the site logo.

A useful lead visual should represent the article.

For:

Google canonical re-evaluation

use:

• URL cluster diagram;
• timeline;
• canonical decision tree.

Do not use:

• RankBuilder logo;
• generic magnifying glass;
• stock laptop with “SEO” typed onto the screen.

The visual should carry information.

Avoid text-heavy lead art.

Google also advises avoiding images with lots of text.

Text baked into an image:

• can become unreadable on mobile;
• crops badly;
• duplicates the headline;
• provides weak visual context.

A chart can have labels.

A diagram can have short callouts.

But do not turn the entire article title into a JPEG billboard.

Cropping matters.

Google may crop images for Discover.

Check the lead image at:

• 16:9;
• square crop;
• mobile thumbnail;
• small card.

Keep the important subject near the center unless the composition requires otherwise.

Avoid placing the only meaningful object at the far edge.

Image URL stability.

Use stable image URLs.

Bad:

/image-final-2-new-august-copy.jpg

Better:

/google-preferred-image-seo.jpg

If the content changes materially, update the asset deliberately.

Do not generate random URLs on every build unless your asset pipeline handles indexing and caching well.

Image crawlability.

Google must be able to access the image.

Check:

• 200 response;
• correct MIME type;
• robots.txt;
• CDN;
• hotlink protection;
• signed URL expiry;
• authentication;
• regional restrictions.

An og:image URL returning 403 is not a useful preference.

Image alt text is separate.

alt describes the image for users and accessibility.

og:image identifies a preferred preview asset.

Structured data describes the image relationship.

Do not stuff the primary keyword into all three fields identically.

Write useful alt text.

Example:

Diagram showing a Google canonical cluster being re-evaluated after two pages are made substantially different.

That explains the image.

Build a template audit.

For each article type, verify:

og:image
Article.image
primaryImageOfPage
max-image-preview:large
image width
image height
HTTP status
content type
visible lead image
alt

Sample after deployment.

Search and Discover testing.

You cannot force a thumbnail.

You can verify the inputs.

Use:

• page source;
• rendered DOM;
• Rich Results Test where relevant;
• URL Inspection;
• Google Images;
• Discover performance later if the site qualifies.

Do not declare implementation failure because Google selected another image once.

The selection system uses several sources.

02

Completion criteria

FAQ.

Does Google use og:image?

Yes. Google’s 2026 image guidance explicitly lists og:image as one source for preferred image selection.

Is schema.org better than og:image?

Google documents both. There is no published universal ranking saying one always wins.

What size should a Discover image be?

Google recommends at least 1,200 pixels wide, more than 300,000 total pixels, and roughly 16:9.

Does preferred image metadata guarantee the thumbnail?

No.

Can I use my logo?

Google advises against generic images such as logos as the preferred preview image.

Deployment checklist.

• Original lead image created.
• 1,200+ px width.
• More than 300,000 pixels.
• 16:9 version available.
• og:image set.
• Structured data image aligned.
• max-image-preview:large allowed.
• URL returns 200.
• CDN allows Googlebot.
• Alt text useful.
• No giant text overlay.
• Mobile crop checked.
• Image URL stable.

Verdict.

Google’s 2026 clarification removes an excuse for sloppy image metadata.

Pick the lead image deliberately, tell Google consistently which asset represents the page, and make the visual worth showing.

A search thumbnail is not decoration. It is part of the result.

Verification record.

• March 2, 2026 documentation change was checked on 2026-08-06.
• Current Discover dimensions and preferred-image recommendations were checked.
• No guarantee about which metadata source wins is claimed.

Duplication and search-intent record.

No prior package targets the exact 2026 preferred-image metadata clarification as the main query.

References

Sources behind this record

1. Image SEO best practices — Google Search Central (accessed August 6, 2026)
2. Get on Discover — Google Search Central (accessed August 6, 2026)
3. Latest Google Search documentation updates — Google Search Central (accessed August 6, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.