How to Create Marathi Social Card Images for Website Links
Create a readable Marathi link preview with a landscape image, page-specific Open Graph tags, and a check of the preview on your target platform.
To create a Marathi social card for a website link, make a landscape image with a short, legible Marathi headline, publish it at a publicly fetchable URL, and add page-specific Open Graph metadata pointing to that image. Then inspect the shared URL on the platform where you plan to post it: platforms can crop, resize, and cache previews differently.
1. Write and render-check the Marathi copy
Decide what a reader should understand from the preview, then write the Marathi headline and supporting message before designing the image. Keep the key phrase concise so it remains readable when the card is shown at a reduced size. Check spelling and punctuation; if you are not confident in Marathi, ask a fluent reader to review the final copy.
Use a font that contains the Devanagari characters in your copy. Render the actual image and inspect it for missing glyphs, incorrectly placed vowel marks, or conjuncts that appear broken. Do not assume a browser’s fallback font will produce the result you expect. Google’s Fonts documentation describes loading a web font through a stylesheet and specifying a generic fallback family; it does not name a best font for Marathi artwork. Google Fonts API: getting started.
2. Design a landscape image for the target platform
Leave breathing room around the headline and important artwork. A preview may be reduced or cropped, so avoid placing essential content at the extreme edges. Export a widely supported image format and keep the file within the destination platform’s limits.
| Destination or guidance | Image guidance in the research | How to use it |
|---|---|---|
| Minimum 1200 × 627 pixels; recommended 1.91:1 ratio; 5 MB maximum for the sharing module. Images narrower than 401 pixels display as thumbnails. | Use these LinkedIn-specific constraints when preparing a card for LinkedIn. LinkedIn: Make your website shareable. | |
| Facebook workflow described by Webflow | Webflow recommends JPG or PNG, cites a Facebook image width recommendation of at least 1080 pixels, and gives 1200 × 630 as an example. | Treat this as Webflow’s Facebook workflow advice, not a universal specification. Webflow: Control the look of social shares with Open Graph. |
There is no single dimension or file limit established here for every social platform. Check the target service’s current requirements and preview the actual shared page there.
3. Publish the image and set page-specific Open Graph metadata
Put the image at a stable public URL that a social crawler can retrieve. The page and image must not require a login or be blocked by access rules that prevent crawler fetching. Add metadata to the HTML of the page being shared, using that page’s own title, description, image URL, and canonical share URL.
<meta property="og:title" content="मराठी लेखाचे शीर्षक">
<meta property="og:description" content="लेखाचा थोडक्यात मराठी परिचय">
<meta property="og:image" content="https://example.com/images/marathi-share-card.jpg">
<meta property="og:url" content="https://example.com/marathi-article">Replace the example values with the Marathi page’s real content and the image’s actual public URL. LinkedIn identifies these four Open Graph fields as relevant share information. Webflow also recommends making social-share content specific to the page.
4. Inspect the live preview and refresh stale data
- Publish the page and verify its source contains the intended metadata.
- Open the image URL directly in a browser or request it without a logged-in session to confirm it is publicly accessible.
- Use the destination platform’s preview or debugging workflow, if available, to inspect the URL that readers will share.
- If the preview shows an older image, use the platform’s available re-scrape or cache-refresh workflow and inspect it again. Webflow recommends pre-caching with Facebook’s debugger, including after image changes.
- Check the same URL on each platform you care about. A correct preview on one service does not guarantee the same crop or cached result elsewhere.
5. Create a card image from HTML when you need repeatable output
If your site already renders the Marathi card as HTML, a browser-based capture workflow can turn that page into an image. Load the intended Devanagari font before capture and wait until the card is rendered; otherwise the output may contain fallback glyphs or an incomplete layout. This method creates the image asset. You still need to publish it and set the page’s Open Graph metadata as described above.
For a hand-built card, use your usual design workflow and export the image. For a generated card, render the page in a browser at the intended landscape dimensions, capture it, and inspect the resulting file at both full size and preview size. The research dossier does not establish a particular browser library or capture-tool API, so the code below shows the metadata needed after you have created and hosted the image rather than prescribing an unverified rendering package.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. If your card is rendered on a public webpage, one GET request can capture it as an image. The API also supports custom CSS and JavaScript, viewport choices, and element capture by CSS selector. See the ScreenshotNeo API documentation for parameters and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/marathi-card -o marathi-card.webpCookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An 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. Create a free ScreenshotNeo account.
Troubleshooting
| Problem | Likely cause | What to check |
|---|---|---|
| Marathi characters are missing or look broken | The chosen font lacks glyph coverage, the intended web font did not load, or rendering changed conjuncts or vowel marks. | Inspect the rendered image, confirm the font loaded and covers the copy, and set a suitable fallback. Ask a fluent Marathi reader to check the final text. |
| The social preview has no image | The image URL is wrong, the crawler cannot fetch it, or the page metadata is absent or incorrect. | Open the exact image URL without authentication, check crawler access rules, and inspect the page’s og:image and other Open Graph values. |
| The old image appears after an update | The platform is showing a cached preview. | Use the platform’s available re-scrape or debugger workflow. Webflow recommends pre-caching with Facebook’s debugger for its Facebook workflow. |
| The preview is cropped differently across services | Platforms apply different preview behavior and image constraints. | Check the target platform’s documented requirements, keep key content away from edges, and inspect each destination’s actual preview. |
| The image is reduced to a thumbnail on LinkedIn | LinkedIn reports that images narrower than 401 pixels display as thumbnails. | Provide an image meeting LinkedIn’s stated minimum dimensions and ratio guidance. |
Performance, reliability, and cost considerations
- Keep the asset retrievable: A publicly fetchable image and page are prerequisites for crawler previews. Avoid access controls that require a session.
- Use a suitable export size: Follow the destination’s stated dimensions and file-size limits. The LinkedIn limits above apply to LinkedIn’s sharing module.
- Account for caching: Metadata or image changes may not appear immediately because a platform can reuse a cached preview. Re-scrape where supported and verify the result.
- Render only when useful: For a static card, create and publish the image once. For frequently changing or page-specific artwork, automate rendering and check that fonts and content finish loading before capture.
- ScreenshotNeo billing: ScreenshotNeo states that only clean shots are billed; bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Its responses identify page verdict and billing status in headers. See the product documentation for the applicable response details.
FAQ
Does the Marathi text belong in the image or only in metadata?
If you want the Marathi headline visible in the card artwork, put it in the image. Also set Open Graph title and description so the page has share text; metadata alone does not draw text into the image.
Can I use the same card image on every platform?
You can, but the researched requirements only establish specific guidance for LinkedIn and Webflow’s Facebook workflow. Inspect the card on each destination and adjust if its crop or size makes the Marathi text hard to read.
Will updating og:image immediately change existing shares?
Not necessarily. Platforms may cache previews. Refresh or re-scrape the URL where the platform provides that option, then check the resulting preview.
