Find the missing tag behind a WhatsApp or Slack link with no picture
Runs in your browser. Nothing you type is sent anywhere. Updated on 24 Oct 2026.A link that pastes into WhatsApp or Slack as bare blue text is nearly always one tag away from working. Paste the page HTML and this lists what each chat app looks for, in the order it looks, and marks the first thing it cannot find. The two usual culprits are a relative og:image path and tags added by JavaScript that the scraper never runs.
The page opens on the WhatsApp card.
Paste the page source into Page HTML; tags added later by JavaScript are not in it, and chat apps do not see them either.
Read the Image line: no tag supplies this means the chat app has no picture to show.
Press Slack to check the same page for a Slack preview.
Fix the first tag under Missing, often a relative og:image path, and paste the page again to confirm.
This Open Graph preview reads the meta tags in a page you paste and draws the share card that Facebook, LinkedIn, X, WhatsApp and Slack would each build from them. Every network is shown with its own fallback order, so you can see which tag actually supplied the headline, the second line and the picture.
One thing it will not do is fetch a page for you. There is no server behind this site and the browser is not allowed to request other people's pages, so any tool here claiming to read a live URL would be lying about where the work happens. Open the page, press Ctrl+U to view source, and paste that in. Pasting only the head, or even a few meta tags, is enough.
The checks cover the mistakes that actually break cards: a relative og:image path, a missing og:url, a twitter:card value that is not a card type, repeated tags where the scraper silently keeps the first, and tags added by client-side JavaScript that a scraper never executes. Each one says what the network does instead.
The rest of the article, and all 6 questions about Open Graph Preview, are on the Open Graph Preview page.
Nine times out of ten the og:image value is a relative path like /card.png. Networks fetch the image from their own servers, so it must be a full https:// address. The other common causes are an image behind a login and a file larger than about 5 MB.
X retired the public Card Validator in 2022. Checking a card now means posting the link, or reading the tags yourself. This page reads them the way X does: twitter: tags first, then og: tags, with the small summary card as the default.
Facebook caches a card the first time a link is shared and does not re-read it on its own. After changing tags, run the URL through Facebook's Sharing Debugger and choose Scrape Again. LinkedIn's Post Inspector does the same job.
Usually not. Facebook, WhatsApp and Slack scrapers read the HTML the server sends and do not run your JavaScript. Tags injected by a client-side framework are invisible to them, so render them on the server or pre-render the page.
Still stuck? Ask about Open Graph Preview and anybody who knows can answer. No account needed.
Same job, other tools: Readability Checker – Flesch reading ease and grade level, with what to change · HTTP 404 Not Found – What a 404 means, when to send it, and when 410 or 403 is the better answer.
On the related tools: Cron to systemd Timer Converter – Turn a crontab line into a systemd OnCalendar= value with ready .timer and .service units.
In the collection SEO Tools.