TechCompare LogoTechCompare

How to test Open Graph tags: sharing previews and current tools

Test with the Facebook Sharing Debugger first, then inspect the page source and test an X share or post preview. For messaging apps (Discord, Slack, WhatsApp, iMessage), test manually in a private conversation because each service caches previews separately. Keep a short checklist of the platforms that matter to your audience.

Platform debuggers and share previews let you test the tags that each crawler sees. The Facebook Sharing Debugger at developers.facebook.com/tools/debug is useful for Facebook's extracted title, description, image, URL, and type. X no longer has the old Card Validator workflow as a dependable public check, so inspect the page tags directly and test a normal post preview. LinkedIn's inspection flow plus manual Discord, Slack, and WhatsApp shares round out the toolkit.

By TechCompare · Updated

Platform or focus
Best Practices
OG tag strategy and tooling
Topic detail
OG debugger tools
debugger-tools

How this is calculated

Facebook's Sharing Debugger shows what Facebook extracted from your page: title, description, image, URL, and type. It also reports warnings and lets you request a fresh scrape. For X, inspect the `twitter:` and `og:` tags, make sure the image is publicly fetchable over HTTPS, and test an ordinary share or post preview. The common failure across platforms is a missing or unreachable image, an unsupported format, or a crawler seeing stale cached HTML.

Verdict

Each platform exposes a different check: the Facebook Sharing Debugger, LinkedIn's inspection tools, an X share or post preview, and manual Discord, Slack, or WhatsApp shares. Common failures revolve around the image, usually from an unreachable HTTPS asset, unsupported dimensions or format, stale cached HTML, or a crawler being blocked before it can read the tags.

More OG scenarios

Frequently asked questions

Which debugger should I use to test Open Graph tags?
Start with the Facebook Sharing Debugger at developers.facebook.com/tools/debug. It shows what Facebook extracted, reports warnings, and lets you request a fresh scrape. Then inspect the `twitter:` and `og:` tags directly and test an X share or post preview, followed by LinkedIn or messaging apps if those channels matter to you.
Why does my og:image show up in some debuggers but not others?
Each platform's crawler has its own failure modes: missing og:image:secure_url on HTTPS sites, images on a different domain without the right CORS response, or fetches that blow past the 5-second timeout most crawlers enforce. The Facebook debugger's warning log names the specific failure, which usually explains why the stricter platforms dropped the image too.
How do I force Facebook to re-scrape my updated OG tags?
Paste the URL into the Sharing Debugger and hit the Scrape Again button. That clears Facebook's cache immediately, and any new shares of the link pick up the fresh tags. Previously shared posts don't retro-update - Facebook snapshots the card at share time - so re-scraping only affects shares going forward.