Open Graph Checker: Fix the Social Preview People Actually See
CodexFuse Team · 2026-11-02T15:44:38.417Z · 9 min read min read
Audit your open graph tags before a bad preview costs you clicks — check titles, images and descriptions for Facebook, X, LinkedIn and WhatsApp.
Open graph tags are the small block of metadata in a page's head section that tells Facebook, LinkedIn, WhatsApp and X what title, description and image to show when someone shares a link. When those tags are missing or wrong, the platform guesses — and the guess is often an old logo, a cropped photo, or a sentence pulled from the middle of the page. An open graph checker audits those tags before your audience ever sees the broken version.
Why a good page can still look broken when shared
Three failures cause most of the damage. The image is the wrong size, so the platform crops out the product or the headline. The title is a generic site name instead of the page's real subject. The description is either missing, so the platform invents one, or so long that it is cut off mid-sentence.
What does an open graph checker actually check?
An open graph checker reads a page's og: tags and Twitter card tags, then reports whether the title, description, image, URL, type and site name are present, correctly formed and within the length and size limits each platform expects, and shows a preview of the resulting social card.
CodexFuse's checker goes a step further than a raw tag dump. It validates title and description length, image size and ratio, and the presence of og:url, og:type and og:site_name, then scores the page against a protocol compliance checklist. You also get previews for Facebook, Twitter/X, LinkedIn and WhatsApp, which is useful because the same tags render differently on each platform.
Check the preview on WhatsApp as well as Facebook. WhatsApp crops aggressively and shows very little text, so a preview that looks fine on a desktop Facebook feed can still fail in a chat thread, which is exactly where small businesses get most of their shares.
A bakery link that lost the sale before anyone clicked
Consider a fictional but typical case. Meher runs a home bakery in Lahore and sells a signature chocolate cake through a single product page. A happy customer shares the link in a family WhatsApp group of about 40 people. That share should have been free advertising. Instead, it worked against her.
The shared preview showed her site's generic logo, not the cake. The title read only "Meher's Kitchen" instead of "Signature Chocolate Cake — Order Online". The description was a fragment from her delivery policy, cut off after "Delivery available on…". Nobody in the group could tell what was being sold, how much it cost, or why they should tap.
Meher ran the page through the Open Graph Checker. The audit flagged four problems in one pass:
- Missing og:image: the page had no social image tag at all, so WhatsApp fell back to the logo.
- Generic og:title: every page on the site shared the same site-name title.
- Over-long description: the og:description ran to 260 characters and was truncated mid-sentence.
- Missing og:type and og:site_name: two small tags that help platforms classify the page correctly.
How to audit a page with CodexFuse's Open Graph Checker
The tool lives at CodexFuse's Open Graph Checker. The walkthrough below follows the live tool's own steps, verified against the page itself.
- Enter the page URL: paste the full URL into the field on the tool page.
- Click Audit Open Graph: the tool runs its checks and produces a score plus a protocol compliance checklist.
- Switch between platforms: pick Facebook, Twitter/X, LinkedIn or WhatsApp to preview how the same tags render on each one.
- Read the tag table: review the extracted Open Graph and Twitter card tags side by side, so you can see exactly which tag is missing or malformed.
- Copy or download the result: copy the head-tag HTML snippet for your developer, or download the audit as a text report to work through the fixes.
| Tag | What it controls | The most common failure |
|---|---|---|
| og:title | The headline on the shared card | Same generic site name on every page |
| og:description | The short text under the headline | Missing, or so long it is cut off mid-sentence |
| og:image | The photo on the card | Wrong ratio, too small, or absent entirely |
| og:url | The canonical link behind the card | Points to the homepage instead of the real page |
| og:type | How the platform classifies the page | Left out, so the card renders as a plain link |
| twitter:card | How X renders the card | Set to summary when a large image was intended |
Run your key pages through an audit, then let CodexFuse's fully managed team fix the tags, the hosting and the follow-through for you — one platform, on credits, with no subscription to manage.
Get Started with CodexFuseWhat the checker will not do for you
Honesty matters here, because the tool page itself states an important limit: the audit is simulated, with checks generated from the entered hostname rather than fetched live from the page. Treat it as a structured checklist and preview guide, not as a live crawl of your server's current HTML.
That has two practical consequences. First, after you fix your tags, confirm them in your page's actual source code or with the platform's own debugger before you declare the job done. Second, the checker cannot fix anything on its own. It tells you what is wrong; the edits still happen in your site's code or content system.
Social platforms cache previews. Fixing your tags does not always refresh an old share instantly. If a corrected page still shows the old card, use the platform's sharing debugger to request a fresh scrape, and test the link in a new chat rather than trusting the old message thread.
The five tags to fix first
If a full audit feels overwhelming, start with this short list. It covers the failures that cost the most clicks.
- One real image per page: use a 1200 × 630 image that shows the subject of that specific page, not your logo.
- A specific title: name the product, article or service on that page, not just your business name.
- A complete short description: aim for roughly 120–160 characters that end cleanly and say what the reader gets.
- A correct og:url: point to the canonical version of the page, including the right https address.
- A matching Twitter card: set twitter:card to summary_large_image when you have a proper image, so X does not shrink it to a thumbnail.
When should you re-check a page?
You should re-check a page whenever its title, image, price or main offer changes, and again after any redesign, migration or change of content system, because all of those can silently drop or overwrite head tags.
A sensible routine is to audit your five most-shared pages once a quarter, and any new landing page before it goes into an ad, an email campaign or a press release. Catching a bad preview before a campaign launches is free. Catching it after thousands of people have already shared the broken version is not.
Pair the fix with the rest of your metadata: a clean JSON-LD schema helps search engines understand the page, and the basics of on-page SEO cover what search engines see, while open graph covers what people see when they share.
If your shared images look wrong for a different reason, read how to strip EXIF and metadata from images before re-uploading them — leftover metadata and oversized files cause their own share of preview problems.
Frequently Asked Questions
What is open graph?
Open graph is a protocol of meta tags, originally created by Facebook, that lets a web page control its title, description, image and type when shared on social platforms. Without these tags, each platform guesses what to display, and the guess is frequently wrong.
Is the CodexFuse Open Graph Checker free?
Yes, the tool page describes it as free and unlimited. You do need to log in to use it, so create a free account first, then audit as many pages as you need.
Why does my page look different on WhatsApp and Facebook?
Each platform renders the same tags with different image crops, text limits and layouts. That is why the checker offers separate previews — a card that passes on Facebook can still be cropped badly on WhatsApp, and only a per-platform preview reveals that.
Does fixing open graph tags improve Google rankings?
Not directly. Open graph tags are for social sharing, not search ranking. They improve rankings indirectly: better previews earn more clicks and shares, which bring more visitors to a page that search engines already value.
Why does an old preview still show after I fixed my tags?
Social platforms cache link previews, sometimes for days. Use the platform's sharing debugger to force a fresh scrape, then test the link in a new post or chat instead of relying on the old shared message.
Can one image work for every page on my site?
Technically yes, but it is a poor choice. A single generic image tells a reader nothing about the specific page they are about to open. Give each important page its own image, and reserve the logo fallback for pages that nobody shares.
Stop letting a bad preview speak for your business
Your website is not the only version of your business people meet. The shared card is often the first one, and right now it may be showing a cropped logo, a generic title and a sentence that ends nowhere. That is a fixable problem, and it starts with a single audit.
Run your homepage and your five most important pages through CodexFuse's Open Graph Checker today, fix the five tags listed above, and re-test before your next campaign goes out. Then move the whole job — hosting, business email, security and backups — to CodexFuse, where one fully managed platform on credits keeps the technical side handled while you focus on the business itself. Get started with CodexFuse now, and make sure the next share shows your business the way it deserves to be seen.
