To show the intended product image when someone shares a store link in WhatsApp, put product-specific Open Graph tags in that product page’s HTML <head>. Use an absolute, publicly fetchable image URL and test the exact product URL. This makes the right preview more likely, but cannot guarantee WhatsApp will display a preview card in every message.
Set Open Graph tags on each product page
Open Graph metadata describes a webpage for social previews. The protocol lists og:title, og:type, og:image and og:url as required properties; og:description is optional but generally recommended. Meta-attributed WhatsApp preview guidance also calls for nonempty title, description and canonical URL values, plus an absolute image URL. See the Open Graph protocol and the WhatsApp preview guidance reproduced by ChatArchitect.
As an Amazon Associate I earn from qualifying purchases.
<head>
<meta property="og:title" content="Product name and useful identifying detail">
<meta property="og:description" content="A short, accurate product description">
<meta property="og:url" content="https://shop.example.in/products/product-slug">
<meta property="og:image" content="https://shop.example.in/path/to/product-share-image.jpg">
<meta property="og:image:alt" content="Description of the product shown">
</head>Replace the example domain and values with your own. The canonical URL should identify the product page being shared, and the image should show that product—not a generic store image or a different product. Emit the tags for each product URL rather than relying on homepage metadata.
Make the tags available in the initial HTML
The cited WhatsApp-attributed guidance says the metadata should appear within the first 300 KB of the HTML response. Ensure your server or ecommerce platform returns these tags in the page head; do not depend on client-side JavaScript to add them after the initial response.
Prepare an image WhatsApp can fetch
Use a complete HTTPS image URL, such as https://shop.example.in/images/item.jpg, rather than a relative path like /images/item.jpg. The image and product page should be accessible without a login. Check that redirects, hotlink protection, access rules or asset-host restrictions do not prevent a public fetch.
The ChatArchitect mirror of Meta-attributed guidance gives these image recommendations: less than 600 KB, at least 300 pixels wide, and a width-to-height ratio no greater than 4:1. These are guidance from that source, not a promise that every WhatsApp client will render the image identically. The Open Graph protocol also defines optional image properties for secure URL, MIME type, width, height and alternative text.
Verify the exact URL before sharing
- Open the exact product URL customers will paste into WhatsApp.
- Inspect the HTML response and confirm that its head contains the expected product title, description, canonical URL and image URL.
- Open the
og:imageURL in a browser session where you are not signed in. Confirm it loads the intended image without an access challenge. - Check the image’s file size, pixel width and aspect ratio against the cited recommendations.
- Paste the exact product URL into a WhatsApp chat and inspect the preview. If a CRM or business messaging integration is involved, test through that tool and message type too.
A correct setup does not guarantee that every message displays a card. Preview behavior can differ between an ordinary pasted URL and a URL button in a template, so test the actual route your business uses. A crawler fetch is also not evidence that a customer clicked the link or bought the product. These qualifications are described in the Meta-attributed guidance mirrored by ChatArchitect.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsFix a missing, wrong or stale preview
| Symptom | What to check | Next step |
|---|---|---|
| No image or no preview card | Inspect the HTML for the exact URL; check that og:image is absolute and publicly fetchable. |
Correct the metadata or image access, then test the URL again in WhatsApp. |
| Wrong product image | Check whether the product page is emitting homepage tags, a shared default image or another product’s metadata. | Generate product-specific tags and confirm the canonical URL points to that product page. |
| Image is cropped awkwardly | Check the image dimensions and width-to-height ratio, and whether the chosen asset itself has excess empty space. | Use a representative product image within the cited size guidance, then retest. |
| Old image remains after a change | WhatsApp may cache preview information; the available sources do not establish an official cache lifetime or guaranteed clearing method. | Test a fresh share. Secondary guides suggest versioning or changing the image URL as a troubleshooting option, but do not promise an immediate refresh: OpenGraph Check and Share Preview. |
| Manual sharing works but integration does not | Check the connected sending tool and distinguish a text URL from a template URL button. | Test using the integration and exact message type customers receive. |
Choose between a website link and a WhatsApp Business catalog share
These are different ways to share a product, not two settings for the same preview.
| Route | Best fit | What it changes |
|---|---|---|
| Product-page Open Graph metadata | You want to share your own ecommerce website URL. | Controls the metadata available for an external webpage preview; the page and its image must be fetchable. |
| WhatsApp Business catalog sharing | You want to share catalog products within WhatsApp Business. | Uses the in-app catalog-sharing workflow rather than configuring an ordinary website URL’s Open Graph preview. |
WhatsApp Help Center pages describe catalog sharing in chats or status updates: catalog sharing on Android and product sharing on the web.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need to capture and inspect how a product page renders, ScreenshotNeo is a website screenshot API and MCP server. It can capture a page as PNG, JPEG, WebP or PDF. It is useful for checking the visible result, but a screenshot does not replace fixing the page’s Open Graph metadata or testing WhatsApp itself.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://shop.example.in/products/product-slug -o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo removes supported cookie banners, newsletter popups and chat widgets before capture; bot checks, blank pages and failed loads are not billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteProduct 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.
