How to Create Website Thumbnails for a Hindi Blog Link Page

To create a thumbnail for a Hindi blog link page, first decide where the image needs to appear: in a card on your own blog, in a preview when someone shares a page URL, or both. Make an image that remains clear at the destination’s small size, set it as the page’s featured image or card image, add Open Graph metadata for shared links, then inspect the published result on the target platform.

These are related but separate outputs. Your theme or link-page layout controls the on-site card. A social or messaging app uses metadata and its own crawler to choose a shared-link preview. A featured image may supply both, but a theme or platform is not guaranteed to use it for both.

1. Decide which thumbnail you need

Where it appears	What controls it	What to check
Your blog archive, homepage, or link page	The theme, template, or custom card layout	Which image field the card uses and how it crops the image
A preview when a URL is shared	Open Graph metadata and the sharing platform’s crawler	The published page’s `og:image` and the platform’s preview
Both	Both systems, which may use different crops or image files	Check the on-site card and each important sharing destination separately

Before following CMS-specific steps, identify your CMS and the destination platform. Exact settings and preview requirements vary. The steps below include WordPress details; other systems may use different names for featured images or social preview settings.

2. Design a thumbnail that works with Hindi text

Start with the content. Choose an image that reflects the post, rather than an unrelated decorative picture.
Make the main subject easy to spot. Use clear contrast and leave enough open space around important details.
Keep text brief. If you put a Hindi topic label on the artwork, preview it at the small size used by the link card. Check that the Devanagari font renders correctly and that the words remain legible after cropping.
Protect the important area. Keep the subject and any essential text near the center so a square or otherwise tighter crop is less likely to cut them off.
Export a suitable file. JPG or PNG are practical choices for broad social sharing. Check your CMS and target platform’s current file and size limits.

WordPress.com recommends 1200 × 630 pixels, close to a 1.91:1 ratio, JPG or PNG, and under 5 MB as a general starting point for social previews. Those are WordPress.com recommendations, not a guarantee that every theme or platform will display the image the same way. Its Facebook-specific guidance gives different limits: a 200 × 200 pixel minimum, at least 600 × 315 pixels for larger images, at least 1200 × 630 pixels for high-resolution displays, up to 8 MB, and a ratio near 1.91:1. Use the destination’s own current guidance where available. WordPress.com social preview recommendations · WordPress.com Facebook image guidance.

3. Set the image for the blog’s own link page

In your CMS, assign an image to the post or page using its featured image, thumbnail, or card-image control. Then check the actual archive or link page: a theme may use a different image size or crop than the one you uploaded.

WordPress: use a featured image

In WordPress, open the post or page in the editor, find the Featured image control, choose or upload the image, and update or publish the page. The theme must declare support for post thumbnails for the featured-image control to appear. WordPress themes can render featured images in archives, headers, or above the post, and can choose among registered sizes. WordPress Theme Handbook: Featured Images & Post Thumbnails.

The handbook lists these default registered sizes: thumbnail (150 pixels maximum), medium (300 pixels maximum), medium_large (768 pixels wide with no height limit), and large (1024 × 1024 pixels maximum). Media settings and themes can change the sizes actually produced. A theme can register a custom size with add_image_size(); set_post_thumbnail_size() can request proportional resizing or cropping. Check your theme’s output rather than assuming the source image will appear uncropped.

// In a theme's setup code, declare featured-image support:
add_theme_support( 'post-thumbnails' );

// Optional: register a landscape card size (width, height, crop):
add_image_size( 'blog-link-card', 600, 315, true );

// Render that size where the theme builds the card:
the_post_thumbnail( 'blog-link-card' );

This is theme PHP, not code to paste into a post’s text. Use your theme’s supported setup location and template. If you do not maintain the theme, use its settings or ask its maintainer which image field and crop the card uses.

4. Set the image for shared-link previews

For shared URLs, make sure the published HTML includes Open Graph properties. The protocol defines og:title, og:type, og:image, and og:url as the basic required properties for a page object. When the page specifies og:image, the protocol says it should also specify og:image:alt. Open Graph protocol.

<meta property="og:title" content="A Hindi guide to growing balcony herbs">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/hindi/balcony-herbs/">
<meta property="og:image" content="https://example.com/images/balcony-herbs-share.jpg">
<meta property="og:image:alt" content="Herbs growing in pots on a balcony">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">

Replace the example page URL, image URL, title, alt text, and dimensions with values for your published page and actual image. The image must be available at the URL you publish. Alt text should describe the image for people who do not see it; it is not a place to repeat keywords.

