Use one image-selection workflow, not two competing systems. In WordPress, a featured image (also called a post thumbnail) belongs to the post and is controlled by the theme and post type. An Open Graph image is metadata in the page HTML that social crawlers read. Configure your existing SEO plugin to publish an og:image, define a fallback for posts without images, and verify the rendered head. A featured image by itself does not guarantee that a social network will use it.
Featured image and og:image are different things
The featured-image control stores an image assignment for a post. Whether that control appears depends on post-type support and the active theme. WordPress also creates registered image sizes; themes can add custom sizes.
The og:image tag is separate metadata, normally emitted in the document head by an SEO or Open Graph plugin. A plugin may choose the featured image, a manually selected social image, an image in the content, an attachment, or a site-wide fallback. Social platforms then fetch the URL in that tag. Therefore, setting a featured image is necessary for some workflows but is not, on its own, a guarantee of the social preview.
Choose the automation approach
| Approach | Best fit | Important check |
|---|---|---|
| Configure the existing SEO plugin | Your site already emits Open Graph tags | Find its social-image and default-image controls before installing anything else. |
| Install a dedicated metadata plugin | You need explicit fallback rules or generated branded cards | Check current compatibility, post-type support and whether another plugin already emits tags. |
| Customize with code | You need post-type-specific selection, custom sizes or integration logic | Use the installed plugin’s documented filters and test every fallback case after updates. |
Start with the SEO plugin you already have
Yoast’s documented preference order starts with a user-defined social image, then the featured image, then a prominent image from the content, followed by configured defaults. Exact labels vary by plugin and version, so open the social or Open Graph settings and record the order it actually uses.
Recommended Free Tools
#1 Best Overall
Use a dedicated plugin for explicit fallbacks
WordPress.org listings describe different behaviors. One Open Graph plugin selects the featured image, then content images, then attachments, with site branding as a fallback. Simple Open Graphs describes generated branded cards for posts without an image and lists those cards as 1200 × 630 pixels. That dimension is a feature of that product, not a universal platform requirement. Verify compatibility and the current fallback order before activation.
Use code only when the rules justify it
Code is appropriate when, for example, products should use one image source while articles use another, or when a custom post type needs a dedicated size. Yoast publishes developer documentation for changing or adding Open Graph images through filters. Use the API supported by your installed version rather than copying an old hook from a different release.
A reliable setup workflow
- Confirm featured-image support. Edit a representative post and verify that the Featured image control exists. If it does not, check the post type registration and theme support. Also confirm that the image size your theme displays is available.
- Choose one metadata owner. If your SEO plugin already outputs Open Graph tags, configure it first. Do not add a second metadata plugin until you understand how the two outputs interact.
- Set a deliberate fallback. Pick a static brand image, a content-image fallback, or generated branded cards. Document the order so editors know what happens when a post has no assigned image.
- Configure post-level overrides. If the plugin offers a social-image field, decide whether editors may override the featured image. A manually selected social image commonly takes precedence.
- Publish and inspect the HTML. Open the rendered post, view its source, and search for
og:image. Confirm there is one intended URL and that it points to an accessible image. - Preview on the target network. Use that platform’s current preview or debugging utility. Caches can make an old image appear even after your HTML is correct, so test a newly published URL as well as an updated one.
- Test every branch. Check a post with a social override, one with only a featured image, one with images in the content but no featured image, and one with no images at all.
Designing fallback rules that editors can predict
Write the hierarchy in your editorial documentation. A practical policy is:
- Use a manually selected social image when a campaign needs a crop different from the article artwork.
- Otherwise use the featured image.
- If no featured image exists, use the first suitable content image only if your plugin documents that behavior.
- Use a consistent site default or generated branded card when no image exists.
Different plugins implement different orders. Never assume that installing a plugin will preserve the hierarchy you had before; inspect its settings and rendered output.
Custom post types, dimensions and accessibility
Test every custom post type separately. A post type can support featured images while its editor, template or SEO integration handles metadata differently. Keep the source image and the generated social image intentional: the image shown in a page template is not automatically the one emitted as og:image.
Do not present a single pixel size as a platform-wide rule. The 1200 × 630 value documented for Simple Open Graphs applies to its generated cards. Check current guidance for each network you target and preview the actual result. Keep important text away from edges, and provide meaningful alternative text wherever the image is exposed in the page or media library.
When code is the right tool
Use the selected SEO plugin’s documented Open Graph filters to add or replace image URLs. Keep the logic narrow: identify the post type, test whether a valid featured image exists, choose the intended size, and return one URL. Add tests for missing attachments and unpublished media. After a plugin update, inspect the head again because filter names and execution order are version-dependent.
Avoid writing a second independent wp_head implementation when an SEO plugin already emits tags. Two og:image values leave crawler behavior to the platform and make debugging harder. If you must replace the plugin output, disable or filter its original output first, then verify that only one set of Open Graph properties remains.
Rank #3
Troubleshooting wrong or missing previews
No Featured image control
The post type or theme may not support featured images. Enable support in the post-type/theme configuration, then reopen the editor and assign an image.
The page has no og:image
Check that an SEO or metadata plugin is active and that Open Graph output is enabled. Inspect the page source, not only the editor screen.
The wrong image wins
Look for a post-level social-image override and read the plugin’s documented hierarchy. It may intentionally outrank the featured image.
Two different images or duplicate tags appear
Search the source for every og:image. Jetpack and other plugins can emit Open Graph metadata in addition to your SEO plugin. Disable one producer or use its documented setting to turn off duplicate output.
Rank #4
The URL is correct but the preview is stale
Recheck the live HTML first, then use the target platform’s current preview/debugging tool. A cached preview can lag behind a corrected page; the available tool and cache behavior differ by platform.
The fallback never appears
Test the exact no-image case. Some plugins fall back to content images, some to attachments, and others to a configured default or generated card. Read the active plugin’s rules rather than inferring them from another product.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Preview pages without opening a browser
If you need repeatable checks of the rendered page, ScreenshotNeo is a website screenshot API and MCP server for developers. It can capture a clean image after accepting cookie or consent banners and removing more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. See ScreenshotNeo for the service.
Or skip the browser setup
Call the API after publishing a post and save the returned image for a visual check:
Free tools Windows power users keep installed
One-click scans. No signup required.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for options such as full-page capture, custom CSS, waiting for a selector or network idle, hiding selectors, device presets, PDF output, caching and bulk capture. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Best Value
Operational checklist
- One plugin or code path owns Open Graph output.
- Featured-image support is enabled for each relevant post type.
- The fallback hierarchy is written down and tested.
- Source contains one correct
og:imageURL. - Images are reachable to the intended crawler.
- Overrides, missing-image cases and custom post types have been previewed.
- Plugin compatibility and filter APIs are rechecked after updates.
Frequently Asked Questions
Does WordPress automatically turn a featured image into an Open Graph image?
No. A theme or plugin must emit an og:image tag, and its selection rules determine which image is used.
Should I install a second Open Graph plugin?
Usually check and configure the SEO plugin you already use first. A second producer can create duplicate tags unless its output is deliberately coordinated.
Is 1200 × 630 required everywhere?
No. That size is documented for Simple Open Graphs’ generated cards, not established here as a universal platform requirement.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
