Missing social sharing tags

A title, which is frequently shortened differently from the page title and deserves its own value.

A description, which is the one or two lines under the title and is not the same job as a search snippet.

An image, which is most of the card's visual weight and the element that decides whether anyone clicks.

A canonical URL for the shared resource, so shares of parameterised variants are attributed together.

A type, which tells the platform whether the page is an article, a product or something else.

A logo as the image, which every share of every page on the site then looks identical.

A cookie banner's text as the description, because it was the first text in the document.

A navigation label as the title, on pages where the title element is generic.

No image at all, which produces a small text-only card that is measurably less clicked.

A decorative background as the image, cropped by the platform in a way that shows nothing recognisable.

Platforms crop to their own aspect ratio, so an image whose subject is near an edge loses it.

There are minimum dimensions below which a platform falls back to a small card or to nothing.

The image must be reachable without authentication, which excludes anything behind a login or a signed URL that expires.

An image served only in a modern format that a platform's fetcher does not support produces no card.

Absolute URLs are required: a relative image reference is a common reason a card renders with no picture.

Platforms cache the preview after the first fetch, so fixing the tags does not change an already-shared link.

Each platform provides its own debugging tool that re-fetches and shows what it sees, which is the only reliable way to test.

A card that looks wrong may be a cached version from before the tags existed.

Which is why the sequence is: fix the tags, force a re-fetch through the platform's tool, then share.

Testing by sharing into a private conversation before the tags are right is what populates the cache with the wrong version.

Sharing metadata does not affect search ranking and is not read by search engines as a ranking signal.

The page title and meta description remain the search-facing values, and they serve a different purpose.

Writing one set and expecting it to cover both produces a description that is too long for search or too flat for a card.

So the two are separate, small pieces of work rather than one.

Which is also why a missing sharing tag is reported separately from a missing meta description.

View source and confirm the title, description, image and URL properties are present.

Confirm the image URL is absolute and reachable without a session.

Use each platform's own preview debugging tool, which re-fetches and shows the card it would build.

Check a deep page rather than the home page, since the tags are frequently set only on the template that was reviewed.

Check that the image is not a logo on every page, which is the most common form of present-but-useless metadata.

`seo.open_graph` reports the social sharing tags present in the served markup, which is this problem directly.

`seo.title` and `seo.meta_description` report the search-facing values, which are separate and frequently confused with these.

`seo.canonical` reports the canonical tag, which the sharing URL property should agree with.

`images.inventory` supplies the images the page references, which is what a platform would otherwise guess from.

Whether a platform renders a usable card is its own behaviour and is outside what reading the markup establishes.

Some platforms read a second set of properties of their own, which overlap heavily with the first and differ in a few names.

Most of them fall back to the primary vocabulary when their own is absent, so a complete first set covers the common cases.

The one value worth adding separately is the card type, which decides whether a large image or a small thumbnail is used.

Duplicating every property into both vocabularies doubles the markup and the maintenance for very little gain.

Which makes the practical answer: a complete primary set, plus the one or two values that genuinely change the rendering.