See your link on Google, WhatsApp, X and LinkedIn
Paste a page address and see how it is likely to look when it is shared or searched, then fix the tags that let it down. Free to use with a Webknown account.
Checks on the example page
0 must fix0 worth fixing1 good to know8 passed
Good to know
Note: No WebSite structured data in the <head>
Google's strongest site-name signal is WebSite structured data with a "name" on your home page. We only read the <head>, so if yours is in the body Google can still use it. Here we show og:site_name instead.
Official ruleGoogle
Passed checks (8)
Passed: og:url is this page's full address
It's absolute, on the same site and agrees with the canonical link.
Official ruleWhatsAppLinkedIn
Passed: og:title, og:description and og:image are all set
These are the tags WhatsApp and LinkedIn build the preview from.
Official ruleWhatsAppLinkedIn
Passed: twitter:card is summary_large_image
X will use its large image card.
Official ruleX
Passed: og:image looks right (PNG, 1200 × 630, 50 KB)
A full https:// address that loads, in a supported format, the right shape and a sensible size.
Official ruleWhatsAppXLinkedIn
Passed: Title fits on desktop
About 490 px of roughly 600 px.
EstimateGoogle
Passed: Meta description is a good length
136 characters.
EstimateGoogle
Passed: Canonical link is set
A full address on the same site.
Common behaviourGoogle
Passed: Favicon link found
Google reads the favicon from your home page, so make sure the home page has it too.
Official ruleGoogle
Official rule means the platform documents it. Common behaviour and Estimate mean it isn’t documented, so we never mark those as a hard fail.
Checking your session…
Example
A real check of our own homepage, www.webknown.in
Taken from the live page on 26 September 2026. Sign in to check your own page.
Google search
Webknown — Digital Agency in India | Web Development
Fast, SEO-optimized websites and data-driven marketing for businesses across India, from Bokaro Steel City, Jharkhand. Book a free call.
Desktop title width: about 490 px of roughly 600 px.
- Site name from og:site_name, as we found no WebSite structured data in the <head>. Google prefers WebSite structured data on your home page, and can read it from the body too.
- Favicon from this page. Google uses the one on your home page.
Estimate. Google decides the final title and snippet and may rewrite them, and it publishes no pixel limits. The desktop cut-off here assumes a result column about 600 px wide. On mobile the title wraps instead of being cut.
Preview wrong? How to refresh Google
Google re-reads pages on its own schedule: several days to several weeks.
- Fix the <title>, meta description or canonical on the page.
- In Google Search Console, open URL Inspection for the page and press Request indexing.
- For the favicon or site name, inspect your HOME page instead, since that's where Google reads them.
- There's no guaranteed turnaround. Google decides the final title and snippet and may still rewrite them.
Digital Agency in India | Web Development
Fast, SEO-optimized websites and marketing for businesses across India.
webknown.in
https://www.webknown.in/
- Large preview: the image meets WhatsApp's rules.
WhatsApp documents the tags and image rules but not the exact layout. The small-preview layout and the fallback to your <title> are common behaviour, not documented. The rules are the same on Android and iPhone; only the look differs.
Preview wrong? How to refresh WhatsApp
WhatsApp has no refresh tool, and messages already sent never change.
- Fix the og: tags on the page.
- If the picture changed, give it a new file name too (for example og-v2.jpg), because apps cache images by address.
- Share a slightly different link, such as your address with ?v=2 on the end, so WhatsApp fetches it again. This is common practice, not an official feature.
- Paste the link, wait about 10 seconds for the preview to appear, and check it before you press send.
X
Have a look at this page.
From webknown.in
- Large image card, with the title over the picture. X doesn't show the description on this card.
Unverified layout. X removed its card documentation; this follows archived docs and press reports (headline over the image, no description on the large card). X also doesn't document how it crops images. We don't read your robots.txt: if it blocks Twitterbot, X shows no card at all. To be sure, paste your link into a new post without posting it.
Preview wrong? How to refresh X
X caches a card for about 7 days and has no instant refresh.
- Fix the twitter: or og: tags.
- Give a changed image a new address, for example og.jpg?v=2, so X treats it as a new image.
- Share a unique version of the link (add ?v=2) to get a fresh card straight away.
- Check it by pasting the link into a new post and looking at the card before you post. X's old Card Validator no longer shows previews.
Have a look at this page.
Digital Agency in India | Web Development
webknown.in
- Large card: the image across the top, then the title and domain.
Unverified layout. LinkedIn documents the tags and image sizes but not the feed card's look. It usually shows the title and domain under the image, without the description.
Preview wrong? How to refresh LinkedIn
LinkedIn Post Inspector refreshes the preview, but only for new posts.
- Fix the og: tags, especially og:url.
- Paste your link into LinkedIn Post Inspector (linkedin.com/post-inspector) to make LinkedIn fetch it again.
- Then create a new post. Posts you already published keep their old preview.
Want your previews fixed for you?
Webknown sets up titles, descriptions, share images and structured data so every page looks right on Google, WhatsApp, X and LinkedIn. Leave your details for a free, no-obligation chat. The checker stays free either way.
Questions people ask
Is this exactly what Google, WhatsApp, X and LinkedIn will show?
It is as close as we can make it, but no platform publishes its exact layout. The tags, image rules and size limits come from each platform's own documentation where it exists, and every check says whether it is an official rule or common behaviour. Google can rewrite titles and snippets whenever it thinks they fit a search better, and X removed its card documentation, so treat those two previews as the most likely result rather than a promise. Our checker also fetches your page from our server under its own name, so a site that shows the platforms' crawlers different tags, or blocks our checker while letting them in, can look different to them. To be certain, paste the link into a draft message or post before you share it.
I fixed my tags, but WhatsApp or LinkedIn still shows the old preview. Why?
Because they cache it. LinkedIn refreshes when you paste the link into LinkedIn Post Inspector, but only for new posts. WhatsApp has no refresh tool, and messages already sent never change: share the link with something like ?v=2 on the end so it is fetched again, and give a changed image a new file name. X keeps a card for about seven days, so share a new version of the link the same way. Google re-reads pages on its own schedule; Request indexing in Search Console can speed that up. Each preview on this page has these steps under "Preview wrong?".
What size should my share image be?
A 1200 × 630 pixel JPEG or PNG under 300 KB, linked with a full https:// address in og:image. That meets every documented rule: WhatsApp wants under 600 KB, at least 300 px wide and no wider than 4:1; X wants at least 300 × 157 and under 5 MB, and doesn't support SVG; LinkedIn's minimum is 1200 × 627 and under 5 MB. Keep text and logos away from the edges and the bottom, which can be cropped or covered by the title on X.
Why does my WhatsApp preview show a tiny image or none at all?
WhatsApp only shows the large picture when og:image is a full web address, the file is under 600 KB, at least 300 px wide and no wider than 4:1. If any of those fails it may fall back to a small thumbnail or no picture. It also needs the page's <head> within the first 300 KB of the HTML. This tool measures the real file, not what the tags claim, and tells you which rule failed.
Why do I need an account to check a page?
Each check makes our server fetch a page from the internet. Limiting the checker to signed-in accounts, at about five checks a minute each, stops it being used to hammer other websites or run up our costs. The account is free, and everything else on this page, including the example, is readable without one.
What happens to the address I check?
Our server fetches that page's HTML once, reads the tags in its <head> and measures the share image, then sends the result back to your browser. We don't keep a copy of the page or save the result, and the checker's own logs note only the website's domain, not the full address. The preview images you see are loaded by your browser straight from the website that hosts them. The optional contact form sends the checked page's address only if you submit it, and never the part after a ? or #.
My tags are added by JavaScript. Will the preview work?
Probably not. WhatsApp, X and LinkedIn read the HTML your server sends and don't run your JavaScript, so tags added in the browser are invisible to them. This checker reads raw HTML too, so if it finds no tags, the apps probably won't either. The exception is a site that serves those apps' crawlers a different, pre-rendered page (services like prerender.io do this), which our checker doesn't get. Render the tags on the server, which frameworks like Next.js do for you.