What Is a Featured Image?

In WordPress, the featured image is the file assigned to a post or page from the editor's side panel, through "Set featured image." That's where most glossaries stop. What usually gets left out: that one file doesn't have a single destination. The system reuses it in several different places, each with its own crop and target size.

The first job is the most cited one: it serves as the main image when an article shows up in the blog, in a category, or in a "related posts" block. The exact size used there is decided by the theme, usually one of WordPress's default sizes or a custom size registered with add_image_size().

The second job happens off the site entirely: most SEO plugins, RankMath or Yoast among them, pull the featured image as the default value for the og:image property whenever no manual social image has been uploaded. That means an image chosen for a 4:3 listing can end up representing the whole page in a WhatsApp or LinkedIn preview, at a completely different aspect ratio.

The third job depends on the theme: many templates, especially blog or magazine ones, place the featured image as a visual header inside the article itself, often full-width above or right below the title. Not every theme does this, and some let you turn it off on a page-by-page basis.

The fourth job is the one that's hardest to control directly: Google can use the featured image as a thumbnail in image results and in Google Discover, provided it meets the technical size requirements and the site allows large previews through the relevant meta robots tag.

None of these four jobs is optional or something you can switch off without it showing up somewhere else. Anyone who picks the featured image with only the blog listing in mind is leaving the social preview and Discover eligibility mostly to chance, since both inherit the same file without asking for confirmation first.

The practical problem shows up when someone uploads a single image meant for only one of these four jobs, usually the article header, and assumes it will work equally well for the rest. A vertical image, or one heavily cropped on the sides, can look fine as a header and, at the same time, show up oddly cut off in a WhatsApp preview or fall short of Discover's minimum requirements. That's not a bug in the system. It's the result of treating a file with four destinations as if it only had one.

The most common confusion is treating the featured image as if it were simply "the first image in the article." It isn't. It never has to appear in the body text at all, and it's still the image Google shows in a result or the one WhatsApp displays when the link gets shared.

No single size covers all four uses without a trade-off. A 1200 x 630 px image works reasonably well as og:image and clears the Discover threshold, but it can look too wide and too short as a header if the theme expects a more square format. That's why it's worth deciding which use case matters most for a given content type, rather than applying one rigid size template across the whole site.

In practice, that means editorial teams publishing at volume benefit from a fixed image template built around whichever use case matters most, instead of judging every featured image on its own. For a blog whose traffic leans on organic search and Discover, the fourth row of the table outweighs the third. For a site that gets shared heavily on social media, news or advice content among them, the first row carries more weight.

The featured image's Alt Text is still required, and it's independent of the article text: it describes the image for screen readers or for Google, not the article's headline. It's often left empty by mistake, precisely because the featured image gets uploaded from the side panel rather than the content editor, where filling in alt text tends to be more of a routine step.

The link to Open Graph is tighter than it first appears: in most WordPress installs running an SEO plugin, the og:image property automatically inherits the featured image whenever no manual social image has been uploaded. That automatic inheritance is convenient, but it also means a change made purely for the blog listing can end up altering how the link looks when shared on social media, without anyone touching that setting directly.

The same applies to the related Meta Tags: some plugins also generate schema.org Article markup with the featured image as the value of the image property, technically separate from og:image even though in practice both usually point to the same file. X, formerly Twitter, behaves the same way: without its own twitter:image tag, it falls back to og:image, so a change to the featured image can end up affecting that preview too, without anyone touching it directly.

• Upload the featured image at a generous starting resolution, at least 1200 px wide, so it works as both og:image and Discover thumbnail without losing quality.
• Check the theme to see what size the article header actually uses before assuming 1200 x 630 px is a universal measurement.
• Always fill in the featured image's alt text; it doesn't inherit from the article body, so it's easy to forget.
• Check the social preview after publishing, especially if the theme crops the featured image differently from how Open Graph displays it.
• If an article needs a different social image than the one shown in the listing, upload a manual og:image in the SEO plugin instead of forcing an awkward crop on the featured image.
• Avoid embedding text directly in the image itself: it gets cropped differently depending on the use case and can end up unreadable in one of the four contexts.

• Placing the most important element of an image too close to the edge, without accounting for og:image and Discover cropping to different ratios (1.91:1 versus 16:9).
• Uploading a low-resolution decorative image meant only for the theme header, which then shows up pixelated as the social preview.
• Leaving the featured image's alt text empty because it doesn't go through the same editorial review as images inserted in the article body.
• Assuming that changing the featured image automatically updates a preview that's already been shared; most platforms cache it.
• Reusing the same featured image across dozens of articles in a category, which reduces its usefulness in both listings and Discover.
• Switching themes without checking whether the new template crops the featured image differently or expects a different default size than the previous one.