You fixed your meta tags and hit publish. Then the LinkedIn post shows an old image. Testing Open Graph tags before you share catches that failure in minutes, not after the post is live.
Short answer
Test Open Graph tags in three layers: raw HTML (View Page Source), a multi-platform preview tool like OpenGraph Check, and the official debugger for each network you care about (Facebook Sharing Debugger, LinkedIn Post Inspector). Confirm og:title, og:description, og:image, and og:url appear in server HTML with absolute HTTPS URLs. Open the image URL in a browser tab. Only share after previews look correct on every target platform.
Why testing matters
Social crawlers do not see your site the way your browser does. They request HTML once, read <head> meta tags, fetch og:image, and cache the result. No JavaScript execution on most platforms. No second chance if the first scrape fails.
A page that looks perfect in Chrome can still ship broken tags because:
- Meta tags load only after client-side hydration
- Staging used relative image paths that break in production
- CDN serves an old cached HTML response
og:imagepoints to a redirect or login wall
Testing before publish is cheaper than editing a live campaign post.
The 10-minute pre-publish workflow
1. Confirm tags exist in page source
Right-click the live URL → View Page Source (not Inspect Element).
Search for og:title. You should see something like:
<meta property="og:title" content="Your headline"><meta property="og:description" content="Your summary."><meta property="og:image" content="https://example.com/og.jpg"><meta property="og:url" content="https://example.com/page"><meta property="og:type" content="website">If tags appear in DevTools but not in View Source, crawlers will miss them. Fix server-side rendering first. See Open Graph Tags Explained for the full tag list.
2. Validate the image URL
Copy og:image and paste it into a new browser tab.
| Check | Pass |
|---|---|
| HTTP status | 200 OK |
| Protocol | HTTPS |
| Auth | Loads without login |
| Content-Type | image/jpeg, image/png, or image/webp |
| Size | At least 1200 × 630 px recommended |
If the image fails, read How to Fix a Missing OG Image.
3. Run OpenGraph Check
Paste your URL into OpenGraph Check. The scan shows:
- Live meta values crawlers receive
- Previews for Facebook, X, LinkedIn, WhatsApp, and Discord
- A code tab with the exact tags detected
- Missing or invalid fields highlighted
Use this as your default test. One URL, every major platform, under 30 seconds.
4. Test platform debuggers for networks you will post on
Official tools show what each crawler cached and let you force a re-scrape.
| Platform | Tool |
|---|---|
| Facebook, Instagram, WhatsApp | Facebook Sharing Debugger |
| LinkedIn Post Inspector | |
| X (Twitter) | Card Validator (limited availability) |
Guides: Facebook Sharing Debugger, LinkedIn Post Inspector.
5. Share a test link privately
Send the URL to yourself on WhatsApp or Slack before a public post. Real apps sometimes behave differently than debuggers when cache is warm.
What to check on every scan
Required tags
| Tag | What to verify |
|---|---|
og:title | Matches your intended headline, under ~60 characters |
og:description | Clear summary, 80-125 characters ideal |
og:image | Absolute HTTPS URL, correct aspect ratio |
og:url | Matches the canonical URL you share |
og:type | website, article, or product as appropriate |
Twitter Card tags (for X)
X falls back to Open Graph, but explicit tags give more control. See Open Graph vs Twitter Card.
<meta name="twitter:card" content="summary_large_image"><meta name="twitter:title" content="Your headline"><meta name="twitter:description" content="Your summary."><meta name="twitter:image" content="https://example.com/og.jpg">Image dimensions by platform
General safe size: 1200 × 630 px (1.91:1). Platform-specific details in Open Graph Image Size Guide.
Testing checklist before you hit share
Copy this list into your launch workflow:
- View Page Source shows all
og:*tags -
og:imageopens directly in browser (200, HTTPS) - Title and description read well at mobile width
- OpenGraph Check previews look correct on target platforms
- Facebook Sharing Debugger scrape succeeds (if posting to Meta apps)
- LinkedIn Post Inspector shows correct image (if posting to LinkedIn)
-
robots.txtdoes not block social crawlers - Page returns 200 for the exact URL you will share (no redirect loop)
Common testing mistakes
Testing only in the browser DOM
React, Vue, and Next.js client components often inject tags after load. Crawlers never see them. Always use View Source.
Testing on localhost
Social crawlers cannot reach localhost or private staging URLs without a tunnel. Deploy to a public HTTPS URL first, or use a staging subdomain with basic auth disabled for the test path.
Testing the wrong URL
www vs non-www, trailing slashes, and query strings matter. Test the exact URL you paste into the post. Set og:url to the same value.
Ignoring cache
Platforms cache previews aggressively. If you changed tags on a URL that was shared before, run the debugger scrape again. Read Why Social Platforms Cache Link Previews and Open Graph Cache Busting.
Assuming one preview equals all platforms
Discord reads Open Graph. iMessage uses its own parser. WhatsApp shares Meta's cache with Facebook. Test each network you care about.
When to retest
Run the full workflow again when you:
- Change
og:image, title, or description - Move domains or switch CMS
- Deploy a redesign or new framework
- See a wrong preview reported by a colleague
- Launch paid social ads (broken previews waste spend)
After a fix, wait for debugger tools to confirm the new scrape before posting publicly.
Automated vs manual testing
Manual (recommended for launches): View Source + OpenGraph Check + platform debugger. Catches visual and crawler issues automation misses.
CI checks (optional): Fetch production HTML in a deploy pipeline and assert og:title and og:image exist. Does not replace visual preview review.
Browser extensions: Convenient for quick checks, but verify against raw HTML before high-stakes shares.
FAQ
Can I test Open Graph tags without publishing the page?
The URL must be publicly reachable over HTTPS. Use a staging subdomain, password-protected preview tools with crawler access, or publish to a hidden path (/preview/launch) that is not linked in navigation.
How long does testing take?
Basic scan: 2-3 minutes. Full workflow with two platform debuggers: under 10 minutes.
Does OpenGraph Check replace the Facebook Sharing Debugger?
No. OpenGraph Check shows live tags and multi-platform previews fast. Facebook's debugger is still required to clear Meta's cache and see official scrape errors.
Why does my test preview differ from the live post?
Stale platform cache. Re-scrape in the debugger, or share with a cache-busting query string. See Facebook Preview Not Updating.
Should I test before or after DNS goes live?
After DNS and SSL are active on the production domain. Testing on the wrong hostname produces misleading results.
Do I need to test Twitter Card tags separately?
If you set twitter:* tags, verify them. If not, confirm Open Graph previews on X look acceptable via OpenGraph Check.
What if og:image works in the debugger but not WhatsApp?
WhatsApp uses Meta's infrastructure. Re-scrape in the Facebook Sharing Debugger, then test in a new chat thread.
Bottom line
Testing Open Graph tags takes ten minutes and prevents broken link cards on high-visibility posts. Read page source, validate the image URL, scan with OpenGraph Check, and confirm with platform debuggers before you share. Do that on every launch and your previews match what you designed.
