Bugs and Suggestions

Same issue here. Link preview does not appear for my site: https://vezumba.ru/

I've verified everything on my side:
- OpenGraph meta tags are correctly set (og:title, og:description, og:image) and validated with third-party OG debuggers.
- curl with User-Agent "TelegramBot (like TwitterBot)" returns HTTP 200 with correct HTML and meta tags.
- Server is HTTPS only, no redirects, no robots.txt restrictions for TelegramBot.
- No firewall/WAF rules blocking TelegramBot's IP ranges (149.154.160.0/20, 91.108.4.0/22).
- Checked nginx access/error logs — there are zero requests from TelegramBot at all. The crawler never reaches the server.
- Preview works correctly when the same link is shared in WhatsApp and other messengers.
- Tried @WebpageBot to force a re-crawl — no effect, still no preview.

This strongly suggests the issue is not on the website side but with Telegram's crawler itself not attempting to fetch the page. Would appreciate any insight into why the crawler isn't sending requests at all.

Digital AssistantAug 25

Title: Telegram does not request albumflow.ru pages for link previews
The same issue affects albumflow.ru.
When a link is pasted into Telegram Desktop, “Generating link preview…” appears for several seconds and then disappears. The message is sent without a title, description, or image.
Test URL:
https://www.albumflow.ru/telegram-preview-test-250826-1.html?tgwww=250826-1
Device:
Windows 11, Telegram Desktop
Server-side evidence:
TelegramBot previously reached the website successfully and received HTTP 200:
89.221.230.117 - [25/Aug/2026:19:40:52 +0000] "GET / HTTP/1.1" 200 8762 "-" "Mozilla/5.0 (compatible; TelegramBot/1.0 like Linux)"
However, after sending the new unique static test URL, no request from TelegramBot appeared in the Nginx access log at all.
The test page:
returns HTTP 200;
is a minimal static HTML file without JavaScript;
contains valid Open Graph title, description and image tags near the beginning of <head>;
uses a publicly accessible 1200×630 PNG image;
requires no authentication, cookies or redirects.
The same Open Graph metadata generates a correct preview in other messengers, including MAX.
Both albumflow.ru and www.albumflow.ru were tested. Telegram appears to reject the domain or use an internal negative domain cache before making any HTTP request to the server.
Please review and clear any domain-level link-preview suppression or negative cache affecting albumflow.ru.

Artem B.Aug 30

I can reproduce the same Telegram link preview issue on two unrelated domains:

https://stroymaks.com/ hosted by REG.RU

https://www.green-garden.ru/ hosted by Timeweb

Both sites have valid Open Graph metadata and their previews are rendered correctly by external OG checkers. Other messengers also process the metadata correctly.

For stroymaks.com, we performed additional diagnostics:

HTML returns HTTP 200
og:title, og:description and og:image are present
OG image returns HTTP 200 / image/jpeg
requests using User-Agent: TelegramBot (like TwitterBot) work correctly
unique query parameters do not help
IPv6 was temporarily disabled and the issue remained

REG.RU checked their logs during a controlled test and confirmed that no request from Telegram reached their web server

green-garden.ru shows the same behavior despite being hosted by a completely different provider (Timeweb).

I have also previously tested Telegram connectivity from a Timeweb VPS successfully, so this does not appear to be a general Telegram block on the Timeweb network.

@WebpageBot reports that previews were updated successfully, but Telegram clients still do not generate the actual preview.

This looks like an issue in Telegram's link preview backend before the HTTP request reaches the origin server, possibly domain-level preview suppression or an internal negative cache.

Could you please investigate these domains?

stroymaks.com

green-garden.ru

Евгений СабировSep 1

Telegram preview did not work for:
https://partyathlon.ru/t/1/archive

The page returned HTTP 200 with valid server-rendered Open Graph metadata. The original og:image was a public PNG, 1731×909 and 1,055,831 bytes. Telegram successfully used this same image for the root URL, but not for the archive URL. @WebpageBot reported a successful update, although no effective re-crawl occurred.

We replaced only the preview image with a new URL: JPEG, 1200×630, 84,346 bytes. Telegram then requested the archive page, its canonical URL, and the new image. After that, the exact archive URL started showing a preview.

It is unclear whether the deciding factor was file size, format, the new image URL, or cache invalidation. Telegram’s official documentation does not appear to specify limits for Open Graph preview images. Could these requirements and cache behavior be documented?

Artem RiekhtinSep 12

Same issue with royalauto.pro after changing hosting.
Telegram shows “Generating link preview…”, then only a plain URL. @WebpageBot reports success, but nothing changes. WhatsApp and imo show correct previews.
Static test:
https://royalauto.pro/assets/social/preview-check-20260912.htm
The page returns HTTP 200 with OG tags in the head, without JavaScript or authentication. Its JPEG returns 200. During controlled tests, no new HTTP request to the test page appeared in Nginx logs; only our marked probes were present.
robots.txt explicitly allows TelegramBot/WebpageBot. Responses have noindex,nofollow,noarchive.
Please check crawler fetch errors, cached DNS/failures or domain-level preview suppression for royalauto.pro. The exact cause remains unknown.

Arseniy SavinSep 15

Same symptom on www.effective.dev (static site, Yandex Object Storage + CDN). Two facts that narrow it to the host, not the page:

1. The crawler fetches fine and builds nothing. CDN access log while a fresh link was posted:
TelegramBot/1.0, 89.221.230.201 (AS47764) - GET / - 200 - 3525 B gzip - 0.068 s. No og:image request followed, no preview appeared

2. Same bytes on another hostname work:
https://www.effective.dev/ru/it-swat/ - no preview
http://effective-dev-stage.website.yandexcloud.net/ru/it-swat/ - full card
Identical build, identical OG tags. Hostname is the only difference

3. Assets from the affected host are dropped too: with the document on the working host, og:image on www.effective.dev gives a card with no image; the same file on
storage.yandexcloud.net renders. Both 200, image/png, 1200x630, 699297 B

Also: @WebpageBot replies "Link previews was updated successfully" for a domain that does not exist (dig www.effecitve.dev → NXDOMAIN), so its success message proves nothing. The
apex 301 -> www behaves the same

Our side is clean: 200 for TelegramBot/TwitterBot/facebookexternalhit, robots.txt allows /, no X-Robots-Tag, valid TLS, no CDN ACL or geo rules

Looks like a blocklist or negative cache entry for effective.dev / www.effective.dev in the preview backend. Logs and timestamps available on request

Matvey AvgulSep 15

Reproduced on MacOS 12.10.282987 AppStore: posting https://www.effective.dev/ in a private chat and in a group shows a plain URL, no preview.

EgorSep 18

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.

Show next 3 comments

Steps to reproduce

Device info

30683 Cards