Help Centre

A shared link that shows no title, no description, or a broken/missing image usually means one or more social meta tags are missing or incorrectly configured. The most common causes are:

— Missing og:title or og:description. Social platforms use these to populate the card. Without them, platforms fall back to heuristics (the page <title>, the first paragraph) or show nothing at all.
— An og:image that is a relative path. If the value is /images/hero.png instead of https://example.com/images/hero.png, the platform cannot resolve it and shows no image.
— An image that 404s or is too small. LinkedIn prefers 1200×630 images. Twitter's summary_large_image card also benefits from at least 600×315. Smaller images may be cropped, stretched, or ignored.

Paste your URL into the Previewcard app to get a full diagnostic of exactly what is missing or broken.

Each meta tag in the report gets one of three statuses:

✓ present — the tag was found in the page's HTML and its value was parsed successfully. For image tags, this means the image URL resolved and returned a valid response.
⚠ warning — the tag is present but its value may cause issues. Examples: an image that loads but is smaller than recommended dimensions, a twitter:card type that limits the layout, or a tag that duplicates another platform's value.
✗ missing — the tag was not found in the page's HTML at all. Social platforms will fall back to their own heuristics, which may produce an unpredictable card rendering.

"Missing" for an image tag means Previewcard could not successfully fetch and verify the image. There are several possible reasons:

— The og:image value is a relative path (e.g., /images/hero.jpg) and the resolved full URL does not point to an existing file.
— The image URL returned a non-200 status (404, 403, 500, etc.).
— The image could not be reached — the domain timed out, the connection was refused, or the URL scheme is unsupported.
— The image is a format we do not parse (see Known Limitations below).

The report will tell you which of these happened. If the image loads in a browser but Previewcard cannot read it, check whether the server blocks automated requests (User-Agent filtering, CAPTCHA, or IP-based access control).

No. Previewcard is completely stateless. When you submit a URL, the checker fetches the page, parses the meta tags, fetches the images, and returns the results. That is the entire lifecycle of your data:

— Your URL is not stored, logged, indexed, or cached after the response is sent.
— The fetched page content exists only in the Worker's memory during the request and is discarded immediately afterward.
— Results exist in your browser's memory only — refreshing or closing the page clears them.
— No cookies, tracking scripts, or analytics are used.

See the Privacy Policy for the full details.

Previewcard reports what the page's HTML declares. Social platforms have their own rendering, caching, and fallback behaviour:

— Caching. Platforms cache preview data for hours or days. If you just updated your tags, the platform may still show the old preview. Use LinkedIn's Post Inspector or X's Card Validator to request a re-fetch.
— Different tag vocabularies. LinkedIn reads og: tags. Twitter/X reads twitter: tags but falls back to og: for some fields. Slack and Discord also vary in their tag priority. Previewcard shows each vocabulary separately so you can see which tags each platform will use.
— Platform heuristics. When a tag is missing, platforms guess — they may use the HTML <title>, the first image on the page, or the first paragraph. Previewcard never does this; it only reports what the meta tags actually say.

Previewcard diagnoses the page's metadata — it does not predict every platform's rendering. A clean Previewcard report means your tags are correctly declared, but each platform may still render them differently.

Not yet. The web app is the only interface today. An API with key-based access and higher rate limits is planned for the Pro tier, which is on the roadmap but not yet available. See the Pricing page for the planned feature list.

Previewcard checks the two standard meta tag vocabularies: Open Graph (og: prefix, used by Facebook, LinkedIn, Discord, Pinterest, and many others) and Twitter Card (twitter: prefix, used by X/Twitter). Tags from both vocabularies are parsed and reported separately. The tool also shows standard HTML meta tags that are relevant to social sharing.

The web app has no enforced rate limit for manual, individual use. Automated or bulk submissions are not supported on the Free tier. If you need programmatic access, the planned Pro tier will offer an API with dedicated rate limits.