Bugs and Suggestions

Additional verification for stmk.pro performed on 23 September 2026.

TelegramBot receives HTTP 200 and a minimal 2,195-byte server-rendered HTML document with valid Open Graph metadata, without JavaScript, redirects or video tags. The public JPEG is 1200×630, 255,953 bytes and returns HTTP 200 with image/jpeg. robots.txt allows crawling, TLS is valid, and there is no X-Robots-Tag restriction.

Test URL: https://stmk.pro/?statuscheck=20260923-1
Image: https://stmk.pro/og/stmk-share-cover-v2.jpg

The unique test URL was sent in Telegram for macOS and still remained a plain link. A control URL, https://telegram.org/, generated a preview in the same chat. The issue also affects www.stmk.pro and archbeton.stmk.pro.

Please investigate and clear any domain-level negative cache, suppression or crawler-routing state affecting stmk.pro.

AlexeySep 25

The same issue affects https://biz4deal.com/ — only the exact root URL fails.

Reproduced September 25, 2026 in Telegram Web (Chrome) and Telegram Desktop:
1. Send https://biz4deal.com/ to @WebpageBot: it reports success but returns a plain link with no preview.
2. “Update with content” does not restore the preview.
3. https://biz4deal.com/?preview=team-en-20260925 produces the expected English preview with its image.
4. https://biz4deal.com/ru produces the expected Russian preview.

Both English URLs return HTTP 200 and byte-for-byte identical HTML in our requests using the TelegramBot user agent. Both responses have SHA-256: 6ef28c116bccfedad5cbb542368b0ef88ddab96d305431372c1680a97c814a3b.

Both use https://biz4deal.com/ as canonical and og:url. Open Graph metadata is in the initial HTML head, with no JavaScript required. Both reference https://biz4deal.com/og-250174a142.jpg — a public JPEG returning HTTP 200, 1200 × 630, 129882 bytes. robots.txt allows these URLs. The root response uses Cache-Control: public, max-age=0, must-revalidate. Changing the image URL and redeploying did not resolve the exact-root failure.

This suggests URL-specific cached failure or suppression in Telegram, but we do not have Telegram's internal fetch logs and cannot establish the internal cause. Please investigate and clear any failed preview state for https://biz4deal.com/ and regenerate its preview.

Lev KuzminSep 25

Telegram does not generate link previews for:

https://limonad.moscow/
https://limonad.studio/
https://limcast.ru/

Tests were performed on 25 September 2026 at 22:17–22:49 Moscow time. @WebpageBot reports a successful update, but Telegram still displays only a plain URL.

We also tested new minimal static pages:

https://limonad.moscow/telegram-preview-test-20260925.html
https://limonad.studio/telegram-preview-studio-test-20260925.html

They return HTTP 200, contain about 2 KB of static HTML with server-rendered Open Graph tags, matching og:url and canonical URLs, and no JavaScript, redirects, authentication, or cookies.

The public OG image is a 55 KB JPEG, 1200×630, and returns HTTP 200. DNS, TLS, HTML, and the image were successfully tested from several countries. External OG validation reports 100/100.

During controlled tests, Nginx logs contained the administrator’s browser requests but no requests from TelegramBot, WebpageBot, or Telegram infrastructure.

All three domains use the same Yandex Cloud server without a WAF, geographic filtering, or crawler blocking. Other websites generate previews in the same Telegram client.

Please check and clear any domain/IP-level negative cache, suppression, reputation state, or crawler-routing issue affecting these domains.

Expected: Telegram requests the page and displays its OG preview.
Actual: Telegram never requests the URL and displays only the plain link.

Almaz KarimullinOct 4

I’m experiencing the same issue with my website:

https://do100.pro/

The link preview does not appear for the exact root URL.

However, the preview works correctly when I add any query parameter, for example:

https://do100.pro/?f

@WebpageBot shows the same behavior: no preview for the root URL, while the URL with a query parameter generates a preview correctly.

The website is working normally and has valid Open Graph metadata with a publicly accessible preview image.

Since the exact same page works as soon as a query parameter is added, this seems to be an issue specifically affecting the root URL.

Could you please check the preview state for https://do100.pro/ and regenerate it?

Dmitry SergeevOct 7

Same issue with the entire contents of https://aisports.ru/ — it just shows 'Loading...' and then nothing, even though everything is configured correctly code-wise.

Sergey PimenovOct 8

The same issue affects pimenov.ai. Reproduced on 8 October 2026.

No preview:
https://pimenov.ai/articles/u-proekta-mozhet-byt-odin-polzovatel/

Full preview with title, description and image:
https://pimenov.ai/articles/u-proekta-mozhet-byt-odin-polzovatel/?preview=pim2-51-20261008

@WebpageBot reports success for both URLs. “Update with content” and sharing the clean URL again do not help.

