Why the wrong image appears

LINE reads only og:image. No fallback to twitter:image or anything else. Common causes:

1. og:image points to the wrong URL
2. Cached image from a previous crawl
3. Multiple og:image tags – LINE picks one you didn’t intend
4. Image URL returns an error – LINE shows no image or a stale cached version

Diagnosis steps

1. View page source – check the exact og:image value
2. Load the image URL in a browser
3. Search HTML for duplicate og:image tags
4. Verify the image is publicly accessible over HTTPS

The fix

Correct the og:image tag, then:

1. Use LINE’s cache-clearing tool on the LINE Developers site
2. Share the URL in a new LINE message

No twitter:image fallback

Unlike other platforms, LINE won’t fall back to twitter:image. If og:image is missing, LINE shows no image – even if twitter:image is set.

curl -A "Linespider/1.1" https://yoursite.com/page | grep -i "og:image"

Verify one og:image tag pointing to the correct absolute HTTPS URL.