Webex Link Preview Not Working? Here is How to Fix It
Why your Webex link preview shows wrong title, no image, or just a plain URL — and the exact steps to fix it.
How Webex generates link previews
When you paste a URL in Webex (Messaging or Spaces), the Webex server fetches your page's HTML and reads Open Graph meta tags to build a preview card. If the OG tags are missing, malformed, or blocked, Webex shows just the raw URL with no card.
Webex reads these tags in priority order:
<!-- Minimum tags for a Webex link preview --> <meta property="og:title" content="Your Page Title" /> <meta property="og:description" content="A short summary of this page." /> <meta property="og:image" content="https://yourdomain.com/og/page.png" /> <meta property="og:url" content="https://yourdomain.com/page" /> <meta property="og:type" content="website" />
1. Missing or empty OG tags
The most common cause. View your page source and check that the OG tags exist inside <head>:
# Quick check from terminal: curl -sL https://yourdomain.com/page | grep 'og:' # You should see lines like: # <meta property="og:title" content="..." /> # <meta property="og:image" content="..." /> # <meta property="og:description" content="..." /> # If you see nothing, your OG tags are missing. # If you see empty content="", that's the same as missing.
Fix: Add the required OG meta tags to your page's <head>. See our framework-specific guides for copy-paste examples.
2. OG image URL is relative or broken
Webex requires an absolute URL for og:image. A relative path like /images/og.png will not work.
<!-- ❌ Wrong — relative URL --> <meta property="og:image" content="/images/og.png" /> <!-- ✅ Correct — absolute URL with https --> <meta property="og:image" content="https://yourdomain.com/images/og.png" /> <!-- Also check that the image URL actually returns an image: --> <!-- curl -I https://yourdomain.com/images/og.png --> <!-- Should return 200 OK with Content-Type: image/png or image/jpeg -->
3. Webex bot is blocked by your server
Webex uses a server-side crawler to fetch your page. If your site blocks unknown user agents, returns a login wall, or requires JavaScript execution, the crawler gets an empty response.
# Check if your server blocks the Webex bot: curl -A "Mozilla/5.0 (compatible; Webex)" -sL https://yourdomain.com/page | grep 'og:title' # If this returns nothing but a normal browser request works, # your server is blocking the Webex user agent. # Fix: Allow the Webex bot in your robots.txt or WAF rules: # robots.txt User-agent: * Allow: / # If using Cloudflare, Vercel, or a WAF: # Add an exception for bot user agents on pages # that need social previews.
4. Client-side rendered pages (SPA)
If your page is a single-page app (React, Vue, Angular) that renders OG tags with JavaScript, the Webex crawler will see an empty <head> because it doesn't execute JavaScript.
Fix: Use server-side rendering (SSR) or static site generation (SSG) so that OG tags are present in the initial HTML response. If you can't add SSR, use a prerendering service like Prerender.io to serve pre-rendered HTML to bots.
5. Webex cache is stale
Webex caches link previews for a period of time. If you've fixed your OG tags but the old preview still appears:
- Wait: Webex cache typically refreshes within a few hours. There is no public cache-busting tool like Facebook's Sharing Debugger.
- Append a query parameter: Share the URL with a cache-buster like
?v=2to force a fresh fetch. - Contact Webex support: For persistent issues, Webex support can sometimes clear the cache for specific URLs.
Complete OG tag template for Webex
<head> <title>Your Page Title</title> <!-- Open Graph (used by Webex, Slack, Discord, etc.) --> <meta property="og:title" content="Your Page Title" /> <meta property="og:description" content="A concise description under 200 characters." /> <meta property="og:image" content="https://yourdomain.com/og/page.png" /> <meta property="og:image:width" content="1200" /> <meta property="og:image:height" content="630" /> <meta property="og:url" content="https://yourdomain.com/page" /> <meta property="og:type" content="website" /> <!-- Twitter Card (also helps some platforms) --> <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:title" content="Your Page Title" /> <meta name="twitter:description" content="A concise description." /> <meta name="twitter:image" content="https://yourdomain.com/og/page.png" /> </head>
Verify your Webex link previews
After fixing your tags, paste your URL into OGFixer to preview how Webex, Slack, Discord, and other platforms will render your links.