{{ card.description || 'No description provided.' }}
| Platform | Source tag | Host | Dimensions | Fit | Action | Copy |
|---|---|---|---|---|---|---|
| {{ row.platform }} | {{ row.sourceTag }} | {{ row.host }} | {{ row.dimensions }} | {{ row.fit }} | {{ row.action }} |
| Family | Tag | Value | Used by | Copy |
|---|---|---|---|---|
| {{ row.family }} | {{ row.tag }} | {{ row.value }} | {{ row.usedBy }} |
| Level | Check | Evidence | Action | Copy |
|---|---|---|---|---|
| {{ row.level }} | {{ row.check }} | {{ row.evidence }} | {{ row.action }} |
{{ headSnippet }}Social preview metadata is the set of head tags that link-preview crawlers read before rendering a shared URL. Open Graph tags describe the shared object, X card tags can provide platform-specific fallback fields, canonical links identify the preferred page address, and ordinary title and description tags often fill gaps when social tags are missing.
A preview can fail even when the page looks correct in a browser. Crawler access, cached results, relative image paths, missing dimensions, blocked images, or a title that is too long for a card can all change what appears in feeds and team chats. A launch review needs the raw tags and the likely card shape in the same place, because small head changes can decide whether a link is readable or silent.
Preview checks should be treated as a pre-publish screen. They make metadata problems visible before the final URL is handed to each platform's own crawler, where cache state, robots rules, image access, and platform-specific rendering still matter.
Choose the source path first, then compare the preview cards with the extracted tags and audit rows.
twitter:card is missing, Image size override fills in missing width and height tags, and Load remote preview images lets the browser request the image URLs shown in the card mockups.A clean review ends with a believable card preview, a complete title/description/image/canonical set, no unexpected Error rows, and a live crawler test planned for the deployed URL.
The platform fit percentage is a local readiness score, not a promise from Facebook, X, LinkedIn, Slack, Discord, WhatsApp, Telegram, or iMessage. Treat it as a triage signal that points to missing or risky metadata before you run each platform's own crawler or preview inspector.
| Result Cue | Best Reading | What to Verify Next |
|---|---|---|
| Preview needs crawler fixes | At least one required preview fact is missing, usually title or image metadata. | Open Crawler Audit and fix the rows marked Error before reviewing platform scores. |
| Warning or Review rows | The card may render, but the value is incomplete, long, small, insecure, assumed, or worth checking by eye. | Compare the row evidence with the card mockups and the final page facts. |
| Platform Scores at 85% or above | The visible fields fit the tool's readiness target for that platform. | Test the deployed URL with the target crawler, because cache state and bot access are outside the local score. |
| Tag Ledger | The row list is the best place to confirm exactly which tags were found and which preview family uses them. | Check duplicate or fallback values when og:title, twitter:title, and title disagree. |
| Head Snippet | The snippet mirrors the extracted head tags, not a regenerated or corrected version of the page metadata. | Use it to inspect what was found, then update the source page rather than editing the snippet as the final fix. |
The common false confidence is assuming a good mockup equals the public share card. A platform can keep an older cache, crop a different area, ignore a fallback field, block an image, or see different HTML after deployment. Verify the actual public URL before launch.
Open Graph represents a page as a shareable object. The core object facts are the preview title, object type, representative image, and canonical object URL. Optional facts such as description, site name, image width, image height, and image alt text help crawlers choose the right card content and make better fallback decisions.
X card metadata uses twitter: tag names for similar title, description, image, and card-type facts. Many consumers also fall back to Open Graph or ordinary HTML metadata when platform-specific fields are absent. Canonical URL signals matter because preview crawlers and search systems need one stable identity for a page that may be reachable through several addresses.
| Stage | What Is Read | Resulting Meaning |
|---|---|---|
| Head extraction | title, meta, and selected link elements. |
The ledger records title, description, canonical, Open Graph, X card, image, icon, and theme-color facts that appear in the supplied HTML. |
| URL resolution | Image, canonical, og:url, and X URL values, plus Base URL when pasted HTML is used. |
Relative URLs are converted to absolute URLs when a reliable base address exists. |
| Field precedence | Open Graph values first, then X card values, then ordinary title and description values where useful. | The card mockups prefer explicit social metadata but still show fallback content when a page omits some fields. |
| Image sizing | og:image:width, og:image:height, X image dimensions, or Image size override. |
Width, height, and aspect ratio determine image-dimension audit rows and the card ratio label. |
| Audit profile | Launch QA, Standard review, or Quick preview. | The profile changes how strict missing descriptions, small images, missing X card fields, and short text checks should feel during review. |
Each platform readiness score starts at 100 and subtracts penalties for missing or risky metadata. The result is rounded and clamped from 0 to 100.
p is a penalty for one failed check. A score of 85 or higher is labeled Ready, 70 to 84 is labeled Review, and below 70 is labeled Fix. For example, a page missing a social image loses 22 points on most platforms, so a 100-point starting score becomes 78 before any other penalties are considered.
| Penalty Condition | Applies To | Points |
|---|---|---|
| Missing preview title | All platform scores | 24 |
| Missing preview description | All platform scores | 16 |
| Missing preview image | Facebook, X / Twitter, LinkedIn, Discord, WhatsApp, Telegram, iMessage; Slack uses a lighter penalty | 22 or 12 |
| Missing canonical identity | All platform scores | 10 |
Missing explicit twitter:card |
X / Twitter score | 12 |
| Missing explicit Open Graph title | LinkedIn, WhatsApp, and other Open Graph-first scores | 10 |
| Title above 95 characters or description above the platform length target | All platform scores | 8 |
| Image dimensions missing, too small, or outside the common card ratio range | All platform scores | 8 to 18 |
Missing theme-color |
Discord score | 4 |
| Check | Boundary | Review Meaning |
|---|---|---|
| Preview title | Blank is an error; below 20 characters asks for review except in quick review; above 95 characters warns. | The title should identify the shared page before truncation hides the useful phrase. |
| Preview description | Blank is a warning in launch checks and a review item otherwise; below 70 characters asks for review except in quick review; long text warns at 200 characters for launch checks and 240 for lighter profiles. | The description should summarize the page without relying on every platform to show the full text. |
| Preview image | Missing image metadata is an error. Non-HTTPS image URLs warn. | Rich cards need a public image URL that crawlers can fetch without cookies or bot blocks. |
| Image dimensions | Missing dimensions ask for review. Launch checks warn when the image is below 1200 by 627 pixels; lighter checks mark that as review. Ratios below 1.7:1 or above 2.1:1 ask for crop review. | Dimensions help avoid blurry cards, unexpected crops, and tiny images in large-card formats. |
| Canonical identity | Missing canonical URL, og:url, and X URL metadata raise a warning or review item depending on the profile. |
The preferred public URL should be clear before shares and caches start grouping the page. |
| X card selector | If twitter:card is absent, the preview uses the selected default card only as an assumption and reports a warning or review item. |
An explicit card type removes ambiguity for X card rendering. |
These checks are intentionally practical rather than official certification. Open Graph, X, Slack, LinkedIn, Discord, and search crawlers each keep their own rendering, cache, and access rules. Keep input values stable when comparing runs, and rerun the target platform's own preview tool after the deployed page changes.
Paste HTML parses the supplied markup in the browser. Fetch public URL sends the entered page URL to a remote fetch service so it can retrieve public HTML from its network position. The fetch path accepts only public HTTP and HTTPS targets, rejects localhost and private-network addresses, strips fragments, refuses embedded credentials, follows a short redirect chain, and stops when request time or response size limits are reached.
A page with og:title set to Launch Readiness Checklist, an og:description under 200 characters, canonical URL https://www.example.com/launch-readiness-checklist, twitter:card set to summary_large_image, and a 1200 by 630 HTTPS image should show a high platform fit value. Crawler Audit should report ready rows for Preview title, Preview description, Preview image, Image dimensions, and Canonical identity.
A documentation page may have a good title, description, and canonical URL but no og:image or twitter:image. Social Cards then shows image placeholders, Crawler Audit marks Preview image as an error, and Platform Scores drops below the ready target for most platforms. The text fields are still useful, but the shared link is not ready for a rich-card launch.
A staging address such as http://localhost:3000/launch or a private network URL will fail in Fetch public URL. Copy the rendered head from the staging page, switch to Paste HTML, set Base URL to the intended public address, and review Tag Ledger before publishing the real page.
Base URL is used to resolve relative canonical, image, and icon paths. Without it, a pasted value such as /social/share.png cannot be judged the same way a crawler would judge the final public URL.
Social Cards is a local preview based on extracted metadata and the tool's card assumptions. The final platform may use a cached scrape, apply a different crop, block an image, or ignore a fallback field.
Load remote preview images is off by default. The placeholders let you inspect image URLs and hosts without making browser image requests; turn the switch on only when the image URLs are public and safe to request.
Fetch public URL accepts one public HTTP or HTTPS page. Localhost, private-network addresses, URLs with embedded credentials, unresolved hosts, long redirect chains, timeouts, and oversized responses are rejected; paste the rendered HTML when public fetching is not appropriate.
No. Default X card is only the assumed card shape for previewing pages that omit twitter:card. Crawler Audit still reports that the X card selector is missing so you can add the explicit tag before launch.
twitter: tag names for card type, title, description, image, and image alt text.