Recommended Free Tools
Add page-specific Open Graph metadata to each page’s HTML <head>, including og:image set to a publicly accessible image URL. For a Tamil-language page, use lang="ta"; choose an Open Graph locale such as ta_IN only when the page targets Tamil readers in India. Then inspect the deployed HTML and refresh the relevant platform’s preview if it has cached older metadata.
Add the metadata to each page’s HTML head
The social-sharing image is an existing image file referenced by metadata; adding a tag does not create or upload the image. Each page should supply its own title, description, canonical URL, and image URL so a shared template or CMS can generate accurate previews for every route.
As an Amazon Associate I earn from qualifying purchases.
Here is a minimal example. Replace the sample values with the actual page data and a publicly fetchable image asset:
<!doctype html>
<html lang="ta">
<head>
<meta charset="utf-8">
<title>தமிழ் பக்கத் தலைப்பு</title>
<meta property="og:type" content="article">
<meta property="og:title" content="தமிழ் பக்கத் தலைப்பு">
<meta property="og:description" content="இந்தப் பக்கத்தைப் பற்றிய சுருக்கமான விளக்கம்.">
<meta property="og:url" content="https://example.com/ta/article/">
<meta property="og:image" content="https://example.com/images/ta-article-share.jpg">
<meta property="og:image:alt" content="பக்கத்தின் உள்ளடக்கத்தை பிரதிபலிக்கும் படம்">
<meta property="og:locale" content="ta_IN">
<meta name="twitter:card" content="summary_large_image">
</head>
<body>
<!-- Page content -->
</body>
</html>The Open Graph protocol describes a web page as a rich object in a social graph. Its core properties for this use are og:title, og:type, og:url, and og:image. Include a useful og:description and descriptive og:image:alt as well. If you specify og:image, the protocol says to specify image alt text.
#1 Best Overall
Match language and locale to the page
Set lang="ta" on the document’s <html> element for Tamil content. HTML’s lang value uses a BCP 47 language tag, and ta identifies Tamil. If a portion of the page switches to another language, mark that element with its own appropriate language tag.
og:locale is separate from HTML’s lang. Open Graph expresses it as a language-and-territory value: ta_IN is an example for an India-localized Tamil page, not a universal locale for Tamil readers everywhere. Choose the territory that reflects the intended audience, rather than copying the example onto every Tamil page.
Use a distinct image and canonical URL for each page
Use an image that represents the page, not just a generic site logo. The image URL in og:image should be the public URL of the actual asset, and og:url should identify that page’s canonical URL. A Tamil and an English version with separate URLs should each receive metadata generated from that version’s content and canonical URL.
Optional image properties such as width, height, and MIME type can be declared when those values are known. Do not add guessed dimensions or type values.
Choose an implementation that emits page-level values
For a site with many routes, put the metadata logic in a shared layout or template and feed it values from each page’s data. A CMS-native setup can work too if editors can maintain the title, description, canonical URL, and image for each page. Either approach succeeds only if the delivered HTML contains the right unique values for that route.
- Shared template: useful when route data reliably supplies each page’s Tamil metadata and image.
- CMS fields: useful when editors need to choose or update page-specific share details themselves.
- Either approach: ensure tags appear in the HTML head delivered to crawlers, and avoid duplicate tags from overlapping CMS and template output.
Prepare an image for social previews
No single image dimension in the Open Graph specification guarantees identical rendering across services. Netlify gives 1200 × 630 pixels as a recommended example; Webflow reports Facebook guidance of at least 1080 pixels in width and recommends consistency across a site. Treat these as practical guidance, not universal requirements. Use a clear, high-resolution image with a moderate aspect ratio, then check the current guidance for the platforms your readers use.
When the image may also appear as a Google image preview, Google recommends avoiding generic images and images containing text. Webflow’s asset picker supports JPG and PNG; its help guidance says WebP is supported by many popular social platforms but support can vary. If broad compatibility matters, choose a commonly supported raster format and verify it on the target services.
Check the deployed page and preview
- Deploy the page, then inspect its served HTML head. Confirm that the title, description, canonical URL, image URL, locale, and card type match that specific route.
- Check for duplicate metadata, especially if both a CMS and a shared template generate Open Graph tags.
- Open the page in the preview or debugging tool for each important platform. Webflow documents Meta’s debugger, LinkedIn’s Post Inspector, and X’s Card Validator; use each platform’s current tool and workflow.
- If a service shows old data, request a fresh scrape or refresh there. The new preview may depend on that service fetching the updated page and image.
Social platforms consume and render metadata independently, so a correct HTML head does not guarantee identical cards everywhere. Google also selects images automatically from multiple possible sources: og:image may influence its choice, but does not guarantee a particular Google result.
Troubleshoot missing or incorrect images
The card has a title but no image
Check that og:image points to the actual image file, that the URL is publicly accessible to the platform, and that the file format works on that service. Confirm the tag is present in the deployed page head, not just in an editor preview.
Rank #4
- Elevate your content creator journey with this unique design that resonates with the essence of blogging and vlogging. Stand out in the social media landscape and embrace your inner influencer.
- Capture the spirit of content creation with this exclusive design. Perfect for the dedicated vlogger or blogger looking to reflect their passion for storytelling and connecting with audiences.
- Hardcover journal with 240 line-ruled pages (120 sheets)
- Built-in elastic closure and ribbon bookmark
- Includes an expandable inner storage pocket and a pen holder
The previous image still appears
The platform may be using an earlier scrape. Request a refresh using its debugging tool; Webflow documents a refresh action in Meta’s debugger and re-scraping in LinkedIn’s Post Inspector.
A different page’s title or image appears
Check that the route emits its own canonical og:url and page-specific title, description, and image. Remove duplicate Open Graph tags generated by the CMS and shared layout, since conflicting values can produce an unexpected preview.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Different services show different layouts
Check the page with each relevant platform’s current preview tool and follow that service’s guidance. Image dimensions, format support, caching, and card presentation are not guaranteed to be uniform.
Best Value
Google chooses another image
Google selects images automatically and may consider more than Open Graph metadata. Providing og:image can influence selection but cannot force Google to use that exact image.
Or skip the browser setup
If you want a screenshot of the deployed page for your own visual check, ScreenshotNeo can capture it with one API request. This does not replace checking a social platform’s preview tool: it captures the webpage rather than validating how a platform interprets its metadata. ScreenshotNeo is a website screenshot API and MCP server; its clean-shot options can accept cookie/consent banners and remove known consent platforms, newsletter popups, and chat widgets before capture.
For example, save a WebP screenshot of the deployed Tamil page with cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/ta/article/ -o shot.webpSee the ScreenshotNeo API documentation for request options. Bot checks/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 AI agents. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
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.
