How to Check Link Previews Before Sharing

A shared link can expose a title, description, canonical URL, and image information through page metadata. The receiving app decides whether, when, and how it fetches that information, so a correct page does not guarantee identical cards in every chat, social, or publishing service.

DevToolKit does not provide a built-in Open Graph preview checker. Use the page source, your browser's developer tools, and an actual permitted share destination to inspect what is available. This guide is about checking the public page, not bypassing a platform's cache, access rules, or bot protections.

Open the exact HTTPS URL you plan to share after it has been deployed. Use View Source or the Elements panel to look for a canonical link plus Open Graph properties such as og:title, og:description, og:url, and og:image. Where relevant, also inspect the Twitter card metadata.

Read the emitted values rather than assuming they match the editor or route name. A page can have a visible heading that differs from its metadata, and a canonical URL can point somewhere other than the link copied from the address bar. Record the URL you actually tested so a later change is easy to compare.

Check that the metadata title identifies the specific page and that the description explains its purpose without making an unsupported promise. Look for accidental page titles such as a generic site name, unfinished wording, duplicated sentences, or text that makes sense only inside an administration screen.

Keep the public heading, title tag, Open Graph title, and description consistent in meaning, while allowing each field to fit its job. Do not add words merely to fill a preview: a concise accurate description is more useful than a broad claim that the page cannot support.

Copy the og:image URL into a new browser tab and confirm that it resolves, displays the intended artwork, and is appropriate for the page. If it does not load in a normal browser session, correct the page or image delivery problem before relying on a share preview.

Inspect the image itself at a small viewport as well as at full size. Readability, crop, transparency, and the amount of text are design decisions to review visually; this site has no automated accessibility, social-network, or cross-platform rendering audit. If you need a differently sized asset, create and check a new export rather than assuming an image transformation will make a card correct.

Use a private or otherwise permitted test location on the service you care about, then paste the exact deployed URL. Compare any rendered card with the source inspection: title, description, destination URL, and image. A missing or old card is evidence to investigate, not proof of one particular cause, because the receiving service controls its own fetching and caching behavior.

If the share differs from the page source, first confirm that the URL is public to the intended audience and that the deployed HTML contains the expected metadata. Then check the receiving platform's own documentation or debugging options, if it provides them. Do not try to solve a truncated or altered shared URL by URL-encoding it: encoding changes URL characters; it does not repair a platform's length or handling policy.

Image Resizer and Image Compressor can help create a reviewed image export, but they do not add Open Graph tags, publish an asset, or verify a social preview. Their core image operation runs locally in the browser; their pages disclose that limited usage or diagnostic metadata may still be sent. Read the processing label before selecting a file.

URL Encoder / Decoder transforms text with browser URL-encoding functions. It is useful for inspecting or encoding a URL component when you know that is needed, but it does not validate a public page, generate metadata, or guarantee that a third-party platform will accept a link.

Before sharing widely, confirm in order: the deployed HTTPS page opens; the canonical URL and the URL you will share agree where intended; the title and description are accurate; the declared image opens directly; and at least one permitted real-share test reflects the current page closely enough for your use.

Keep a note of the tested URL and time. That gives you a factual baseline if a platform later displays an older card or a different treatment. It does not guarantee future preview behavior, because the receiving platform remains outside this site's control.