// Marketing & SEO

Social Preview Repair

Diagnose broken link previews, repair the metadata and image asset, and produce platform-aware verification without false cache claims.

Get it on Agensi Browse all skills $12 one-time

What problem does Social Preview Repair solve?

A shared page renders a missing, stale, cropped, unreadable, or generic preview because its metadata, image asset, URL, redirects, headers, or platform-specific requirements are wrong.

Use it to

Fix a LinkedIn or Slack preview whose image is missing, cropped, stale, or unreadable
Repair canonical, og:url, og:image, title, description, and image metadata
Check redirect, response, content-type, crawler-access, dimension, and crop evidence
Separate a verified page-side repair from an unverified or pending platform recrawl

What it returns

Metadata, URL, redirect, header, dimension, and fetchability diagnosis
Corrected Open Graph and social metadata patch
Readable preview-card specification or generated SVG asset
Before-and-after preview verification sheet with cache caveats

A representative input and result

fixture-backed sample

input URL: https://example.com/product Target: LinkedIn and Slack Problem: title appears but the image is missing Brand assets: logo.svg and product screenshot.png

result Root cause: og:image uses a relative URL and the resulting image response has SVG content type not accepted by the target preview path. Repair: publish a 1200x630 raster card, set an absolute HTTPS og:image URL, add width/height/alt fields, and keep the canonical URL stable. Verification: page and image return 200 without authentication; metadata resolves to the final canonical host. Cache note: page-side repair is verified, but LinkedIn's next recrawl time is not controlled or claimed.

Access and approval boundaries

Read access to the supplied URL, page source, response headers, and brand assets.
Optional network access for public-page and image fetchability checks.
Source writes, deployment, debugger submissions, and other external actions require separate approval.

Known limitations

Remote networks choose when to recrawl and may continue showing cached data after the page is correct.
Private, blocked, authenticated, region-limited, or bot-protected URLs may not be verifiable from outside their environment.
Platform rendering can change and may crop or prioritize fields differently from a local approximation.

// choose with context

Best fit

A shared page renders a missing, stale, cropped, unreadable, or generic preview because its metadata, image asset, URL, redirects, headers, or platform-specific requirements are wrong.

It returns

Metadata, URL, redirect, header, dimension, and fetchability diagnosis. Corrected Open Graph and social metadata patch.

Do not use it as

It does not claim to clear or control a social network's remote cache.

Compatibility, access, version, and licence

Reads or accesses: Declared local scope: src/**, app/**, pages/**, public/**.
Compatibility: Static HTML and framework-rendered pages with accessible head metadata. Open Graph, X card, LinkedIn, Facebook, Slack, and common messaging-preview conventions where publicly documented. Public URLs or supplied source for private and pre-release pages.
Version: 1.0.1
Licence: Review the package licence and seller terms at the linked destination.

What happens next

The Agensi listing opens at the current offer. Complete purchase there, inspect SKILL.md and its bundled files, then add the complete folder to your agent.

Questions

Why is my LinkedIn preview image missing?

Common causes include relative or inaccessible image URLs, redirects, unsupported response types, blocked crawlers, dimensions, stale metadata, and remote caching. The skill tests the evidence before choosing a cause.

Can it clear LinkedIn or Facebook's cache?

No. It can prepare or, when authorized, submit supported debugger actions, but it records page-side correctness separately from remote recrawl behavior.

Does it generate a replacement card?

Yes. It can produce a crop-safe card specification or generated SVG asset using supplied brand material and verified page content.

Can it work before the page is public?

It can inspect supplied source and assets, but public fetchability and final network rendering remain unverified until the URL is reachable.

How is this different from an Open Graph audit?

It includes the bounded metadata repair, a suitable card asset, and verification evidence rather than stopping at a defect list.

Does one card render identically everywhere?

No. The workflow uses crop-safe composition and platform-aware checks, while noting that each network controls its own renderer.