LINE Open Graph Preview

LINE draws a shared link as a chat-bubble card: the og:image full-width on top, a bold og:title underneath, one line of muted og:description, and the bare domain as a footer. The bubble is rounded with a subtle border, so it reads as part of the conversation rather than as an embedded post.

LINE reads only og:title, og:description, and og:image — every other Open Graph property is ignored, and so are the twitter:* tags. A card whose meaning lives in another tag renders here as a picture plus a headline, or a headline alone without og:image.

When a chat shows a bare URL instead of a card, the fetch failed rather than a tag being absent. LINE's preview fetcher, PagePoker (line-poker in your logs), requests the page server-side without executing JavaScript and needs a 200 OK HTML response with the tags in the initial markup. A login wall, an internal host, a firewall rule against its user agent, or client-rendered tags leave only the link text.

The scan above requests the page with the same user agent, so a check that passes here is a fetch that works in a LINE chat. Linespider, the crawler named in LINE's search docs, is a different bot and does not build chat previews.

Set og:title, og:description, and og:image in the page head. Use an HTTPS image at 1200×630 when possible, keep it under 5 MB, and serve it without an avoidable redirect.

Keep the title short and the description to a single line — that is all the bubble shows before it truncates. The scanner fetches both the page and its image with PagePoker's user agent, so it can show whether the tags are reachable before you share the link.