Both URLs return HTTP 200 and byte-for-byte identical HTML in our diagnostic requests, including requests with an emulated TelegramBot User-Agent. Open Graph metadata is present in the initial HTML. The image is a publicly accessible 1200×630 JPEG returning HTTP 200. Canonical and og:url point to the clean URL.

Please investigate the preview state for the clean URL. The internal cause is unknown; adding a query parameter is only a workaround.

VladislavOct 8

Link previews are not working for the entire mtv36.info domain.
Neither the homepage (https://mtv36.info/) nor individual news articles generate previews in Telegram.
We have verified the following:
Open Graph metadata is correctly configured.The server returns HTTP 200.Images are publicly accessible.Canonical URLs and og:url are correct.robots.txt does not block crawlers.Server logs show repeated requests with the TelegramBot User-Agent, all receiving HTTP 200.Other websites, including telegram.org, generate previews correctly in the same Telegram client.
The problem affects our news website, mtv36.info, and prevents proper sharing of news articles.
Please investigate possible domain-level restrictions, cached failures, or link preview processing issues and help restore previews for mtv36.info.

GbtOct 12

The same issue occurs with all content on https://app.fixomni.io/ — only “Loading...” is displayed, followed by nothing, even though everything is configured correctly in the code.

@WebpageBot reports successful processing for both URLs. Using “Update with content” and reposting the clean URL does not help.

Testing performed on October 12, 2026, in Telegram Web (Chrome) and Telegram Desktop:
We tested a project invitation link using a request with the TelegramBot User-Agent. The server returns HTTP 200 and an HTML document of 4,885 bytes. The Open Graph metadata, including the project title and preview image URL, is present directly in the HTML. There are no redirects, and the document contains only one JavaScript tag.
The preview image is generated server-side in PNG format: 1200×630 pixels, 18,689 bytes. It is publicly accessible without authentication and returns HTTP 200 with Content-Type: image/png. The robots.txt file allows crawling.
However, during previous tests, requests from WhatsApp were recorded in our server logs, while we could not identify any requests originating from Telegram. Testing with a manually specified TelegramBot User-Agent confirms that the resources are accessible from our side, but does not prove that Telegram's servers receive the same responses.
Interestingly, we have one successful example on the same domain where Telegram did generate a link preview:
https://app.fixomni.io/join/0d8b5951bfae90f2df3bddebfd0ab90d

Please investigate and clear any negative caches, domain-level restrictions or blocks, or crawler routing state affecting app.fixomni.io.

Александр ЖигановOct 13

The same link-preview issue affects https://studio-shum.ru/.
Tested on 13 October 2026. Telegram displays only a plain URL. A fresh URL with a query parameter:
https://studio-shum.ru/?tg_preview=20261013
remains stuck on “Getting Link Info…”.
Server-side checks confirm:
pages and OG images return HTTP 200;Open Graph tags are server-rendered in <head>;robots.txt allows crawling;DNS and TLS work;there is no HTTP firewall or geographic filtering;requests using the TelegramBot user agent receive the complete HTML.
During the controlled test, Nginx recorded normal browser traffic but zero actual requests from TelegramBot or WebpageBot. The query URL also received no Telegram request.
All 36 public URLs were submitted to @WebpageBot. It replied “Link previews was updated successfully”, but no recrawl appeared in the server logs and previews remain absent.
The same Telegram chat successfully generates a preview for https://studio-shum.art/.
This appears to be domain-level negative caching, suppression or a routing problem inside Telegram’s preview backend. Please investigate and clear the preview state for studio-shum.ru.

Vitaly KukharenkoOct 15

Hello Telegram team,
We're experiencing an issue with link previews for our website:
https://justlist.io/ — No preview is generated at all.
https://justlist.io/?tg_test=20261015 — Preview works correctly.
Both URLs return identical Open Graph metadata, including og:title, og:description, and og:image.
We've verified that:
Both URLs return HTTP 200.Open Graph tags are present in the server-rendered HTML.The OG image is publicly accessible (HTTP 200, image/png, 1200×630).Requests using the TelegramBot User-Agent are successful.HTTPS and SSL certificates are valid.Refreshing through @WebpageBot does not resolve the issue.
This appears to be a stale or broken Telegram link preview cache associated specifically with the root URL.
Could you please investigate and invalidate the cached preview for https://justlist.io/?
Thank you!

MaxOct 18

Same issue affects yarostnayakoshka.ru and yakoshka.ru.
Both domains return HTTP 200. OG tags and image are valid, robots.txt allows crawling, and requests with TelegramBot User-Agent return HTTP 200.
When sharing a fresh /telegram-preview-test URL, no TelegramBot request reaches the server at all. @WebpageBot says the preview was updated successfully, but also produces no request and the preview remains missing.
As a control test, I exposed the same Flask app and same test page through a new *.trycloudflare.com hostname. Telegram immediately generated the correct preview there.
This strongly suggests a domain-level preview/crawler issue affecting yarostnayakoshka.ru / yakoshka.ru.

Show next 7 comments

Steps to reproduce

Device info

31068 Cards