How to Set an Open Graph Image for a WooCommerce Product in India

To choose the image that appears when a WooCommerce product link is shared, set the product’s main image in WooCommerce and, if that is not the image you want shared, set a product-specific Open Graph image in your SEO plugin. Save the product, then inspect the rendered page metadata. The documented WooCommerce and SEO-plugin steps are general; the sources reviewed do not establish an India-specific setting or different procedure.

1. Set the product image in WooCommerce

In WordPress admin, open Products and edit the product. In the product image area, select an image from the Media Library or upload one. This is the product’s main image. Use the separate Product gallery control to add additional images. WooCommerce documents these as distinct controls. WooCommerce: Adding Product Images and Galleries.

Open the product you want to update.
Choose or upload the intended main product image.
Add gallery images only if they are useful as additional product views.
Save or update the product.

Setting the main product image is a good first step, but do not assume it overrides every SEO plugin’s social-image selection. If the shared preview needs a different image, use the product-level social image control provided by your SEO plugin.

2. Set a product-specific Open Graph image in Yoast

Yoast documents social controls for individual content, including products: enable Open Graph metadata, edit the product, open Yoast’s Social tab, and choose the image. The same area can override the social title and description. Yoast: Customize your Facebook appearance with Open Graph meta tags.

Confirm Open Graph metadata is enabled in Yoast.
Edit the WooCommerce product.
Open the Yoast Social tab.
Set the social image you want associated with the product URL. Set a social title or description there too if needed.
Update the product.

Yoast’s documented image selection uses a hierarchy. A user-defined Facebook image has priority; other fallbacks can include a post’s featured image, a prominent image in page content, social defaults, and, when Yoast WooCommerce SEO is installed, the first product-gallery image. The gallery fallback is specific to that extension. If you need a particular image, a product-level override is less ambiguous than relying on a fallback. Yoast OpenGraph specification.

Yoast WooCommerce SEO also documents product-related metadata such as product type and availability; simple products can include price and currency metadata. Those tags are separate from selecting the social image. Yoast OpenGraph extensions and addons.

3. If you use another SEO plugin

Use the social or Open Graph controls provided by the plugin that actually outputs metadata on your product pages. Rank Math documents Open Graph controls and filters, including product-related behavior, but the sources reviewed here do not establish a current product-editor walkthrough comparable to Yoast’s. Check the plugin’s current documentation or the editor controls in your installation. Rank Math: OpenGraph.

Avoid enabling multiple plugins or theme features that each output Open Graph tags. If the HTML contains multiple og:image tags, sharing services may select an image you did not intend. Identify which plugin or theme owns the page metadata and resolve duplicates there.

4. Verify the product page metadata

After saving, inspect the product page itself, not just the WordPress editor. In the page source, look for Open Graph tags such as:

<meta property="og:image" content="https://store.example/wp-content/uploads/product-share.jpg">
<meta property="og:title" content="Product name">
<meta property="og:description" content="Product description">

Replace the example URL and values with your actual page output. Check that og:image points to the intended, publicly accessible image. If you inspect source through a browser, use “View page source” and search for og:image; the browser’s rendered Elements panel can also help when metadata is altered by scripts.

Then check the exact product URL in the social service where the issue occurs. A service may show a previously fetched preview after an update. The sources reviewed do not establish a universal cache duration or refresh procedure, so do not assume the preview changes immediately. First confirm the current page source is correct, then use the platform’s available preview/debugging tool if it provides one.

5. Keep catalog-sync settings separate

Meta for WooCommerce documents an image choice for Facebook catalog synchronization: use the WooCommerce image or a custom image URL. That setting concerns catalog data synchronization. It does not, by itself, prove that the product page’s HTML og:image tag changed. If the problem is a shared web link preview, verify the page metadata separately. WooCommerce: Meta for WooCommerce documentation.

6. Image choice and India-specific questions

