Link Preview

Enter a public URL and review the title, description, image, favicon, domain, and fetched metadata before sending the link to a post, message, ad, or client review.

Use it when a shared URL shows the wrong headline, image, or description.

Raw metadata stays beside the preview for clearer developer and marketer QA.

  • Check Open Graph and Twitter Card fields
  • Preview a public URL before sharing
  • Spot missing title, image, and description data

How to use Link Preview

Use these steps to inspect a link card the way a real person would before publishing, sending, or asking another team to review it.

  1. 1

    Enter URL to inspect

    Paste the final public URL, including the protocol. Use the exact page you plan to share, not a dashboard URL, preview-only CMS link, or redirect you do not control.

  2. 2

    Fetch the page metadata

    Run the check and review the fetched title, description, image, favicon, publisher, cleaned URL, and domain. If a field is blank, the page may not expose that tag.

  3. 3

    Review preview metadata

    Compare the preview against the channel where it will be used. A good link preview has a clear headline, a useful description, a correctly sized image, and no surprise tracking or redirect behavior.

Public URL metadata fetch

Fetches metadata from a public HTTP or HTTPS URL so you can inspect what the page actually exposes instead of guessing from the CMS editor.

Open Graph and card review

Helps check common preview fields such as page title, meta description, preview image, favicon, publisher, domain, and final URL.

Cleaned URL handling

Removes common tracking parameters before fetching so QA can focus on the canonical page and the metadata that matters.

Image quality clues

Checks preview images for usable dimensions when possible, which helps catch tiny favicons, tracking pixels, or missing social images.

Share workflow fit

Useful before sharing links in Slack, Discord, LinkedIn, X, Facebook, email campaigns, documentation, support replies, or launch notes.

Debug-friendly output

Keeps the source URL and fetched metadata together so it is easier to send a clear issue back to a developer, editor, or SEO owner.

Link Preview privacy and processing

Link Preview uses server-assisted fetching because browsers cannot reliably read another site page directly. The page shows what is sent, what is stored, and why some URLs may fail.

Processing Server-assisted

Link Preview sends the entered URL to a server route that fetches the page, follows allowed redirects, removes common tracking parameters, and extracts readable metadata.

Storage None

Fetched metadata is shown for the current check. The tool is not a bookmark manager, campaign archive, or permanent preview history.

Link Preview account access

Link Preview works without sign-in, which is useful for quick QA on published pages, launch URLs, client drafts, and social-share checks.

Before You Use Link Preview

Check these points before using the result as proof that a link will render perfectly everywhere.

Privacy

Use public URLs only. Private dashboards, invite-only documents, staging pages, and signed links may fail or expose metadata you did not intend to review.

Do not paste links that contain tokens, private query strings, or customer-specific identifiers unless you have already removed them.

Accuracy

Social platforms often cache link cards, so a fixed title or image may still look old until that platform refreshes its cache.

If the preview looks wrong, check the page source for Open Graph tags, Twitter Card tags, canonical URL, redirects, and blocked image URLs.

Compatibility

The tool expects HTTP or HTTPS URLs. Mail links, app deep links, local addresses, and malformed URLs are not a good fit.

Some sites block server fetches, require JavaScript rendering, or hide metadata behind consent screens, which can limit the returned result.

Output

Use the output as a QA view, then still test the final URL inside the actual platform if the post, campaign, or launch is important.

Keep a note of the exact URL checked so teammates can reproduce the same preview and avoid debating different redirected versions.

Limits

Link Preview checks one public HTTP or HTTPS URL at a time and returns the metadata fields the destination page exposes.

Metadata fetching can be limited by private pages, robots rules, bot blocking, redirects, missing tags, slow servers, or cached social previews.

Questions about Link Preview

What does Link Preview check on a URL?

It fetches a public URL and shows useful preview metadata such as title, description, image, favicon, publisher, domain, and cleaned URL when those fields are available.

Is this the same as an Open Graph checker?

It covers the same practical job for most page checks: inspecting the metadata that powers Open Graph previews, Twitter Cards, and link cards in messaging or social platforms.

Does Link Preview require an account?

No. You can check public URLs without creating an account. Avoid private, tokenized, or customer-specific links unless they are safe to fetch.

Why does my fixed preview still look old on social media?

Many platforms cache link previews. If the page metadata is now correct, refresh that platform's debugger or cache tool and then test the exact final URL again.

4.4 (614 ratings)