OGP correction / handoff guide
When OGP previews look wrong: separate tags, image URLs and cache
HTML values and what a social network displays are not the same proof. Check tag presence, image URLs and refresh behavior as separate questions.
Separate three states first
This guide can verify only the local HTML values and proposed repair tag that were actually checked.
| State | Meaning | Next action |
|---|---|---|
| Verified | HTML values and repair tag were checked locally | Write original and repair into the handoff |
| Missing | A required OGP tag is absent | Give the smallest repair to the owner |
| Unknown | Reachability, cache or live preview was not checked | Keep that boundary visible |
Do not mix search and OGP tags
<title> and meta description are search-oriented source values. og:title and og:description are sharing values. Do not treat every platform fallback as one universal rule.
title: Store guideog:title: Autumn campaignog:image: missing<meta property="og:image"content="https://example.invalid/…">reachability: UNKNOWNMake the smallest repair
For a missing og:image, propose one escaped meta tag. Do not add duplicates blindly; reparse the fixed fixture.
<meta property="og:image" content="https://example.invalid/assets/offer.png">The tag and attributes can be checked locally. Reachability and social display remain unknown because this guide does not fetch the image.
Separate relative URLs, auth and cache
- Resolve
/assets/offer.pngagainst base URLhttps://example.invalid/offer. - Keep URL presence separate from successful image retrieval.
- Do not bypass authentication or public-access controls without approval.
- Do not infer social cache refresh or live display from a fixture.
Hand a repair note to the owner
Include target page, original tag, proposed repair, verified scope and what was not checked on a live social platform. A preview-like mockup is not proof of publication success.
These synthetic fixtures are static. No third-party page, image or script is fetched or executed.