What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Generate listing thumbnails from authorized, genuine property photos; create image variants for the actual card and sharing layouts; and expose them through standard HTML images and page metadata. There is no established India-wide thumbnail size, and neither Google nor social metadata guarantees which image a platform will display.

Start with a genuine, authorized property image

Keep the original photo as the source of truth and create separate display versions from it. Confirm you have permission to use the image, and avoid edits that make the property appear materially different from the original. For example, PropertyHub India’s Photo & Document Upload Guidelines, last updated 19 November 2025, require media on that platform to be genuine, property-related, clear, unaltered, and not misleading. That is PropertyHub’s policy, not evidence of a nationwide rule for Indian listings.

Choose sizes and crops for your actual layouts

The reviewed guidance does not establish a universal thumbnail pixel size for real estate websites in India. Instead, inspect the listing card, property detail page, and social preview layouts your site supports, then generate derivatives that fit each one.

  • Fixed crop: Useful when cards need a uniform grid. Apply one consistent rule and check that it does not cut off important property details.
  • Flexible aspect ratio: Better when showing the full view matters more than consistent card heights.
  • Responsive variants: Serve an appropriately sized derivative for the layout and screen rather than relying on one oversized file. Google’s image SEO guidance links to responsive-image practices and allows CDN-hosted URLs in image sitemaps.

Pre-generated derivatives and on-demand CDN transformations are both possible delivery approaches; the sources do not establish a particular CDN as necessary or identify one best choice. Whichever approach you use, verify that the final image URL is publicly accessible to the intended crawlers.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Make listing images discoverable and accessible

Place the card image in a standard HTML <img> element, with useful alternative text that describes the visible property image. Google says it discovers images in HTML image elements and does not index CSS background images in the same way. An image sitemap can also expose images that might otherwise be missed; see Google’s image guidance.

For example, a server-rendered listing card can use:

<img
  src="https://example.com/images/listing-123-card.webp"
  alt="Living room in a two-bedroom apartment in Pune"
  width="640"
  height="480"
  loading="eager"
>

Replace the example URL, dimensions, and description with values for your image and layout. Dimensions in the markup help the browser reserve space; they are not a recommended universal thumbnail size. Avoid using generic alt text such as “property image” when you can describe what is actually visible.

Set metadata for link previews and Google separately

Social link previews

Set Open Graph metadata on each listing page so link-sharing services have a representative image to consider. The Open Graph protocol defines og:image and optional properties for its MIME type, dimensions, and alt description. Use an absolute, reachable image URL and make the metadata specific to the listing. See the Open Graph protocol.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
<meta property="og:image" content="https://example.com/images/listing-123-share.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Apartment living room with large windows">

The example dimensions illustrate metadata fields, not an India-wide or platform-wide requirement. Choose a share image and crop that suit the destinations your visitors use, then verify how those destinations render it.

Google image selection

Google chooses image previews automatically. You can indicate a preferred representative image using metadata such as primaryImageOfPage or an image attached to the page’s main entity, but you cannot guarantee that Google will use it. Google’s image documentation describes this selection behavior.

If you add structured data, ensure its image URL is crawlable and indexable and that the markup accurately represents the page. Valid structured data may make a page eligible for a search feature, but it does not guarantee display. Consult Google’s structured data policies and structured data guidelines.

Validate the page and its image URLs

  1. Inspect the rendered page. Confirm the correct listing image appears in the card and that the image is an HTML <img>, not only a CSS background.
  2. Check page metadata. View the page source or rendered HTML and confirm the listing-specific og:image and any Google-facing image metadata point to the intended image.
  3. Check crawler access. Open the image URL without a login or session and verify that the page and image are not blocked from crawling. Structured-data image URLs need to be crawlable and indexable.
  4. Test supported Google features where applicable. Use Google Search Console inspection tools and supported rich-result tests to review what Google can access. Passing a test does not promise a particular preview or search display.
  5. Check actual sharing destinations. Share the listing URL in the services relevant to your audience and review the preview. Metadata gives services a candidate image; each service controls its own rendering.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Or skip the browser setup

If you need a screenshot of a live listing page rather than a derivative of its source photo, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a PNG, JPEG, WebP, or PDF. For a WebP capture, replace the example target URL with your listing page:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/listing/123 -o shot.webp

See the ScreenshotNeo documentation for request options. Cookie banners are accepted before capture and more than 60 known consent platforms, newsletter popups, and chat widgets can be removed; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers say which page verdict applied and whether the request was billed. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.

Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.

Common problems and fixes

  • The expected image is missing from Google. Google selects previews automatically. Confirm that the image is accessible, relevant to the page, and exposed in crawlable HTML or supported metadata; then inspect the page using Google’s tools. Correct markup cannot force a particular image choice.
  • A crawler does not find the image. If the image is only a CSS background, expose it with an HTML <img>. Check that the URL is publicly accessible and consider an image sitemap for images that might otherwise be missed.
  • A shared link shows the wrong image. Check that the listing page’s Open Graph tags point to the correct listing-specific image and that the URL is reachable. Review the preview in the target sharing service; its display is not guaranteed by the metadata standard.
  • A structured-data image is ignored or flagged. Verify that the image URL can be crawled and indexed and that the structured data accurately describes the page. Eligibility is not a promise of display.
  • A crop hides an important feature. Revisit the crop rule for the card layout. Use a flexible ratio or a different derivative when preserving the full property view matters more than uniform card dimensions.

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.