Something not working? Here are the most common issues and how to fix them.

Meta tags not in page source

Nuxt 3 renders on the server by default, so useHead and useSeoMeta should produce meta tags in the initial HTML.

Check: View your page source, not DevTools. DevTools shows client-hydrated HTML. Page source shows what crawlers see.

If tags are missing, make sure useHead or useSeoMeta is called in a component that runs on the server, not inside a <ClientOnly> wrapper.

Client-only components

Components wrapped in <ClientOnly> don’t render on the server. If your meta tag logic is inside a client-only component, social crawlers won’t see it.

Move useHead / useSeoMeta calls to the parent page or layout component instead.

Wrong image showing

This is almost always a caching issue. Social platforms and OpenGraph+ both cache images.

1. Open the preview tool in your OpenGraph+ dashboard
2. Paste your URL to see what OpenGraph+ currently has
3. If the image is stale, purge it from the dashboard
4. Re-check with the preview tool

Social platforms not updating

Twitter, LinkedIn, and Slack cache images aggressively on their end. After confirming the correct image appears in the OpenGraph+ preview tool:

• Twitter: Use the Card Validator to force a refresh
• LinkedIn: Use the Post Inspector to clear their cache
• Facebook: Use the Sharing Debugger to scrape again

This is platform-side caching that OpenGraph+ cannot control.

Purging cached images

1. Go to your website dashboard in OpenGraph+
2. Find the page you want to refresh
3. Click purge to clear the cached image

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.