What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Generate listing thumbnails from authorized property photos, not from a screenshot of the whole page: keep the original image, create responsive derivatives for the card and sharing layouts your site actually uses, and display them with a standard HTML <img>. There is no established India-wide thumbnail size. Set separate sharing metadata on each listing page, and treat Google’s image choice as a preference you can influence, not control.
Choose the image and thumbnail context first
A property thumbnail is a small, optimized derivative of a genuine image of that property. It is distinct from a screenshot of the listing page: a page screenshot can help you inspect how a listing looks, but it is not a replacement for an accurate property photo in a listing card or search preview.
As an Amazon Associate I earn from qualifying purchases.
Start with an image you are authorized to use and retain the original as the source of truth. PropertyHub India’s upload policy, last updated 19 November 2025, says media on its platform must be genuine and related to the actual property, clear, unaltered, and not misleading. That is PropertyHub’s policy, not evidence of a nationwide Indian rule. Read PropertyHub’s Photo & Document Upload Guidelines.
Make derivatives for real display slots
Inventory the layouts you need to support: listing cards, larger detail-page galleries, and link previews shared on social platforms. Choose each derivative’s dimensions and aspect ratio to suit its destination. A fixed crop makes a grid look consistent; a less aggressive or flexible crop can preserve more of a building or room. Check that the subject remains visible at the smallest size, especially when the source image is tall or wide.
#1 Best Overall
The reviewed official guidance does not establish one universal pixel size for Indian real estate thumbnails. Measure the actual card and preview layouts in your design, then test the crop at those sizes instead of adopting an unsupported country-wide standard.
Pre-generate or transform on demand
For a modest catalogue or a site that needs predictable output, generate the required derivatives when an image is uploaded and store them alongside the original. At larger scale, an image CDN can generate variants on demand; it is an optional delivery approach, not a requirement. Whichever approach you use, make sure the image URL placed in the page is public to the crawlers and users that need it. Google permits CDN-hosted image URLs in image sitemaps when they are accessible. Google’s image SEO guidance covers image discovery and responsive images.
Display thumbnails so crawlers can discover them
Use an HTML image element for the property photo. Google says it discovers images in standard HTML <img> elements and does not index CSS background images in the same way. Background images may be appropriate for decoration, but do not rely on one as the only way to expose a listing photo to search crawlers.
<img
src="/images/listings/123-card.webp"
alt="Bright living room in a two-bedroom apartment in Pune"
loading="lazy"
width="640"
height="426"
>Replace the example path and description with the actual image and visible content. The width and height should match the delivered file’s dimensions; the example values are illustrative, not a recommended standard. Write alternative text that describes what is visible rather than stuffing in search terms. If the image itself is a link to the property, ensure the link and surrounding text make the destination clear.
For responsive layouts, provide appropriate image variants using the browser’s srcset and sizes attributes or your site’s equivalent responsive-image pattern. Choose candidate files that fit the rendered slot and device density; verify in the browser that the expected derivative is requested. Google’s guidance recommends responsive-image practices and explains image discovery: Google Images SEO best practices.
Set social preview metadata on every listing page
Social link previews are separate from the thumbnail displayed in your own card grid. Set Open Graph metadata in each listing page’s HTML head so a shared link can advertise the specific property image, rather than a generic site image.
<meta property="og:image" content="https://www.example.in/images/listings/123-share.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="800">
<meta property="og:image:alt" content="Living room of the listed Pune apartment">The URL, dimensions, and description above are examples only; publish values that match the actual accessible image. Open Graph defines og:image and optional image type, width, height, and alt properties. Open Graph protocol.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteGoogle’s image previews are chosen automatically. Metadata such as og:image or Google-relevant primaryImageOfPage can indicate a preferred representative image, but neither guarantees that Google will show that image. Keep the page’s visible content and metadata aligned. Google image guidance.
Use structured data carefully and keep image URLs accessible
If you add structured data to describe the listing page or its main entity, use image URLs that crawlers can fetch and index, and make the markup accurately represent the page. Valid structured data can make a page eligible for supported search features; it does not guarantee a particular image or a rich result. See Google’s structured data introduction and structured data policies.
Use an image sitemap when it helps expose images that might otherwise be missed, including relevant CDN-hosted image URLs. It supplements discoverability; it does not override access restrictions or ensure a preview. Google’s image documentation describes sitemap support: Google Images SEO best practices.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Validate the page in its real destinations
- Check the rendered listing. Open the page at desktop and mobile widths. Confirm the correct property photo loads, the crop preserves the important subject, and the image is not hidden behind a CSS-only treatment.
- Inspect the image response. Confirm the URL resolves without login or a crawler-blocking rule and returns the intended image. Check that the URL in the markup and metadata is the derivative you meant to serve.
- Inspect page metadata. View the generated HTML and verify each listing has its own correct
og:imageand any structured data accurately reflects that listing. - Use Google’s inspection and supported result-testing tools where applicable. These can help identify crawl or markup issues; passing a test is not a promise about which image Google will display. Google’s policies and image guidance are available at Google Images SEO best practices and structured data policies.
- Test the shared link itself. Share a representative listing URL in the destinations your audience uses and inspect the generated preview. Social platforms may fetch and cache page metadata, so check again after correcting a wrong image rather than assuming a source-code change instantly changes an existing preview.
Troubleshoot common thumbnail and preview failures
- The card shows no image: check that the image URL is valid and publicly fetchable, and that the HTML contains an
<img>rather than only a CSS background. Inspect the browser’s network panel for a failed request. - The wrong property photo appears when shared: check the listing page’s rendered
og:imagevalue and ensure it points to that listing’s representative image, not a site-wide default or another property’s file. - The image is cropped badly: adjust the derivative’s crop or choose a more suitable source image for that slot. Do not stretch a small source to fill a differently shaped card; make a deliberate crop and verify it at the actual display size.
- Google shows a different image: Google selects previews automatically. Confirm the preferred image is accessible, relevant, and represented accurately in the page, but do not treat metadata or structured data as a guaranteed selection control.
- A structured-data test passes but the expected feature is absent: valid markup establishes eligibility, not guaranteed display. Confirm the image URL is crawlable and that the data reflects visible page content; consult Google’s policies for the relevant feature.
Or skip the browser setup
If you need a screenshot of the rendered listing page for a QA record or an internal visual preview, ScreenshotNeo can return a page screenshot via one GET request. This captures the page, not a standalone property-photo derivative, so use your image pipeline for listing-card and social images.
Install no browser for this API call; replace the example listing URL with a page you are authorized to capture. See the ScreenshotNeo documentation for request options.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.in/listing/123 -o shot.webpScreenshotNeo removes 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 per 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.
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.
