Why it happens

Telegram caches preview data on its servers with no documented expiration. Updated OG tags don’t matter until you manually trigger a refresh, and Telegram may hold onto stale data indefinitely.

Fix with @WebpageBot

1. Make sure your updated tags are live and visible in the HTML source (not just client-rendered).
2. Open @WebpageBot in Telegram.
3. Send /start if it’s your first time.
4. Paste the URL you want to refresh.
5. Wait for confirmation, then share the URL in a chat to verify.

You can submit up to 10 URLs at a time.

Existing messages won’t update

Already-sent messages keep their original preview permanently. @WebpageBot only affects new shares. If you need to correct something critical (a price, an event date), delete the original message and re-share after refreshing.

The noindex memory problem

If your page ever served noindex, even briefly, Telegram may be suppressing the preview entirely. Removing the directive isn’t enough; you must also re-crawl through @WebpageBot.

Prevention

• Finalize tags before the URL is first shared, since the first crawl sets the cached baseline
• Send URLs to @WebpageBot before sharing in group chats or channels
• When updating images, change the og:image URL path (not just the file at the same path), since Telegram is more likely to recognize it as new