Best WordPress Plugins for Setting Open Graph Images per Page
Compare WordPress options for choosing a unique Open Graph image on each page, understand their fallbacks, and troubleshoot the tags social platforms read.
If you need editors to choose a different Open Graph image for each WordPress page, SEOPress has the clearest documented per-page workflow in the sources reviewed: it supports manually editing social metadata for individual posts and pages and provides Facebook and X previews in its SEO metabox. Yoast SEO is also a strong fit, with a user-defined social image and a documented fallback order. If you want to generate branded images from page content, consider ogdynamic; if automatic image selection or developer-level customization is enough, the WordPress.org Open Graph plugin or Rank Math’s developer hooks may fit better.
This is a documentation-based comparison, not hands-on plugin testing. Plugin interfaces, features, plans, and platform behavior can change; check current documentation and generated page metadata before relying on a specific workflow.
1. What to look for in a per-page Open Graph plugin
Open Graph metadata tells sharing platforms which title, description, and image to use when a page is shared. The practical requirement is usually two parts: a way to override the image on an individual page, and sensible defaults for pages where no override is set.
- Per-page selection: Can an editor choose a unique image on a post or page?
- Fallback precedence: What image is used if the custom field is empty: featured image, content image, post-type default, or site default?
- Preview and validation: Can the editor see the card and catch image size, dimension, or format concerns?
- Image workflow: Does the plugin use an uploaded image, select one automatically, or render a design from a template and page data?
- Output ownership: Is another SEO or social plugin also emitting Open Graph tags?
- Customization: Does the site need developer filters rather than an editor-facing field?
Keep one plugin or service responsible for the page’s Open Graph output. Duplicate tags can cause platforms to show the wrong metadata. Yoast explicitly warns about this when another plugin emits Open Graph data too.
2. Plugin comparison
| Option | Best fit | Per-page image evidence | Watch for |
|---|---|---|---|
| SEOPress | Editors who want a manual image field and a social preview | Documents manual social image editing for each post or page, plus Facebook and X previews in its SEO metabox | Verify which defaults apply on your site and inspect the generated tags |
| Yoast SEO | Sites already using Yoast or wanting a clear image fallback hierarchy | Documents a user-defined Facebook image in the Social tab of the post or page metabox | Prevent another plugin from outputting duplicate Open Graph data |
| ogdynamic | Sites that want branded social images rendered from templates and WordPress data | Its WordPress.org listing describes template fields mapped to content such as the post title or featured image | Image generation is hosted on its servers and requires an account; compatibility claims are listing claims |
| Open Graph (WordPress.org plugin) | Automatic image selection or developers comfortable with filters | Listing describes automatic selection from featured, content, and attached images | It says there is no admin settings page; customization uses filters |
| Rank Math developer filters | Developers who need to customize image output in code | Cited developer documentation covers filters for image output and image sizes | The cited source does not establish current editor steps, plan restrictions, or ordinary per-page UI |
3. SEOPress: the clearest documented manual workflow
SEOPress documents editing the social title, description, and image for each post, page, post type, or taxonomy term. Its SEO metabox includes Facebook and X previews, and its documentation says it checks image size, dimensions, and format and alerts users to concerns. It also documents default images globally or per post type.
This makes it the most directly documented choice in this comparison when editors need an individual image field and a preview. A default image is useful for pages without a custom selection, but do not assume it overrides an explicitly selected page image. Check the rendered tags for the site’s configuration.
Sources: SEOPress social media features and SEOPress feature overview.
4. Yoast SEO: page image plus documented fallbacks
Yoast’s technical specification gives this image-selection order:
- A user-defined “Facebook image” in the Social tab of the Yoast metabox.
- A featured image for a page where applicable; the specification notes the featured-image fallback applies only for posts in this step.
- A prominent image from the content.
- A template-level social default.
- The site’s fallback or default social image.
This hierarchy helps explain why a page may show an image other than the one an editor expected. Check the page-specific field first, then follow the fallback chain. Yoast says Open Graph data is enabled by default and warns that another plugin emitting Open Graph metadata can result in social networks showing the wrong title, description, or image.
Sources: Yoast Open Graph technical specification and Yoast guidance on incorrect social metadata.
5. When generated images or automatic selection make more sense
ogdynamic for template-generated cards
The ogdynamic WordPress.org listing describes templates with fields such as title, subtitle, and image, which can be mapped to WordPress data such as a post title or featured image. It says generated images are 1200×630 pixels and that generation is hosted on its servers and requires an account. The listing says it can work alongside named SEO plugins and avoids outputting a duplicate og:image when it generates an image. Treat these as listing claims, not independent compatibility testing. The 1200×630 figure is the listing’s stated generated-image size, not a universal current requirement for every platform.
Source: ogdynamic WordPress.org listing.
Open Graph plugin for automatic image selection
The WordPress.org Open Graph plugin listing describes choosing a featured image first, then images in content and attached images, with the site icon, custom logo, or header image as fallbacks. The listing says it has no admin configuration page and that developers can customize behavior with filters. That can suit an automatic setup, but is less direct for editors who need a custom image field on every page.
Source: Open Graph WordPress.org listing.
Rank Math for code-level customization
The cited Rank Math documentation describes developer filters for changing image output, preventing a default or content-derived image, and choosing image sizes. It supports a developer-customization option, but does not establish the current editor-facing per-page workflow, plan restrictions, or interface steps. Confirm those in current product documentation or the plugin before choosing it for nontechnical editors.
Source: Rank Math developer filters documentation.
6. A reliable setup process
- Choose the metadata owner. Decide which SEO or Open Graph plugin will emit the tags. Disable overlapping output from other plugins where needed.
- Set a site or post-type fallback. Choose a usable default for pages without a specific image. Treat defaults as fallbacks until the live output confirms their precedence.
- Set a page-specific image. Use the plugin’s social field on the target post or page when that page needs a distinct card.
- Use the preview if available. Review cropping and the visible card in the editor. A preview helps, but the generated metadata on the live page is the source to inspect when diagnosing output.
- Check the page source or fetched HTML. Confirm there is an
og:imagetag with the intended absolute image URL, and check whether multiple plugins emitted competing tags. - Recheck the platform preview. Social services may cache fetched page previews. If the HTML is correct but an old card remains, use that platform’s current preview refresh or debugger process; platform-specific refresh instructions are outside the sources reviewed here.
7. Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The shared card uses the featured image instead of the chosen image | The page-specific field was not saved, the wrong metadata owner is active, or a fallback rule is taking effect | Reopen the page’s social settings, save the selection, then inspect the live og:image and follow the plugin’s documented precedence. |
| A different plugin’s image or title appears | Multiple plugins may emit Open Graph tags | Choose one output owner and disable duplicate Open Graph output. Yoast specifically warns that duplicate metadata can produce incorrect previews. |
| The editor preview looks right but the shared card is stale | The platform may have cached an earlier fetch | Confirm the live HTML first. Then refresh the platform’s cached preview using its current tool or workflow. |
| The image is missing or unsuitable | The image URL may be unavailable to the crawler, or dimensions, format, or file conditions may be unsuitable | Check that the selected image resolves publicly and review plugin warnings. SEOPress documents checks for image size, dimensions, and format. |
| A default appears where a page image was expected | The custom image may be empty or a site/post-type default may be active | Verify the page-level field is populated and inspect the actual tag. Do not infer precedence from the settings label alone. |
| Editors cannot find an image setting | The chosen plugin may rely on automatic selection or developer filters rather than an editor field | Use a plugin with a documented page-level workflow, or implement and maintain a custom integration. |
8. Performance, reliability, and cost considerations
This comparison has no independent performance benchmarks, so it cannot support claims that one plugin makes a site faster or more reliable than another. For routine editorial use, evaluate the operational shape of the workflow: whether images are selected locally or generated by a hosted service, who can edit the field, whether a preview catches mistakes, and how the site behaves if an image is unavailable.
For ogdynamic, the listing describes hosted generation and an account requirement; verify current plan and pricing details directly before adopting it. The research reviewed here does not establish current prices or plan boundaries for these options. For plugins that select existing WordPress images, account for the work of preparing, storing, and maintaining suitable images. In all cases, test an actual page with its intended image, fallback, and social metadata owner.
9. ScreenshotNeo for capturing a page preview
ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. It is an alternative to try first when you want to capture a page to inspect its visual appearance, rather than choose or emit its Open Graph metadata. Its API can return PNG, JPEG, WebP, or PDF; capture alone does not configure WordPress metadata.
For example, capture a public page after publishing a social image change:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/your-page -o shot.webpSee the ScreenshotNeo API documentation for options and output formats. Its cookie and consent handling accepts banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up free for 1,000 screenshots a month with no card.
10. FAQ
Does an Open Graph image change the page’s featured image?
Not necessarily. Social metadata is a separate selection; a plugin can use a custom social image while the page keeps its existing featured image.
Is 1200×630 required for every Open Graph image?
The cited ogdynamic listing says its generated images are 1200×630. The research does not establish that as a universal requirement for all platforms.
Can I use both Yoast and SEOPress?
Using multiple plugins may be possible for other functions, but avoid having both emit competing Open Graph tags. Choose one source for that metadata and inspect the page output.
Which option is best for an editor who does not write code?
SEOPress is the clearest documented match in this comparison for individual image editing plus a preview. Yoast also documents a per-page social image field and fallback behavior.
Sources and scope
Feature descriptions above are based on vendor documentation and WordPress.org listings available at the research check on October 3, 2026. The comparison does not claim hands-on testing, independent performance measurements, or verified current prices. Check the linked documentation and current plugin interface before publishing version-specific instructions.
