How to Create Social Media Link Previews for an Indian Shopify Store
Set Shopify’s fallback and page images, check Open Graph tags, and debug stale or missing social previews with a practical workflow for Indian stores.
To create a reliable social media link preview for a Shopify store, set a store-wide fallback image, add a suitable featured image to each product, collection, and blog post, and verify that the active theme outputs the right Open Graph metadata. Then inspect the exact public URL with a platform preview tool and refresh cached data if a platform still shows an older preview.
The setup is the same for an Indian Shopify store as for other stores in the reviewed Shopify documentation: it does not describe India-specific social preview settings or behavior. Also, rich previews depend on the sharing platform and surface; do not assume every Instagram surface or messaging app will show the same card.
1. Set Shopify’s store-wide fallback image
- In Shopify Admin, open Online Store > Preferences.
- Find Social sharing image and SEO.
- Add or change the image, choose an image from your device, and save.
This image is a fallback for pages without another available image. It may not be the image a platform ultimately reads: Shopify documents a priority order in which images hard-coded in theme files can take precedence, followed by images in theme settings, then the Online Store Preferences image. Some themes also use a logo from theme settings as a fallback. If the Preferences field appears blank, inspect the theme’s social sharing and logo settings.
Choose a clear image that represents the store when used for pages that lack their own featured image. Check that the important subject remains understandable when the image is shown in a compact preview. Avoid relying on a logo with a transparent background or unsuitable shape as your only fallback; Shopify notes that theme settings can add a background color around some logos.
2. Give individual pages their own preview images
Shopify says its free themes use the featured image for product pages, collection pages, and blog posts. Pages without a featured image, such as the homepage and About page, use the store’s social sharing image. Shopify’s page_image Liquid reference describes the same featured-image and fallback behavior.
- Products: set a product image that accurately represents the item being shared.
- Collections: set a collection image that makes sense for the collection landing page.
- Blog posts: set a featured image for each post you expect readers to share.
- Pages and homepage: use the store-wide social sharing image unless the theme provides a page-specific option or you add appropriate theme metadata.
After changing a page image, test that page’s canonical public URL separately. A working homepage preview does not prove a product or collection page has the right image.
3. Check the title, description, and Open Graph tags
Social cards commonly use a page title and description along with an image. Shopify’s page_description Liquid reference describes the page description used in search listings and social previews. The Open Graph metadata commonly relevant to a shared page includes:
| Tag | Purpose |
|---|---|
og:title |
The title associated with the shared page. |
og:url |
The preferred URL for the page. |
og:type |
The content type. |
og:description |
A short summary. |
og:image |
The image a crawler can use for the preview. |
Shopify’s developer article explains these tags and older Liquid theme patterns. Theme structures change, so inspect your active theme and its rendered page source before adapting any older example. Shopify can automatically generate Open Graph image fallback tags using page_image when a theme does not include og:image tags.
4. Inspect the active theme before editing Liquid
First view the storefront page source or inspect the rendered document’s <head>. Search for og:title, og:description, og:url, and og:image. Confirm there is one coherent set of values and that the image URL is the one intended for that specific page.
If a tag is missing or wrong, locate the active theme’s metadata code before editing. Theme file names and snippet structure vary. Shopify’s older developer guide describes placing tags in the head and using Liquid values; use the current theme’s patterns and test its output after a change. Avoid blindly adding a second set of tags: duplicate or conflicting metadata can leave crawlers with ambiguous values.
For a theme that needs an explicit image fallback, Shopify documents the page_image object as a source for Open Graph image tags. A simple illustrative Liquid pattern is:
{% if page_image %}
<meta property="og:image" content="https:{{ page_image | image_url }}">
{% endif %}
Treat this as a pattern to adapt, not a drop-in replacement for every theme. Check how your theme formats image URLs and whether it already outputs these tags. Preserve any existing dimensions or secure URL tags and avoid emitting a duplicate og:image.
Shopify’s page_image documentation notes that Shopify automatically generates og:image, og:image:secure_url, width, and height fallback tags when a theme does not include Open Graph image tags. Verify the final rendered source rather than assuming a code change is required.
5. Preview the exact URL and refresh cached data
- Copy the exact public URL you plan to share, including the product, collection, or article path.
- Inspect the page’s rendered head and confirm its title, description, canonical URL, and image are correct and publicly accessible.
- Use a platform’s available preview inspection tool. Shopify names Facebook’s crawler/Sharing Debugger, LinkedIn’s Post Inspector, and Twitter’s Card Validator as examples.
- If Facebook displays an old image after a change, use the Sharing Debugger to refresh the saved link data. Shopify notes that Facebook can retain image data for a number of days.
- Test the URL in the actual sharing context when possible. A preview tool reports what its crawler reads; presentation can vary across platforms and app surfaces.
For an additional visual check, capture the publicly rendered page and compare what is actually visible with the metadata image. That can help distinguish a wrong social image tag from a storefront page that itself has loaded incorrectly.
6. Troubleshoot missing, wrong, or stale previews
| Symptom | Likely cause | What to check or do |
|---|---|---|
| The wrong image appears | A hard-coded theme image or theme setting outranks the Preferences fallback; a page-specific featured image may also be the intended source. | Check the page’s featured image first, then inspect theme code and theme settings, and finally the Preferences image. Confirm the rendered og:image. |
| The homepage image is correct but product previews are not | Different page types can use different featured images and metadata. | Inspect the exact product URL and its product image, then verify the rendered tags. |
| The Preferences image field looks blank | The theme may be sourcing an image from its own social or logo settings. | Review the theme’s social sharing and logo settings; add an explicit Preferences fallback if needed. |
| The updated image does not appear on Facebook | The platform may be showing saved preview data. | Refresh the URL with Facebook’s Sharing Debugger, then check again. |
| No image appears in the preview inspector | The theme may omit a usable image tag, or the crawler may not be seeing the expected rendered metadata. | Inspect the public page source for og:image, check the URL it points to, and confirm the active theme’s fallback behavior. |
| The title or description is wrong | The page’s SEO fields or theme metadata may be supplying a different value. | Check the page title and description in Shopify, then inspect og:title and og:description in the rendered head. |
| A code change creates inconsistent results | Existing theme tags may duplicate or conflict with the added tags. | Remove the duplicate source or adapt the existing metadata snippet; verify the rendered head after saving. |
| A preview works in one app but not another | Apps and platform surfaces can interpret or display previews differently. | Check each platform’s crawler or preview tool where available, and avoid assuming one result guarantees identical rendering everywhere. |
7. Choose the lightest maintenance approach that works
| Approach | Per-page control | Code and upkeep | Best fit |
|---|---|---|---|
| Shopify featured images and Preferences fallback | Good for product, collection, and blog images; one fallback for other pages. | Low setup; review theme behavior if the expected image does not win. | Most stores with standard sharing needs. |
| Theme metadata changes | Can provide more direct control over title, description, and image behavior. | Requires theme code access and review after theme changes. | Stores whose current theme output does not meet their page-level needs. |
| Shopify app | Depends on the app’s advertised capabilities. | Adds setup and potentially recurring cost; verify current listing terms and theme compatibility. | Merchants who need controls not provided by built-in settings and prefer an app workflow. |
The Shopify App Store listing for PreviewBuilder: Link Image advertises templates and image or metadata customization for products, collections, pages, blogs, and articles. App features, availability, and pricing can change; check its current listing before choosing it. Use an app only when the built-in image and theme behavior do not meet the store’s needs.
8. Performance, reliability, and cost notes
- Performance: This workflow relies on Shopify’s page images and metadata. Keep the shared image appropriate to the page and confirm that the image URL in the rendered metadata resolves for a public crawler.
- Reliability: The preview is generated from what a platform can read and may be cached. Re-check the exact URL after changes and refresh saved platform data when that platform provides a tool.
- Maintenance: Theme edits require review when changing or updating themes because theme metadata structures vary. Reinspect the rendered head after edits.
- Cost: Shopify’s built-in fallback and featured-image workflow does not require a separate preview app. An optional app may have a subscription; check its live listing rather than relying on old prices.
Or skip the browser setup
For a visual check of a public storefront URL, ScreenshotNeo is a website screenshot API and MCP server. Its one-call API returns an image or PDF; see the API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://your-store.example/products/example -o shot.webp
Replace the example URL with the public Shopify page you want to inspect. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response includes page-verdict and billing headers. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for 1,000 free screenshots a month, no card required.
Frequently asked questions
Does an Indian Shopify store need different social preview settings?
The reviewed Shopify setup documentation does not identify India-specific settings or behavior. Use the same fallback, featured-image, metadata, and preview-check workflow.
Will every Instagram share show a link card?
Do not assume every Instagram surface renders a rich link card. Preview behavior depends on the platform and the context where a link is shared.
Should I use the store logo as the social image?
A logo can be a fallback, but page-specific featured images are generally the relevant source for products, collections, and blog posts in Shopify’s free themes. Check how the theme handles the logo and fallback image.
Do I need to add Open Graph tags manually?
Not necessarily. Inspect the active theme and rendered source first. Shopify can generate fallback image tags when the theme lacks them.
What should I do after replacing the social image?
Check the rendered metadata and use the platform’s refresh or inspection tool if it continues to show saved older data. Shopify specifically recommends Facebook’s Sharing Debugger for refreshing Facebook’s saved link information.


