Link Preview Not Showing? Check og Tags and Clear the Cache

Contents
Sometimes you paste a link into a KakaoTalk chat and only a gray box shows up. Or you swap the image and the old thumbnail keeps coming back. There are only two causes: the share bot couldn't read the page, or it's showing you an old result it already saved.
Your phone isn't the thing building the preview card. The moment you paste a link, Kakao's scraper bot visits that URL itself, reads the Open Graph (og) tags inside the <head> at the top of the HTML, and draws the card from them. So "it looks fine in my browser" proves nothing.
Summary ① The card is drawn from three values:
og:title,og:description, andog:image. If the image area is blank, the usual cause is a missingog:imageor a URL that won't load. ② Share bots don't run JavaScript. If the tags aren't in View Page Source, the bot can't see them. ③ If you fixed the tags but the old card still shows, that's the cache. You have to clear the cache for that URL in Kakao's debugger before it changes.
The card is built from what a bot reads
Open Graph is a spec that lets a page declare "this is my title, and this is my lead image." The required properties defined by the spec document (ogp.me) are og:title, og:type, og:image, and og:url.
Add og:description and you have the five values that actually get used on the card. The KakaoTalk card lays them out in this order: image, title, description, domain.
The important part is that the bot reads these values only from the first HTML it receives. Anything behind a login, or anything JavaScript fills in later, is invisible to the bot.
When no card shows at all: a no-tools checklist
With nothing but a browser, you can check three things in order and narrow the cause down almost every time.
1. Search for og: in View Page Source
Open the page in Chrome on a desktop, right-click, and choose View Page Source (Ctrl+U on Windows, Cmd+Option+U on Mac). Then hit Ctrl+F and search for og:.
You want View Page Source, not Inspect (DevTools). The Inspect panel shows you the page after JavaScript has run; View Page Source shows you the raw HTML the bot receives. If the tags are in Inspect but not in View Page Source, that's exactly why your card isn't showing.
If you have a terminal, you can do the same check in one line.
curl -s https://example.com/page | grep 'og:'
2. Paste the og:image URL into a new tab
Copy the URL in og:image and paste it into a new tab. If the image doesn't open there, that spot will be blank on the card too.
It's safer to write image URLs as a full address starting with https. A relative path like /img/card.png may not resolve depending on who's reading it.
Check the size too. Per Facebook's sharing documentation, the minimum allowed is 200×200 pixels; for a large card, 1200×630 pixels or bigger is recommended, at an aspect ratio close to 1.91:1, with a file no larger than 8MB.
3. Open it in an incognito window
Check whether the page loads when you're logged out. If a page requires a login or a membership tier, the bot hits the same wall and can't build a card.
Check it with our tool. If repeating those three steps every time is a hassle, just enter the URL and the same checks run at once. Our server fetches the page for you, reads the og tags, and renders them as a KakaoTalk-style card.
No signup or install. Paste a URL and our server fetches the page for you, reads its og tags, and shows them in a chat-style link card.

Below the card, the values for og:title, og:description, og:image, og:site_name, og:type, twitter:card, twitter:title, twitter:image, and canonical are listed as-is, and empty items show as —.
If any of the first three are missing, the tool calls them out separately as Missing tags. If the page loads but has neither og tags nor a <title>, it tells you "Cards won't be created when this is shared."
One thing to know: even if og:image is written as a relative path, the tool converts it to a full address for display. To confirm whether the original tag uses a relative path, you'll need View Page Source as described above.
When the old image shows: it's the cache
If you fixed the tags and shipped the change, but KakaoTalk is the only place still showing the old card, you're looking at the cache, not the tags. KakaoTalk stores what its scraper bot read, per URL.
So to see the new card, you have to clear that cache. On Kakao's developer site, open the Share Debugger, enter the URL, and clear the cache; from the next share onward, the new tags apply. This tool requires a Kakao account login.
If you just need a quick check, you can also tack something like ?v=2 onto the end of the URL. The bot treats it as a different address and reads it fresh. Just don't keep using that URL for actual sharing, since it splits your stats. Use it for temporary checks only.
Common snags
| Symptom | Common cause |
|---|---|
| Title and description show, but the image is a blank gray box | Missing og:image, or that URL won't load |
| No card at all | The page couldn't be fetched because of a login requirement or bot blocking |
| No tags in View Page Source | The tags are being injected by JavaScript only |
| Fixed it, but the old card shows | Share bot cache |
| The preview tool and the real KakaoTalk card differ | The tool shows current tags; KakaoTalk shows the cached values |
Sometimes the preview tool will tell you the page was "blocked." That's not a problem with your tags; it means the site blocks requests coming from data centers. YouTube and Google pages are typical examples, and since Kakao's and Facebook's bots connect through different routes, the real card can still be built just fine.
Naver Blog is a special case too. The desktop URL (blog.naver.com) is a frame layout, so the blog service's own information gets read instead of the post's actual tags. In that case the tool switches to the mobile URL (m.blog.naver.com) to check, and tells you on screen that it did.
The short version
- The card is built by Kakao's scraper bot visiting the page itself and reading the og tags in the
<head>. What you see in your own browser doesn't count. - The spec's required properties are
og:title,og:type,og:image, andog:url, and what really shapes the card is those values plusog:description. - The order to check things: ① search for
og:in View Page Source, ② open theog:imageURL in a new tab, ③ confirm in an incognito window that the page loads without a login. - For
og:image, use a full URL, and stay safe with 1200×630 pixels or larger, a 1.91:1 ratio, and 8MB or less. - If the tags are fine but you see an old card, it's the cache. Clear that URL's cache in Kakao's Share Debugger.
No signup or install. Paste a URL and our server fetches the page for you, reads its og tags, and shows them in a chat-style link card.
Frequently Asked Questions
I fixed the tags, but KakaoTalk still shows the old image.
KakaoTalk stores the results its scraper bot read for each URL. No matter how many times you refresh the page, the card in the chat comes from that stored value, so it won't change. You have to clear the cache for that address in the sharing debugger on the Kakao Developers site before the next share will build a new card.
What pixel size should I make og:image?
Based on Facebook's sharing docs, the minimum allowed size is 200×200 pixels, and 1200×630 pixels or larger is recommended for a large image card. Keep the ratio close to 1.91:1 and the file size under 8MB. These specs are effectively the common standard across many services.
Some links show a card and some don't. What's the difference?
It comes down to whether the bot could read the og tags at that address. Pages that require a login, pages that block bot access, and pages that only add tags with JavaScript give the bot nothing to read, so no card gets built. In most cases, checking whether you can see og: in the page source tells you which one it is.
It looks fine in a preview tool, but the actual KakaoTalk card is different.
Because you're looking at two different points in time. A preview tool reads and shows the tags on the page right now, while KakaoTalk shows the value the bot read earlier. If the two differ, the tags are already fixed and only the cache is left over, so clearing the cache will bring them in line.
This article was adapted from our Korean original. Read the Korean original