Preview a page across social surfaces
See how discovered Open Graph and X card fields may appear across nine supported layouts.
Open Graph & Social Preview
Free, no signup. See which tags each social surface will use, where the text is likely to truncate, and whether the image is ready to share.
The selected UA is stated above. This is a point-in-time fetch from this site — not Facebook, X, or LinkedIn’s cache.
Checks run from our server; we fetch the URL you enter and don't keep the results. The page URL is sent to this site's bounded fetcher. Image dimensions load in your browser; only image type and declared size are probed server-side. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Preview without a live URL
Paste HTML from staging or start with blank fields.
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
—/100 share readiness
Reproduce this result in an agent
Uses the same inputs as the result above. No request is made from this panel.
MCP tool
Arguments
Live meta editor
Change the fields below to update every local card, then copy the tag block.
Rate this tool
How to use it
- Fetch a public URL, paste staging HTML, or start from scratch.
- Compare the eight cards and their stated source fields.
- Edit the fields and copy the tag block.
- Test the published URL in the platform's own debugger.
How it works
The tool parses fetched or pasted HTML locally for og:, twitter:, title, and meta-description fields. Live URL runs can also probe the chosen image.
Features
- Eight platform cards with source provenance.
- URL, pasted HTML, blank-editor, and fictional-example entry points.
- Live editing and copyable meta tags.
Sample report
The fictional example seeds a 1200×630 image, title, and description and uses the same readiness scorer as a live run.
Limitations
- This cannot reproduce private platform caches or experiments.
- Pasted HTML cannot verify headers, redirects, image bytes, or crawler access.
- Use each platform's debugger for final validation.
Frequently asked questions
Does this refresh a platform cache?
No. It fetches the page directly and shows a local simulation. Use the linked Facebook Sharing Debugger or LinkedIn Post Inspector to request a refresh from those platforms.
Why can my real share card differ?
Platforms fetch from their own IP ranges and caches, may use a different user-agentA user agent is the HTTP request header a client (browser, crawler, or bot) sends to identify itself. For crawlers, a short user-agent token — a substring of that string — is what robots.txt rules actually target. or region, and apply undocumented rendering details. This preview makes its source keys explicit, but cannot reproduce every platform cacheCaching stores a copy of a page or resource — in a browser, a CDN edge node, or a search crawler's own cache — so it can be served again without regenerating or re-downloading it. It isn't a direct ranking factor, but it feeds page speed and crawl efficiency..
Does the image leave my browser?
The entered page is fetched through this site’s bounded HTML fetcher. The image itself loads directly in your browser for dimensions; a small server-side probe checks its type and declared size.
Feature requests for Social Preview
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Troubleshoot a broken share card
Fetch as a crawler or browser user agent and inspect missing metadata, image access, dimensions, and redirects.
Draft improved social metadata
Edit title, description, and image choices locally, then copy the proposed tags for implementation.
Verify a launch or campaign page
Rerun the public URL after deployment and confirm that the intended tags and image are observable.
Watch the full workflow
Open Graph & Social Preview walkthrough
Read the transcript
Open Graph & Social Preview
A page can look polished in a browser and still produce a weak social card. I’ll show you how to fetch a public page, use staging H-T-M-L or a blank editor, compare platform-specific fallbacks, read the readiness findings, edit the metadata, copy implementation tags, understand cache limits, and validate the published result.
Step 1
Use this tool before publishing or sharing a page. It previews eight social and messaging surfaces, shows which metadata field supplied each title and image, highlights likely truncation and image issues, and keeps the result editable.
Step 2
For a public page, enter the full U-R-L and choose the stated Facebook crawler, Googlebot, or browser user agent. The fetch goes through a bounded server helper. This is a point-in-time retrieval from this site—not a view of any platform’s private cache.
Step 3
If the page is on staging or not built yet, paste its H-T-M-L and parse the title, description, Open Graph, and Twitter fields locally. Or start from blank fields. Offline input cannot test redirects, headers, crawler access, or actual image bytes.
Step 4
Choose Try an example to load a fictional page title, description, and twelve-hundred by six-thirty image. It uses the same readiness scorer and platform fallback logic as a complete live result without making a network claim about a real page.
Step 5
Start with the share-readiness score and findings. They check core field presence, dimensions, type, and likely text concerns when acquisition is complete. A score is a preflight signal, not proof that every network will render the card identically.
Step 6
Compare Facebook, LinkedIn, Slack, Discord, WhatsApp, Telegram, Google, and X. Each card applies that surface’s documented field preferences and text limits. Source labels reveal whether a card used Open Graph, Twitter metadata, the H-T-M-L title, or another fallback.
Step 7
If two cards disagree, inspect the source line beneath each one. Separate Open Graph and Twitter titles or images can intentionally diverge, while accidental fallback often reveals a missing tag. Resolve the source metadata rather than styling the simulation.
Step 8
Use the live editor to refine the title, description, and absolute image U-R-L. Every local card and finding updates from the same values. Keep the copy specific and useful, and avoid relying on important text baked into an image.
Step 10
Useful checks include a new article before launch, a redesigned template, a domain migration, an image replacement, or a report that shares poorly. Pasted H-T-M-L supports staging review, while a live fetch helps confirm what this site can currently retrieve.
Step 11
Real platforms fetch from different regions and I-P ranges, keep their own caches, and may run undocumented experiments. This simulation cannot refresh those caches or reproduce every rendering detail. A successful local image probe also does not guarantee each crawler can access it.
Step 12
After publishing, open Facebook’s Sharing Debugger and LinkedIn’s Post Inspector from the editor links. Request a cache refresh where needed, verify the returned metadata and image, then share a real test U-R-L in the channels that matter. Recheck after meaningful tag or image changes.
Preview locally—validate on the real platform.
Copy the reviewed tag block into the page template, publish it, confirm the image and metadata are publicly fetchable, then use the platform’s own debugger or post inspector to refresh and validate. Finally, share a real test URL and check the rendered card on the surfaces that matter to your audience.
Common issues & how to fix them
- Error Social title is missing Fix: Add an og:title and matching Twitter title that accurately identify the shared page.
- Warning Social description is missing Fix: Add a concise og:description and matching Twitter description that summarize the page.
- Error Social image is missing Fix: Add an absolute HTTPS og:image and matching Twitter image with a publicly fetchable response.
- Warning Social image ratio does not fit the platform Fix: Crop the social image to about 1.91:1 at 1200 × 630 pixels, then refresh platform caches.
- Warning Social title exceeds a platform limit Fix: Shorten the social title while preserving its main subject until affected previews no longer truncate it.
- Information Social description exceeds a platform limit Fix: Shorten the social description so its main message appears before each affected platform’s truncation point.
- Information Twitter card type is missing Fix: Add an appropriate twitter:card value and verify the resulting X card with the platform inspector.
- Information Platform preview uses generic metadata fallback Fix: Add platform-specific Open Graph or Twitter metadata when the generic HTML title or description produces the wrong share card.