Fetches a page from our server and shows how its link will look when shared on WhatsApp, LinkedIn, Facebook, X, Slack, Discord and iMessage, with the Open Graph and Twitter Card tags it found and what is missing. For founders and marketers who share links to their own pages.
How to use it
Enter the address of the page you will share. You can leave out https://.
- Type or paste the address of the page and press Run check.
- Look at the seven link cards to see the title, description and picture each platform would draw.
- Read the findings, starting with the critical ones, and follow the fix of each.
- Change the tags on your page, publish it, then run the check again.
How Reavlo tests this
This tool runs on our server, because a browser cannot read another site's page. Nothing about the request is stored or logged: not the address, not the page.
Fetching. One request to the address, with up to 3 redirects, a size cap and a time limit. Addresses that point to private or internal networks are refused before any connection is made, and the connection goes only to the address that was checked. The chain of redirects is shown.
Reading. The page is parsed once, as a browser parses HTML, so broken markup is still read. The tool reads the Open Graph tags (og:*) and the Twitter Card tags (twitter:*), following the Open Graph protocol. A card takes its title, description and picture from the Open Graph tag, then the Twitter tag, then the page itself.
Checks. The page must answer without an error, hold readable HTML, and carry og:title, og:description and og:image. The picture address should be a full address and must answer. When the page declares the picture's size with og:image:width and og:image:height, it is compared with the 200 by 200 pixel minimum Facebook documents, and 1200 by 630 is the size most platforms recommend. A missing og:url, picture description or twitter:card is reported as information.
The picture. The tool asks the picture's address and reports whether it answered. It does not download or measure the picture, and the picture is never loaded in your browser or served from our site, so each card shows a placeholder with what we know about it.
Limits. The cards are schematic approximations, not copies of any platform's interface. Platforms cache a link for days, use their own crawlers (which a site may treat differently from ours) and may rewrite or hide a card. A page that builds its tags with JavaScript shows no tags here, as it shows none to most platforms' crawlers. Pages behind a login cannot be read.
Questions
Is the address I enter stored?
No. The address goes to our server only to fetch the page, and neither it nor the page is stored or written to a log. Analytics records only that the tool ran, never the address.
Why does my link show no picture on some platforms?
The most common cause is a missing or unreachable og:image, or a relative address. The findings name which one it is. Platforms also keep a copy of a link for some time, so a fixed page may need to be refreshed in each platform's own sharing debugger.
What size should the share image be?
Platforms recommend about 1200 by 630 pixels. Facebook documents 200 by 200 pixels as the minimum for a link image; below it the card falls back to a small thumbnail.
Can I check a page that is not public yet?
No. The request comes from our server, so the page must be reachable from the public internet. Addresses on private networks, such as localhost, are refused on purpose.
Is the preview exactly what the platform will show?
It is an approximation. Each card is a simplified drawing of how the platform lays out a link, and a platform may change its layout or rewrite the text.