How to Fix Missing Website Previews in Telegram
Diagnose missing Telegram link previews by checking the exact URL, page metadata, image access, and crawler requests—then know what to do if those checks pass.
A missing Telegram website preview usually comes down to one of three things: the message or URL being tested, page metadata or image access, or Telegram fetching the page successfully but not displaying a preview. Check the exact URL, inspect the public HTML and image, and review your server or CDN logs for Telegram crawler requests. If those checks are clean, record what happened and escalate; there is no guaranteed cache-clearing trick.
1. Check the message and exact URL
Start with the URL recipients actually share. Confirm it uses the intended public https:// address and that link previews have not been disabled in the composing or sending flow. Test the exact form of the link: the site root, a path, or a URL with a query string can behave differently.
- Send the URL in the same Telegram chat and client where the problem occurs.
- Compare it with a known-working link in that same chat and client.
- If the page has a root URL, a path, or query variants, test each relevant form separately and note which one produces a preview.
A URL variant that works while another does not is a useful diagnostic clue. It does not establish the cause, and adding arbitrary query parameters is not a reliable permanent fix. Keep canonical URL behavior intact.
2. Check whether Telegram can reach the page and image
A page loading in your browser does not show that Telegram’s crawler received the same response. Check the public route and the request logs for the time of a controlled test. Look for requests attributed to Telegram’s crawler, then inspect the status code, redirect chain, and image requests. User reports describe this kind of investigation, but they do not provide a complete official crawler specification. Telegram issue report c/61650 and issue report c/61806 are examples of reported symptoms, not confirmed explanations of Telegram’s internal behavior.
For both the HTML page and preview image, verify that an unauthenticated public request can retrieve the content without a login, cookie, JavaScript execution, or interactive challenge. Also check DNS, TLS, redirects, CDN and web application firewall rules, and robots directives for restrictions affecting the public page or its image.
- If a crawler request reaches your origin and gets an error or block: fix the response, redirect, access rule, TLS or DNS issue, then retest.
- If no request appears in your logs: review the public route, DNS and TLS, CDN or firewall rules, redirects, and bot restrictions. A missing origin log entry alone cannot show why Telegram did not request the URL.
Record the test time and exact URL so you can correlate the request with your logs. A successful fetch is useful evidence, but it does not guarantee a rendered preview.
3. Verify the metadata in the initial HTML
Inspect the HTML returned to an unauthenticated request, not just the settings page in your CMS. The returned page should identify the linked content with an accurate title and description, provide a suitable public image when one exists, and use a site name that matches the identity visitors see. Telegram’s official Instant View checklist describes these preview content recommendations. It does not state a universal image dimension or file-size limit.
Check that:
- The title and description describe this specific page rather than only the site in general.
- The image URL is public and returns the intended image without a login, challenge, or broken redirect.
- The image is a suitable cover for the page, rather than an empty image or generic logo when a relevant cover is available.
- The site name matches what readers see on the site.
- The metadata is present in the initial HTML response and is not added only after client-side JavaScript runs.
If your CMS, plugin, or framework generates Open Graph metadata, inspect its actual output and open the image URL directly. Correcting metadata makes the page’s preview information clearer to a fetcher; it does not guarantee how quickly Telegram will refresh or display a preview.
4. Interpret the results without assuming a cache fix
Telegram’s messages.getWebPage API documentation describes webpage objects and a URL and hash mechanism for caching in that API context. It does not document a general command for website owners to clear every missing preview.
Some users report a preview appearing for a query-string variant when the exact root URL fails, while other reports describe successful page and image fetches without a visible preview. These cases show why the exact URL and client matter to diagnosis; they do not confirm a negative cache, suppression rule, or other internal cause. Sending a link to @WebpageBot has been reported as an attempt, but it is not a guaranteed cache reset.
| Evidence | Next step | What it does not establish |
|---|---|---|
| The crawler request is blocked or returns an error | Correct access controls, redirects, DNS, TLS, or the server response, then retest. | That hosting is the cause of every missing preview. |
| The page is fetched, but metadata or its image is missing or unsuitable | Correct the initial HTML metadata and make the intended image publicly accessible. | That Telegram will update the preview immediately. |
| Page, image, and metadata appear valid, but no preview appears | Compare exact URL forms and clients, preserve evidence, and report the behavior. | That a cache or suppression mechanism is confirmed. |
| One URL form works and another does not | Document and repeat the comparison; preserve canonical URL behavior. | That adding query parameters is a safe general workaround. |
5. If the preview still does not appear
If the page and image return valid public responses, the metadata describes the page, and logs show Telegram fetched the resources, gather a concise diagnostic record before reporting the issue through Telegram’s support or issue channels.
- The exact URL and the time of the test in UTC.
- The Telegram client and platform used.
- The page and image response status codes and relevant redirect destinations.
- A short, relevant server or CDN log excerpt showing the requests, if present.
- The result for a control link tested in the same client.
Describe observations rather than guessing at Telegram’s internal cause. User reports can document a symptom for a particular site, client, and time; they do not prove how Telegram handled another link.
Or skip the browser setup
If you need to inspect how a page renders, ScreenshotNeo is a website screenshot API and MCP server for developers. A screenshot can help you spot a blank or unexpected rendered page, but it does not prove what Telegram’s crawler fetched or diagnose Telegram’s preview service.
One GET request returns an image or PDF. For a quick page check, save the response as an image:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for the request options. Cookie banners, popups, and chat widgets are removed before the shot; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status. An MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan.
Sign up free for 1,000 screenshots a month, with no card required.
FAQ
Does a missing preview mean my website is broken?
No. A missing preview can reflect metadata or crawler access, but reported cases also include successful page and image fetches without a visible preview.
Will adding a query string force Telegram to refresh the preview?
There is no supported guarantee. A query variant can be used as a controlled comparison, but do not treat it as a universal workaround.
Can a screenshot confirm that Telegram’s preview will work?
No. A screenshot shows a rendered view from the screenshot service. It does not establish what Telegram fetched or whether Telegram will display a link preview.
