Open Graph preview checklist before sharing links

Bad link cards make good posts look unfinished.

The copy can be fine, but if the preview title is stale, the image is missing, or the description is wrong, the post looks careless. I check the card before I schedule anything important.

Use TheBlue.social's Open Graph preview tool for the first pass. Paste a public URL and check the metadata that social networks use for link previews.

What the tool checks

TheBlue's OG preview tool fetches the page and shows the important fields:

  • Title
  • Description
  • Image
  • Twitter/X image
  • Image width and height when available
  • Image size when available
  • Site name
  • Type
  • URL
  • Twitter card type

It also calls out missing common fields and gives a copyable HTML example for missing Open Graph tags.

It does not fetch localhost or local file URLs. That is deliberate. Test public URLs, staging URLs, or deployed pages that the backend can reach.

The checklist I use

I check these before sharing a link:

  • Does the preview title match the page people will open?
  • Does the description explain the page, not the whole site?
  • Is the image present?
  • Does the image crop make sense in a card?
  • Is the canonical URL the one I want people to share?
  • Is there a Twitter/X image when the OG image alone may not be enough?
  • Is the preview stale because a platform cached an old card?

Most link-card bugs are not technical mysteries. They are usually missing tags, the wrong image, or a cached response.

Fix the page, not the post

If the preview is wrong, I fix the page metadata first.

Editing the social post around a bad card is a workaround. It does not help the next person who shares the same URL. Update og:title when the title is wrong. Add og:image when the image is missing. Fix og:description when the description is vague.

Then check the URL again.

For TheBlue article pages, regenerated pre-rendered HTML matters. The live page needs the updated title, description, canonical URL, and image tags. A normal app deploy does not automatically publish article HTML if the article pre-render bundle is served from the separate article release directory.

That is the sort of detail I want to catch before publishing.

Pair it with the post previewer

The OG preview tool checks the link. The multi-platform post previewer checks the text around the link.

I use both:

  • Paste the URL into the OG preview tool.
  • Fix missing or stale metadata.
  • Paste the final social copy into the post previewer.
  • Check length, line breaks, link count, and emoji density.
  • Move the draft into TheBlue.social's scheduler.

The two checks catch different problems.

The OG tool will not tell you the post is too long for X. The character counter will not tell you the link image is missing. Use the right small tool for each small job.

What to do when the card looks wrong

If the card is wrong, work through this order:

  • Confirm the URL is public and not blocked.
  • Check that the page has og:title, og:description, and og:image.
  • Check whether the image URL is absolute and fetchable.
  • Check whether the page redirects to a different URL.
  • Rebuild or regenerate the page if it is pre-rendered.
  • Wait if the social platform has cached the old card.

I do not start by blaming the scheduler. The scheduler posts the URL. The card usually comes from the page metadata and the platform's cache.

Where TheBlue fits

TheBlue is useful around the publishing work:

That is the practical shape: check the page, check the post, then schedule.

Last updated: June 9, 2026