Publishing a new page or launch
Confirm that the live URL exposes the right metadata and that the image can actually be fetched by social crawlers.
Audit a live public URL for Open Graph tags, X/Twitter card coverage, canonical alignment, and preview image fetchability before you share it.
Live page you plan to share.
Metadata, redirects, image reachability.
Use the priority list before publish.
Use this tool when
Confirm that the live URL exposes the right metadata and that the image can actually be fetched by social crawlers.
Use it when a page shares with the wrong image, missing title, weak fallback card, or stale preview art.
Run it after CDN, canonical, cache, or CMS template changes so social previews do not silently regress.
Tool visual
A good social share setup is not just one image tag. You need the full handoff: page URL, title, description, image, and X-specific card instruction.
Healthy setup
This is enough for predictable Facebook, LinkedIn, Slack-style, and X large-card previews on most public pages.
Weak setup
This is where previews become unreliable or platform-specific. The checker is built to surface these first.
Tool visual
Most teams know they need `og:image`, but the rest of the preview is just as important. This board shows which tags control which part of the share card.
Page URL context
Canonical + og:url keep the card tied to one public page.
Use `twitter:card=summary_large_image` if you want X to prefer the wide image treatment instead of a compact fallback.
The preview asset still needs a direct `200`, image MIME type, and enough pixels to survive large-card rendering.
If `og:url` points at one page and canonical points at another, you create mixed signals for debuggers and crawlers.
Tool visual
The fastest way to debug bad share previews is to fix the blockers in severity order instead of tweaking everything at once.
| Problem | What breaks | Fix first |
|---|---|---|
| Missing `og:image` | Social cards fall back unpredictably or render without a strong image. | Publish one absolute, public image URL first. |
| Wrong or tiny image | Large-card previews look soft, cropped, or weak in-feed. | Aim for roughly `1200 x 630` and recheck the rendered card. |
| Missing title/description | Networks invent their own fallbacks from page copy. | Set concise explicit OG values before tuning image design. |
| Versionless preview art | Platforms can keep an old image even when the page markup changed. | Version the filename or query string when the card art changes. |
Step 1
Create the image. Use OG Image Generator if you still need the asset.
Step 2
Publish absolute tags. Keep `og:image`, `og:url`, and canonical tied to the final public page and asset URL.
Step 3
Run this checker. Confirm the preview image is reachable and the tags are aligned before you share.
Step 4
Version changed artwork. If you swap the preview image later, change the URL too so social caches pick it up.
Related workflow
Create the asset first, then validate it on the live page.
Keep moving
Create the preview image before auditing the live metadata handoff.
Open tool
Keep moving
Pick readable brand colors before exporting final preview artwork.
Open tool
Keep moving
Audit another critical share/search surface when the page launch is broader than OG metadata.
Open tool
Practical playbooks to help you ship faster with fewer mistakes.
Audit live Open Graph and X metadata, debug broken social previews, and fix the highest-impact issues first.
Use platform-safe Open Graph dimensions so social previews look clean and clickable.
Use platform-ready dimensions and safe zones for social posts, link previews, ads, and carousels.
Configure CDN image delivery, canonical URLs, and cache behavior so crawlers can consistently discover and index assets.