The setup described above applies to WooCommerce and plugin controls generally. The official documentation reviewed does not identify a different Open Graph procedure for stores based in India. It also does not establish one image dimension that works universally across all sharing platforms. Choose an image that represents the product clearly, check the resulting preview on the target service, and follow that service’s current image guidance if it specifies requirements.

7. Troubleshooting

Symptom	Likely cause	What to check or do
The store logo appears instead of the product	No product-level social override, or the SEO plugin is using a site-wide social default.	Set the image in the product’s Social/Open Graph controls, update the product, and confirm the product page’s `og:image` value.
A gallery image appears instead of the chosen image	The plugin is using a fallback, such as the first gallery image where the relevant extension supports that behavior.	Set an explicit product-level social image and check the generated tag. Do not rely on fallback ordering when the exact image matters.
The image is cropped or looks wrong in a preview	The target service may render the image differently from the product page, or the selected image may not suit its preview presentation.	Try a clearer product image and inspect the preview on the target service. The sources reviewed do not support a universal dimension recommendation.
The preview still shows the old image	The service may be displaying a previously fetched preview.	Verify the live page source first. Then use any preview refresh/debugging option the service provides; no universal cache duration is established here.
There are multiple `og:image` tags	A theme and one or more plugins may all be emitting Open Graph metadata.	Check the rendered source, identify the active metadata output, and disable or configure duplicate output so the page has an unambiguous intended image.
The page has no `og:image`	Open Graph output may be disabled, or the active plugin may not have a usable image or fallback.	Enable Open Graph metadata in the SEO plugin, set a product image and social override, update, and inspect the page source again.
The Facebook catalog image changed, but link sharing did not	The catalog-sync image setting and page-level Open Graph metadata are separate controls.	Set or correct the product page’s Open Graph image in the SEO plugin and verify the HTML tag independently.

8. A reliable update checklist

The WooCommerce main product image is set.
The SEO plugin that outputs metadata has Open Graph enabled.
The product has an explicit social image if the default is not suitable.
The saved product page has the expected og:image value.
There is no conflicting duplicate metadata output.
The target sharing service is checked using the exact product URL.
A catalog-sync image setting is not being mistaken for the page’s Open Graph setting.

Or skip the browser setup

To capture a screenshot of the product page for review or sharing, ScreenshotNeo provides a one-request screenshot API. This does not configure the product’s Open Graph metadata; it captures the page so you can inspect its current appearance. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://store.example/product/example/ -o product.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://store.example/product/example/",
    },
    timeout=90,
)
open("product.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://store.example/product/example/'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('product.webp', Buffer.from(await res.arrayBuffer()));

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.

Performance, reliability, and cost notes

For this WooCommerce change, the work is a product image selection, an SEO-plugin setting, and verification of the generated page metadata. The reviewed sources provide no timing or performance benchmarks, so allow time to inspect the live product URL and the service preview after publishing. Avoid repeatedly changing settings based only on a stale preview; use the page source to determine whether the site output is already correct.

ScreenshotNeo offers caching with a chosen TTL, async jobs with signed webhooks, and bulk capture for up to 100 URLs per call. Only clean shots are billed: bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; responses identify page verdict and billing status in headers. Plans are Free (1,000 shots/month), Starter ($5 for 3,000), Growth ($15 for 15,000), Pro ($39 for 60,000), Scale ($99 for 250,000), and Business ($249 for 1,000,000); yearly billing gives two months free. Every feature is on every plan. These are screenshot-service details, not requirements for setting Open Graph metadata.

Frequently asked questions

Does adding a WooCommerce product image always set the shared image?

No. The main product image and the social image are distinct choices in a workflow. The SEO plugin’s output and fallback behavior determine the page’s Open Graph metadata.

Does this setup change for a store in India?

The official setup documentation reviewed does not establish an India-specific difference.

Will changing the image update every old preview immediately?

That is not established by the reviewed sources. Confirm the current page metadata and check the target service’s available preview refresh options.

Does the Facebook catalog image control set the page’s `og:image`?

The catalog-sync documentation does not establish that. Verify and configure the product page metadata separately.