Bugs and Suggestions

I have reproduced a closely related root-only link preview issue for https://kapital-rust.wtf/.

The exact root gets no preview and, during controlled origin correlation, no TelegramBot/WebpageBot request reaches the origin. A query variant such as https://kapital-rust.wtf/?tg is fetched by TelegramBot and generates the correct preview.

I also reproduced this with Bot API LinkPreviewOptions: the visible root URL can display a preview when the preview URL is explicitly set to /?tg, which isolates the failure to Telegram's handling/state of the exact root preview URL.

Full report:
Link preview still not generated for exact doma... #65828

Valentin GrachevSep 19

The same link preview issue affects https://valentingrachev.ru/.
Controlled tests performed on 19 September 2026:
A control link, https://telegram.org/, generated a correct preview in the same Telegram chat.TelegramBot at 149.154.161.213 requested https://valentingrachev.ru/?tg_audit=20260919-1433 and received HTTP 200 with the complete 140,063-byte HTML response.No subsequent request for the Open Graph image was made, and no preview appeared.After replacing the preview asset with a fresh JPEG URL, https://valentingrachev.ru/og-r35.jpg, a new unique URL https://valentingrachev.ru/?tg_r35=1 displayed “Generating link preview…” and then fell back to a plain URL. No request for this fresh URL reached the origin server.
The website has been verified to return:
HTTP/2 200 and Content-Type: text/htmlvalid TLSworking IPv4 and IPv6consistent public DNSno X-Robots-Tag, WAF challenge or crawler restrictionserver-rendered Open Graph tags near the beginning of the HTML heada public 1200×630 JPEG Open Graph image, 131,994 bytes
@WebpageBot did not resolve the issue.
This appears to be a domain-level negative cache, suppression or routing issue inside Telegram’s link preview backend. Please investigate and clear any affected preview state for valentingrachev.ru.

Nikita M.Sep 23

The same link preview issue affects electro-energo-estet.ru.

Controlled tests performed on 23 September 2026.

TelegramBot can reach the domain successfully:

23/Sep/2026 00:32:31 GET /calculator -> HTTP 301
23/Sep/2026 00:32:32 GET /calculator/ -> HTTP 200

User-Agent: TelegramBot/1.0 like Linux

However, newly shared URLs do not generate link previews. Telegram shows link preview loading on the first attempt, but no TelegramBot request reaches the origin server.

A previously cached preview for:

https://electro-energo-estet.ru/galery/

was still visible in old @WebpageBot message history. After the page was published/shared again, that old preview disappeared. During this time the page itself returned HTTP 200, but nginx access logs contained no TelegramBot request to /galery/.

@WebpageBot does not resolve the issue. It currently keeps responding with:

Sorry, no links found. Please send me up to 10 links and I will update previews for them.

even when its menu commands are used.

@SpamBot reports that my Telegram account has no restrictions. The same link-preview behavior was reproduced from another Telegram account.

The WordPress site uses server-rendered Yoast Open Graph metadata with matching og:url, canonical URL, title, description and image.

Please investigate possible domain/URL-level negative preview cache, suppression or routing state in Telegram's link preview backend.

Ivan ShalenkoSep 23

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.

Steps to reproduce

Device info

30683 Cards