Can you really control which image appears in Google's text search results?

Why does Google say you can't control the displayed image?

Google automatically selects the image it deems most relevant to accompany a text search result. This selection is based on opaque criteria: search query context, image quality, semantic relevance, and position on the page.

The search engine doesn't just pick the most visible image or the first one in the DOM. It analyzes the content and decides what will best serve the search intent. As a result — you can technically mark an image as priority, but Google retains final control over the choice.

What is the primaryImageOfPage metadata parameter?

Google introduces the ability to signal a priority image via the primaryImageOfPage (schema.org) or og:image (Open Graph) tags. These metadata elements indicate to the search engine which image you consider as the main one.

Heads up — this is not a directive, it's a suggestion. Google can ignore it if another image seems more relevant for a given query. It's one signal among many, not an absolute control lever.

What are the best practices for Google Images?

Google points to its general recommendations for optimizing images: quality files, descriptive filenames, relevant alt attributes, textual context around the image, and ImageObject structured data.

• Use high-quality images with appropriate dimensions
• Provide alt attributes in a descriptive and precise manner
• Place images in coherent textual context
• Implement primaryImageOfPage or og:image to signal the main image
• Avoid decorative or off-topic images in strategic areas

Is this statement consistent with real-world observations?

Yes and no. On paper, Google has always been vague about controlling images in text SERPs. The novelty here is that they're finally formalizing a preference signal via primaryImageOfPage.

In practice, we've observed for years that Google sometimes picks unexpected images — logos, ad banner images, off-context visuals. The new parameter should reduce these aberrant cases, but [To be verified] to what extent it will actually be taken into account. Field tests are still lacking.

What's the real scope of primaryImageOfPage?

Google qualifies this parameter as a "suggestion," not a directive. Concretely, this means it can be ignored if the algorithm deems another image more relevant for a given query.

Let's be honest — it's consistent with Google's philosophy: provide hints, not commands. The risk? That this parameter becomes a placebo for SEOs, like so many other "signals" whose real impact remains difficult to measure. [To be verified] through A/B tests on high-traffic pages.

Should you systematically implement primaryImageOfPage?

Yes, especially if you have pages with multiple images and want to guide Google toward the one that best represents your content. It's a weak signal, but it costs nothing to implement.

What should you actually do on your pages?

First step: identify strategic pages (those generating organic traffic) and audit which images Google currently displays in text search results. You can use Google Search Console or simply search for your key pages.

Next, implement primaryImageOfPage via schema.org or og:image if not already done. Prioritize a quality image that's relevant, with an appropriate ratio (16:9 or 4:3 depending on context).

What mistakes should you absolutely avoid?

Don't designate a decorative image, generic logo, or promotional banner as your priority image. Google may ignore it, and you risk degrading user experience if the displayed image doesn't match the content.

Also avoid multiplying og:image or primaryImageOfPage tags on the same page. One clear, representative main image. Everything else falls under standard Google Images best practices.

• Audit images currently displayed in text SERPs for your key pages
• Implement primaryImageOfPage (schema.org) or og:image on strategic pages
• Verify that the designated image is high quality and representative of your content
• Provide alt attributes descriptively on all images
• Optimize the textual context around images (headings, captions, adjacent paragraphs)
• Monitor progress in Google Search Console after implementation