Meta tags not in page source
View your page source, not DevTools. Meta tags must be in the initial HTML response, not injected by JavaScript. Social crawlers only see server-rendered HTML.
Wrong path in og:image URL
The path must match the actual page URL. If your page is at yoursite.com/blog/my-post, the og:image URL should be https://$OGPLUS_KEY.ogplus.net/blog/my-post.
For dynamic sites, ensure your server-side code outputs the correct path. Hardcoded paths are the most common source of mismatches.
Wrong image showing
This is almost always a caching issue. Purge the cached image from the OpenGraph+ dashboard, then re-check with the preview tool.
JavaScript-rendered content
OpenGraph+ renders your page with a browser, so JavaScript content is captured in the social card image. But the og:image meta tag itself must be in the initial HTML for social platforms to read it. Social crawlers do not execute JavaScript.
Social platforms not updating
Social networks cache images aggressively. After purging from OpenGraph+, use each platform’s debugger to force a refresh:
- Facebook: Sharing Debugger
- Twitter/X: Card Validator
- LinkedIn: Post Inspector
Purging cached images
- Go to your OpenGraph+ dashboard
- Navigate to the website’s cache page
- Enter the URL and purge
The next request from a social platform will trigger a fresh render.
Testing
Use the preview tool in your OpenGraph+ dashboard to verify your setup before sharing URLs. This shows you exactly what social platforms will see.
Need a specific framework guide?
Check our framework-specific guides for detailed integration instructions for Next.js, Nuxt, Astro, Django, Laravel, Jekyll, Middleman, WordPress, Shopify, Webflow, Wix, Rails, or Sitepress.