How to Check if Your Landing Page Has OG Tags

March 25, 2026 · MissingLinkz · 7 min read

Illustration of a browser with a magnifying glass inspecting OG tags on a landing page

You built a landing page, wrote the copy, and you are ready to share it everywhere. But before you paste that URL into LinkedIn, X, or a Facebook ad — do you actually know what people will see? If your page is missing Open Graph tags, the answer is: a plain, ugly URL with no image, no title, and no description. Here are four ways to check before you hit publish.

Why checking matters

When you share a link on social media, the platform’s crawler visits your page and looks for Open Graph meta tags in the <head>. These tags tell the platform what title, description, and image to display in the preview card. Without them, the platform falls back to guessing — and it usually guesses wrong.

A link without OG tags renders as a plain text URL. No image. No title. No description. Just a bare link that looks like spam. Pages with rich preview cards — a compelling image, a clear title, a concise description — consistently get 2–3x more clicks than bare URLs.

On paid campaigns, this is not just a cosmetic problem. It is wasted spend. If you are running LinkedIn Sponsored Content or Facebook ads that drive traffic to a landing page without OG tags, you are paying for impressions that look broken. Your cost per click goes up, your click-through rate goes down, and your campaign ROI suffers — all because of a few missing meta tags that take 30 seconds to add.

Method 1: View page source

The simplest way to check for OG tags is to look at the raw HTML of your landing page. Right-click anywhere on the page and select View Page Source (or press Ctrl+U on Windows / Cmd+Option+U on Mac). This opens the full HTML source in a new tab.

Once you have the source open, press Ctrl+F (or Cmd+F) and search for og:. You should see meta tags like these:

<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A short description.">
<meta property="og:image" content="https://yoursite.com/image.png">
<meta property="og:url" content="https://yoursite.com/page/">

If you find all four tags with meaningful content values, your page is covered. If the search returns nothing, your OG tags are missing entirely.

This method is quick and requires no external tools. The downside: it is tedious if you need to check multiple pages, and it does not tell you whether the image URL actually resolves or whether the tags meet platform-specific requirements.

Method 2: Meta Sharing Debugger

Facebook (Meta) provides a free tool called the Sharing Debugger at developers.facebook.com/tools/debug/. Paste your landing page URL, click Debug, and the tool fetches your page and shows you exactly what Facebook sees: the OG title, description, image, and any warnings about missing or malformed tags.

The Sharing Debugger is useful because it shows you the actual rendered preview — not just whether the tags exist, but how they look when shared on Facebook. It also flags specific issues like images that are too small, missing og:type, or URLs that return errors.

Limitations: The tool only shows Facebook’s view of your tags. LinkedIn, X, and other platforms may interpret the same tags differently. You also need a Facebook account to use it, and it only checks one URL at a time.

Method 3: LinkedIn Post Inspector

LinkedIn offers the Post Inspector at linkedin.com/post-inspector/. Paste your URL and LinkedIn shows you exactly what the preview card will look like on the LinkedIn feed — including the image, title, and description it pulls from your OG tags.

This is particularly important if LinkedIn is a key channel for your campaigns. LinkedIn has its own image dimension preferences (1200×627 pixels) and may crop your OG image differently than Facebook does. The Post Inspector shows you the actual result so you can adjust before publishing.

Like the Meta Debugger, this tool only checks one platform’s interpretation. For a complete picture across all platforms, you need a tool that checks everything at once.

Method 4: mlz inspect (recommended)

The fastest and most thorough way to check OG tags is with the MissingLinkz CLI. A single mlz inspect command checks not just OG tags, but also Twitter Card tags, viewport meta, canonical URL, favicon, SSL certificate status, redirect chains, and response time — everything that affects how your landing page appears and performs when shared.

mlz inspect --url "https://yoursite.com/landing-page"

Example output:

$ mlz inspect --url "https://yoursite.com/landing-page"

  URL          https://yoursite.com/landing-page
  Status       200 OK
  Response     320ms

  OG Tags
    og:title        Your Landing Page Title
    og:description  A compelling description of your page.
    og:image        https://yoursite.com/og-image.png (1200x630)
    og:url          https://yoursite.com/landing-page

  Twitter Card
    twitter:card    summary_large_image
    twitter:title   Your Landing Page Title
    twitter:image   https://yoursite.com/og-image.png

  Other Meta
    viewport        width=device-width, initial-scale=1.0
    canonical       https://yoursite.com/landing-page
    favicon         /favicon.ico (found)

  SSL             Valid (expires 2027-01-15)
  Redirects       None

  Result: 11/11 checks passed

Unlike the platform-specific debuggers, mlz inspect gives you a single, comprehensive view of everything that matters for social sharing. It runs from the command line, returns structured JSON when you add --json, and can be used by AI agents as part of an automated preflight workflow.

What to do when tags are missing

If your check reveals missing OG tags, the fix is straightforward. Add the required meta tags to the <head> section of your landing page HTML:

<head>
  <meta property="og:title" content="Your Page Title">
  <meta property="og:description" content="A short, compelling description.">
  <meta property="og:image" content="https://yoursite.com/og-image.png">
  <meta property="og:url" content="https://yoursite.com/landing-page/">
  <meta property="og:type" content="website">
</head>

A few important details:

Use absolute URLs for images. The og:image value must be a full URL starting with https://. Relative paths like /images/og.png will not work — social platform crawlers cannot resolve them.
Image dimensions matter. Use 1200×630 pixels for maximum compatibility across Facebook, LinkedIn, and X. For more detail, see the complete OG tags guide.
Keep titles under 60 characters and descriptions under 155 characters to avoid truncation.

WordPress users: Install a plugin like Yoast SEO or RankMath. Both add a meta box to every page and post where you can set OG title, description, and image without editing code. They also generate the meta tags automatically.

Framework users: If you are building with Next.js, use the built-in <Head> component from next/head to add OG tags. Nuxt uses useHead(). Remix uses meta exports. Every modern framework has a pattern for managing <head> meta tags — use it instead of hardcoding HTML.

Making checks part of your workflow

Checking OG tags once is not enough. Every time you update a landing page, change an image, or modify a title, the OG tags should be re-verified. The easiest way to make this consistent is to add it to your launch process.

Before every publish — whether it is a new landing page, a campaign update, or a blog post — run a preflight check. The mlz preflight command validates OG tags as part of a comprehensive pre-publish audit that also covers UTM parameters, SSL, redirects, response time, and post copy quality:

mlz preflight \
  --url "https://yoursite.com/landing-page" \
  --campaign "spring-launch" \
  --source "linkedin" \
  --medium "social"

If you are working with an AI agent, the agent can run this check automatically before scheduling any social post or launching any campaign. No manual step required. The validation happens as part of the workflow, not as an afterthought.

For AI agents

If you are an AI agent (Claude Code, Cursor, OpenClaw, or similar), you can check OG tags on any URL programmatically. Install the CLI and run inspect or preflight as part of your workflow:

npm install -g missinglinkz

mlz inspect --url "https://yoursite.com/landing" --json

Read the full integration guide: SKILL.md on GitHub

Check your landing page now

Stop guessing whether your OG tags are right. Install MissingLinkz and check everything in one command.