See your link the way
Paste any URL. Weblytic reads its Open Graph and meta tags, then renders the exact share card each platform will build — plus a list of everything that is missing.
Open Graph and meta tag previewer
Google ignores Open Graph tags. It builds this snippet from your
<title> and meta description.
Facebook, WhatsApp, Messenger and Slack all read the same Open Graph tags, so this card is a good proxy for all four.
X uses twitter:* tags first and falls back to og:*.
A card set to summary_large_image shows the wide image above.
LinkedIn shows no description at all — the title and the image do all the work, so keep the title under about 70 characters.
Tag health check
All meta tags found
0 tags| Tag | Value | Length |
|---|
Copy-ready meta tags
What are Open Graph tags, and why should you care?
Every time somebody pastes your link into Facebook, WhatsApp, Slack, LinkedIn or X,
that platform sends a robot to your page. The robot does not read your article. It
reads a handful of invisible lines in the <head> of your HTML and
uses them to build the little preview box everyone sees in the feed. Those lines are
Open Graph tags.
The protocol was published by Facebook in 2010 so that any web page could describe itself to a social network in a predictable way. It caught on fast. Today LinkedIn, Pinterest, WhatsApp, Telegram, Discord, Slack, Microsoft Teams and dozens of other products all read the same tags. Write them once and every one of those platforms gets the message.
An Open Graph tag is a normal meta tag with a property attribute:
<meta property="og:title" content="How to Speed Up a Slow WordPress Site">
<meta property="og:description" content="Nine fixes that cut our load time from 4.2s to 0.9s, in order of impact.">
<meta property="og:image" content="https://example.com/images/wp-speed-cover.jpg">
<meta property="og:url" content="https://example.com/speed-up-wordpress/">
<meta property="og:type" content="article">That is the whole idea. Five lines decide whether your link shows up as a bold headline with a big picture, or as a bare blue URL that nobody clicks.
The part people get wrong: Google does not use Open Graph
tags for search results. It uses your <title> and
meta description. Social platforms do the opposite — they prefer
og:* and only fall back to the plain tags. You need both sets, which is
exactly why this tool shows you a Google snippet and three social cards side by side.
The cost of getting it wrong
A link posted without an og:image renders as a thin grey strip. A link
with a broken image URL renders as a thin grey strip with a broken icon. A link whose
og:title was never set inherits whatever your CMS shoved into the title
tag — often something like "Page not found | My Site | My Site". None of that
is fatal, but all of it costs clicks, and the fix takes about ninety seconds.
If you run a blog, an affiliate site, a store or a portfolio, the share card is the ad. It is the only thing a stranger sees before deciding whether you are worth their attention. Treat it with the same care you would give a thumbnail or a subject line.
Check any page in four steps
No account, no browser extension, no API key. Paste and go.
-
Paste the URL
Any public page works — your homepage, a single blog post, a product page, even a competitor's article you want to reverse-engineer. Weblytic adds
https://for you if you leave it off. -
We fetch the page server-side
A small PHP script on our server downloads the raw HTML. This is necessary because a browser is not allowed to read another website's HTML directly — the browser's same-origin policy blocks it. Nothing about the page is stored or logged.
-
Read the cards and the warnings
Switch between the Google, Facebook, X and LinkedIn tabs to see the four different ways the same page gets displayed. Below them you get a health check that flags missing tags, descriptions that are too long, and images that will not render.
-
Copy the fixed tags into your site
The Copy-ready meta tags block builds a corrected version of your tags from what we found. Paste it into your theme's
<head>, or into Yoast, Rank Math, or whatever your CMS uses, then run the check again.
Every tag this tool checks
What each one does, and how much it actually matters in practice.
| Tag | Used by | What it does | Priority |
|---|---|---|---|
| title | Google, all platforms (fallback) | The blue headline in search results and the browser tab. Aim for 50–60 characters. | Critical |
| meta description | Google, Bing | The grey paragraph under the headline. Google may rewrite it, but yours usually wins. 150–160 characters. | Critical |
| og:title | Facebook, LinkedIn, WhatsApp, Slack | The bold headline on the share card. Can differ from your SEO title — make this one punchier. | Critical |
| og:description | Facebook, WhatsApp, Slack | One or two lines under the card title. LinkedIn ignores it entirely. | High |
| og:image | Every social platform | The picture. This single tag has the largest effect on click-through rate of anything on this list. | Critical |
| og:image:alt | Accessibility tools | Describes the share image for screen readers. Cheap to add, easy to forget. | Nice to have |
| og:url | Facebook, LinkedIn | The canonical address for the page. Keeps likes and share counts pooled on one URL instead of split across tracking variants. | High |
| og:type | Facebook, Pinterest | website for normal pages, article for blog posts, product for shop items. | High |
| og:site_name | Facebook, LinkedIn | Your brand name, shown alongside the card on some surfaces. | Nice to have |
| twitter:card | X | summary_large_image gives the big wide image. summary gives a small square thumbnail. | High |
| twitter:title | X | Overrides og:title on X only. Useful when you want shorter copy there. | Nice to have |
| twitter:description | X | Overrides og:description on X. Keep it under 200 characters. | Nice to have |
| twitter:image | X | A different crop for X. Skip it and X uses og:image, which is usually fine. | Nice to have |
| link rel="canonical" | Google, Bing | Tells search engines which URL is the real one when the same content lives at several addresses. | High |
Open Graph image sizes that actually work
One image at 1200 × 630 covers almost everything. Here is the detail if you want to be precise.
Facebook & WhatsApp
1200 × 630 px, ratio 1.91:1, under 8 MB. Anything smaller than 600 × 315 gets downgraded to the small square card. Keep text away from the outer 10% — feed crops are unforgiving on mobile.
X / Twitter
1200 × 628 px for summary_large_image, under 5 MB. For the small
summary card use a square, at least 144 × 144. X does not render
animated GIFs in link cards.
1200 × 627 px, under 5 MB. LinkedIn shows no description, so any message you need read should live in the title or be baked into the image itself.
Four rules that prevent most broken images
- Use an absolute HTTPS URL.
/images/cover.jpgwill not work. It has to behttps://yoursite.com/images/cover.jpg. - Do not put it behind a login or a hotlink block. The scraper is an anonymous robot. If it cannot fetch the file, you get no image.
- Declare the dimensions. Adding
og:image:widthandog:image:heightlets the platform reserve space on the first scrape instead of showing nothing while it downloads. - JPG or PNG. WebP and AVIF support is still patchy across scrapers. Use a normal format for the share image even if the rest of your site is modern.
Writing tags people actually click
Your social title is not your SEO title
An SEO title is written for a search engine and a person who is already looking for something. A social title is written for somebody scrolling past with no intent at all. The first should contain your keyword near the front. The second should contain a reason to stop. There is no rule that says they must match, and on most pages they should not.
Compare "WordPress Speed Optimization Guide 2026 | MySite" with
"We cut 3.3 seconds off our load time. Here is every change, ranked." The
first belongs in <title>. The second belongs in
og:title.
Design the image for a phone
Most shares are opened on a screen where your 1200 px image renders about 340 px wide. Body copy at that size is a grey smudge. Use three or four large words at most, high contrast, and put your face or your product where the eye lands first. If you already design YouTube thumbnails, the same instincts apply — because the job is identical.
Set og:url and keep it clean
When somebody shares ?utm_source=newsletter and somebody else shares the
plain URL, Facebook treats them as two different pages and splits your engagement
between them. Setting og:url to the canonical address merges the two.
Remember that platforms cache aggressively
The first time a URL is shared, the platform scrapes it and stores the result — often for days or weeks. Fixing your tags afterwards changes nothing until you force a re-scrape. Facebook's Sharing Debugger has a Scrape Again button, X's Card Validator refreshes on request, and LinkedIn has a Post Inspector. Use this tool to confirm the tags are right, then use the platform tool to clear the cache.
Check pages, not just the homepage
Most CMS themes set decent tags on the front page and then leave archives, tag pages, category pages and older posts with defaults nobody reviewed. Those are usually the pages being shared. Spot-check five or six of your most-linked URLs, not just the one you remember configuring.
Frequently asked questions
The things people ask most often about Open Graph tags and this tool.
Is this tool really free?
Yes. There is no account, no trial, no usage cap you will realistically hit, and no credit card. The site is supported by advertising. If you want to run it on your own server, the whole thing is plain HTML, CSS, JavaScript and a single PHP file — no framework, no build step, no database.
Do you store the URLs I check?
No. The URL is passed to the fetch script, the page is downloaded, the tags are sent back to your browser, and that is the end of it. Nothing is written to a database and the fetched HTML is not kept. The only thing our server keeps is a short-lived counter used to stop one address from hammering the tool.
Why did my URL fail to load?
The usual reasons, in order of how often they happen:
- The page sits behind a login, a paywall, or a members-only area.
- The site uses a bot-protection layer such as an aggressive Cloudflare rule and blocks server-side requests.
- The URL is on a local or private network, which the tool deliberately refuses to fetch for security reasons.
- The server took longer than twelve seconds to answer.
If a page loads fine in your browser but fails here, bot protection is almost
always the cause. You can still check the tags by viewing the page source and
searching for og:.
What is the ideal Open Graph image size?
1200 × 630 pixels, a 1.91:1 ratio, saved as JPG or PNG, under 5 MB, served over HTTPS. That single file works on Facebook, LinkedIn, X, WhatsApp, Slack, Discord and Telegram. Only bother with platform-specific crops if you have a reason to.
I fixed my tags but the old preview still shows. Why?
You are seeing a cached scrape. Platforms store the first version they fetch so they do not have to re-download your page every time somebody posts the link. Run the URL through Facebook's Sharing Debugger and press Scrape Again, then do the same in X's Card Validator and LinkedIn's Post Inspector. The new card usually appears within a minute.
Do Open Graph tags help my Google rankings?
Not directly. Google has said repeatedly that og:* tags are not a
ranking factor, and the search snippet is built from your
<title>, your meta description and the page content. The
indirect effect is real though: a link with a strong share card earns more clicks,
more traffic and more natural links, and those things do matter.
Do I need both Open Graph and Twitter Card tags?
Not strictly. X falls back to og:title, og:description
and og:image when the twitter:* versions are missing.
The one tag worth adding on its own is
<meta name="twitter:card" content="summary_large_image">,
because without it X may render the small square card instead of the wide one.
How do I add these tags in WordPress?
If you use Yoast SEO or Rank Math, open any post, scroll to the SEO panel and look
for the social or share tab. You will find fields for the Facebook title,
description and image, plus X equivalents. Fill them in and the plugin writes the
tags for you. Without a plugin, you can add them in your child theme's
functions.php using the wp_head hook, or paste them into
your theme's header template.
Can I check a page that is still on staging?
Only if the staging site is publicly reachable and not password-protected. Private
IP addresses, localhost and internal hostnames are blocked on purpose,
because an open fetch endpoint that reaches private networks is a security hole.
For a local page, view source and check the tags by hand.
Ready to check a page?
It takes about five seconds, and you will almost certainly find one tag worth fixing.
Scroll back to the tool