Social Preview Repair
Diagnose broken link previews, repair the metadata and image asset, and produce platform-aware verification without false cache claims.
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
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.
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.
Social Preview Repair keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Social Preview Repair on Agensi