How OG Fixer previews work
OG Fixer fetches the metadata available from the URL you submit, then renders local preview components using those fields. The cards are useful for checking content, hierarchy, image choice, and obvious metadata gaps. They are simulations, not screenshots returned by the social networks themselves.
What is source-backed
The inspection starts from metadata fetched from the submitted page, including Open Graph, Twitter-card, title, description, image, and final URL fields when available. The score and preview components operate on that fetched metadata.
What is simulated
Twitter/X, Facebook, LinkedIn, Slack, Discord, and Google cards are rendered by OG Fixer in its own UI. They approximate common card layouts so you can spot likely problems before sharing. They are not official platform renderers and do not prove what a recipient will see.
Why the final card can differ
Platforms can cache older metadata and images, apply their own crop or truncation rules, choose fallback fields, change card layouts, or fetch a page differently. For a consequential launch, verify the final result in the destination platform or its official inspection tool when one is available.
What a passing OG Fixer check means
It means the fetched metadata is compatible with OG Fixer's checks and local simulations. It does not certify platform acceptance, cache refresh, delivery, reach, clicks, or any other distribution outcome.