On WordPress.com, social metadata is added automatically for posts and pages. Its support documentation says the featured image is used first when selecting a social preview. If a plugin or theme also adds metadata, inspect the final page source to confirm there is one intended set of tags and that og:image points to the image you expect. WordPress.com social preview settings.

5. Publish and inspect both results

Publish or update the page and its image.
Open the blog archive or link page at desktop and mobile sizes. Confirm the right image appears and the crop keeps the subject and any Hindi label visible.
Inspect the published page’s HTML or source and confirm its Open Graph title, URL, image, and image alt metadata are correct.
Use the destination platform’s preview or inspection tool to see what its crawler reads. WordPress.com points users to Facebook’s Sharing Debugger and LinkedIn’s Post Inspector; it also describes Jetpack preview for multiple networks.
If a platform shows an old preview, request a fresh scrape or inspection where the platform offers that option. Facebook’s Sharing Debugger provides “Scrape Again.” Cached previews can take many days or weeks to refresh automatically, according to WordPress.com’s Facebook thumbnail support page.

A correct tag in your page source does not guarantee an immediate change in an already cached preview. Check the actual destination, not only your CMS editor.

6. Troubleshoot common thumbnail problems

Symptom	Likely cause	What to do
No image control in WordPress	The active theme may not declare post-thumbnail support, or the editor panel may be hidden.	Check the theme’s support and editor settings. The WordPress handbook documents `add_theme_support( 'post-thumbnails' )`.
The blog card shows the wrong image	The card template may use a different field, fallback image, or registered size.	Inspect the theme’s card template or settings; assign the image field it actually reads and check its crop.
The card crop cuts off Hindi text or the subject	The card uses a tighter or centered crop than the source image.	Move essential content toward the center, reduce overlay text, or create a crop specifically for the card.
The shared URL has no image	`og:image` may be absent, incorrect, or inaccessible to the crawler.	Inspect the published HTML and image URL. Confirm the tag points to the intended published image and try the platform’s preview inspector.
The shared URL shows an older image	The platform may have cached an earlier scrape.	Request a new scrape or inspection if available, then check the preview again.
The image looks soft or too small	The source or generated image size may be too small for the displayed preview.	Upload a sufficiently large source and verify the CMS-generated size. WordPress media settings and theme sizes affect generated files.
Hindi characters appear as boxes or break apart	The chosen font or export path may not render the required Devanagari characters.	Choose a font with Devanagari support and inspect the exported image at card size before publishing.
A platform rejects or ignores the image	The file, dimensions, size, URL, or platform-specific requirements may not fit its current rules.	Check that platform’s current guidance, ensure the image URL is public, and retry its inspection tool.

7. Keep the workflow reliable and efficient

Maintain separate crops when needed. A landscape social image and a compact archive card may need different crops. Reusing one image is convenient, but verify both destinations.
Use stable image URLs. If you replace an image at a new URL, update the page metadata and refresh the destination preview. A crawler may still have the previous URL cached.
Check after theme changes. Theme updates can change the rendered size or crop even when the featured image has not changed.
Keep the file within the destination’s limits. Compress oversized files while checking that small Hindi text and image detail remain clear.
Preview before publishing a batch. If you use a consistent template, inspect a representative Hindi thumbnail on the actual link page and sharing platform before applying the template across many posts.

8. Or skip the browser setup

If you need a screenshot of the finished page as a thumbnail source or a visual check, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a PNG, JPEG, WebP, or PDF. The API accepts options for full-page captures, viewport and device presets, image format, CSS selectors, custom CSS, wait conditions, and more. See the ScreenshotNeo API documentation for the available parameters.

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

# Python
import requests

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

// Node.js (modern Node.js with fetch)
const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com/hindi/'
});
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('shot.webp', Buffer.from(await res.arrayBuffer()));

Replace the example URL with your published page and put your API key in the request. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Use the resulting screenshot as a visual asset only if it fits your design and image rights; it does not replace setting the card image or Open Graph metadata. Sign up for 1,000 free screenshots a month, with no card.

Frequently asked questions

Can one thumbnail serve both my blog card and a shared URL preview?

It can, if your theme and sharing platform both use that image and its crop works in both places. Verify the card and shared preview separately.

No. A CMS may publish it as social metadata, but the destination crawler and its cache determine the preview it displays.

Should the Hindi title be part of the image or the page metadata?

Keep the page title in the page and its metadata. Put a short Hindi label in the image only if it remains legible at the final card size.

What image size should I use?

For a general social-preview starting point, WordPress.com recommends 1200 × 630 pixels. Your theme’s card crop and the sharing destination can have different needs, so inspect the published result.